Im trying to publish a map, and it says "not enough space remaining on this account". The map is only 1.5mb and i have _nothing_ uploaded yet. Catch 22.
I emailed blizzard and they told me to run the repair tool, and delete the maps/cache folder, didnt help. Has this happened to anyone else?
Try publishing it under a name which is a little bit different.
What I see is that the publisher thinks it's updating a map you've already published, but the map isn't published yet.
So changing the map name might fix that.
perhaps do a private publish with the word test added to it orso to check ;p
Yes it has. I had it happen when I deleted a map from my account, then tried to re-publish it later using the same name. If you change the name of the map using the naming option in the publishing dialog, it will allow you to publish the map. You can then publish it again using the original name, and it should work. However, it will retain the version # for some reason.
At least, this is the solution that worked for me. Its seems your situation is a little different than mine was.
Im trying to publish a map, and it says "not enough space remaining on this account". The map is only 1.5mb and i have _nothing_ uploaded yet. Catch 22.
I emailed blizzard and they told me to run the repair tool, and delete the maps/cache folder, didnt help. Has this happened to anyone else?
@Fender187: Go
Try publishing it under a name which is a little bit different.
What I see is that the publisher thinks it's updating a map you've already published, but the map isn't published yet.
So changing the map name might fix that.
perhaps do a private publish with the word test added to it orso to check ;p
@Fender187: Go
Yes it has. I had it happen when I deleted a map from my account, then tried to re-publish it later using the same name. If you change the name of the map using the naming option in the publishing dialog, it will allow you to publish the map. You can then publish it again using the original name, and it should work. However, it will retain the version # for some reason.
At least, this is the solution that worked for me. Its seems your situation is a little different than mine was.