Cannot upload a resource: "The following error occured: Please enter a valid title.".

[Krotos]

I believe the picture is self-explanatory.

As a note I don't have the map title window above map description either.

 

[Dr Super Good]

@Ralle

The title bar appears to be missing from the add map form. It is there for the update map form, just not the add map form.

I am unsure of the cause, but it is physically not on the page (not hidden or very small). Known to effect both Edge and Chrome so is not some browser specific problem.

 

[Daffa]

It's suppose to take map data initially if I'm not mistaken.

 

[Ralle]

Right. Can you post the map here so I can inspect it?

 

[Krotos]

Right. Can you post the map here so I can inspect it?

Dropped my work in the pastebin here. Fall of Quel'thalas | HIVE

 

[LordDz]

You have a dot in your map name, generally in Windows, a dot marks the start of a file type. So don't include dots in your file name.
I'd guess that's what the server is annoyed with.

So name it "Fall of Quel'thalas_1_1.w3x" instead.

 

[Krotos]

You have a dot in your map name, generally in Windows, a dot marks the start of a file type. So don't include dots in your file name.
I'd guess that's what the server is annoyed with.

So name it "Fall of Quel'thalas_1_1.w3x" instead.

That sounds like some high nonsense, considering the fact Hive has maps with a dot in their name like Lordaeron: the Foremath for example.

 

[LordDz]

Well it was a guess.
Still, good practice to not include dots in filenames

 

[Dr Super Good]

You have a dot in your map name, generally in Windows, a dot marks the start of a file type. So don't include dots in your file name.

Not his problem. Windows supports file names with multiple dots... A lot of Warcraft III maps use it for versioning.

Still, good practice to not include dots in filenames

Not really...

If the name is meant to be auto detected, then it is likely a conflict with the map protection solution being used.

 

[Krotos]

Any news on the matter?

 

[Dr Super Good]

Have you tried uploading a placeholder map first? A simple "Just another Warcraft III map" with some minor name and title changes but without map protection and such.

If that passes the title test and gets published then you can update it with your actual map and change the title appropriately using the update map template which does have a distinct title field.

 

[Krotos]

Have you tried uploading a placeholder map first? A simple "Just another Warcraft III map" with some minor name and title changes but without map protection and such.

If that passes the title test and gets published then you can update it with your actual map and change the title appropriately using the update map template which does have a distinct title field.

So I tried posting the unprotected version of the map and it did go through, but it doesn't let me update the bundle with the protected version of the map, claiming that I need to use a "valid file with 100 characters or less".

 

[Chaosy]

Not allowing protected maps seem like a great idea to me. I approve

 

[Krotos]

Not allowing protected maps seem like a great idea to me. I approve

I don't - I don't want to have my work out in the open for some random person to hop in, screw the wires in it and then have it blamed on me.

 

[Chaosy]

If I wanted to open your map, you can bet money I would be able to.
You just make it more annoying by protecting it.

More importantly, I do not like the mindset of "My map is so great I need to protect it because my hundreds of thousands of fans will make copies of it"
Unless you are the dev of dota that's not realistic and is a doucebag move

 

[Krotos]

If I wanted to open your map, you can bet money I would be able to.
You just make it more annoying by protecting it.

More importantly, I do not like the mindset of "My map is so great I need to protect it because my hundreds of thousands of fans will make copies of it"
Unless you are the dev of dota that's not realistic and is a doucebag move

I disagree with that - protecting the map is there so that you can't have a 10yo Billy open it, drop some random crap in it and then leave it under your name: the amount of hacked/bugged/broken Tree Tag and DAoW versions should tell you that.

Besides I don't think this is the place for such discussion.

 

[Dr Super Good]

The form of protection you are using must not be compatible with the API Hive is using to extract data from the map.

Now Hive does support map protection, but some sorts of protection might be so stupid that it is more by chance the map can still be opened in Warcraft III than it being protected.

I suggest disabling all sorts of MPQ archive corruption protection and trying to upload again. Such protection is stupid anyway since if Blizzard ever changes their MPQ code the map might stop working, and common MPQ tools get updated to bypass such protection quickly after it is discovered.

If it still does not work, it might be due to some sort of internal file corruption protection, or due to some kind of optimization conflicting with the APIs used by Hive.

The idea is to disable parts of the protection 1 by 1 until the map can be uploaded. One then knows which feature is breaking Hive and either Hive can be fixed to work with it, or the tool author can fix the protection method so as to not break Hive.

 

[Krotos]

Any news on the matter, @Ralle ?

 

[Ralle]

Sorry. Had a daughter since I last posted in this thread. Will look into this and get back to you.

 

[Ralle]

Fixed.

It didn't directly have to do with the protection but rather the optimization of inlining phrases instead of using TRIGSTR_XX for strings in the war3map.w3i file.

 

[Krotos]

It worked, cheers!