Hey everyone - I'm going to take a crack at this in the next few days!

Awesome @seanprashad!

Just so that we're clear on what the bug here really is: Imho it's almost a feature that we don't randomly overwrite the theme name. So we'd have to store some information if the users have overwritten the theme name but even then I'm unsure if the current behaviour is still preferable.

Any opinions on this? I don't want you to waste too much time on something that - at least for me - looks perfectly fine.

Hey @EnTeQuAk! I've just begun inspecting code but from the GIF in the OP, it looks like the theme name is being populated based on the uploaded header image filename.

From my perspective, if I were a user who wanted to create a new theme, say Octocat, but my header image was named Addon_Octocat.png, it would be an extra step in my workflow to correct the contents of that form control. Now in reality, most of the users who are developing addons are probably savvy enough to make the correction after the image upload but it might reduce the need for editing the theme name after they've submitted it - just food for thought!

Edit: I think it should not update the Theme name at all, even if that form control is left blank. The Theme Name is something that will be saved into the system and will be how the end-user will find the new Theme and as a result, shouldn't surprise the user in any way, shape or form.

Just an update @EnTeQuAk - I've opened a PR with my take on what a possible solution would be.

Like I mentioned earlier, I don't think we should populate the Theme name with the header image name at all. More than likely, the header image's file name isn't professional and doesn't necessarily reflect the name that the creator would want to have. If I'm not mistaken, this Theme name is what will be used to allow end-users to search for the theme and as such, should be manually specified without surprises!

If you think we should take a different path, I'll be happy to update my PR to reflect the desired functionality!

Alrighty, so I discussed this with @eviljeff and we actually like the current behaviour. It gives the form a good default and doesn't overwrite any manual changes.

That's why I'm just going to close this issue, although I'm really sorry for all the work and brain you put into this. Thanks a lot for this!

Sorry for getting back to this issue so late.