To accept theme uploads that contain theme files nested inside instead of throwing an error.
Or at least, throw a more comprehensive error message.
Why
Envato Themeforst is a major .org theme seller. The default theme file they provide the users is in Zip format and it includes the theme files in a nested zip along with other files than the theme files (like licensing and documentation).
When uploading that default file users are met with a generic error message.
This is often translated as WordPress.com doesn't support that theme. Or there is an issue with the theme, which results in third-party theme support teams suggesting another host (wrongly).
This is so prevalent that we have a dedicated section on our documentation about that: Upload a Theme
I also had a case of churning for that exact reason: 8897937-zen
How
Better theme file handling:
Our system could extract the theme file and check for nested zips.
For performance, we can limit the number of zip files checked, the depth of the search, and file names.
Typically, the needed theme zip files are one level deep and inside a folder with the word "theme" on its name.
This should address more than %50 of the cases (wrong theme file downloaded from themeforest).
More comprehensive error message:
It can be a dynamic message that checks if the file is suspected to be from Envato themeforst.net, and includes a link to our documentation: Upload a Theme
Or just include a link to that support guide in all cases.
What
To accept theme uploads that contain theme files nested inside instead of throwing an error.
Or at least, throw a more comprehensive error message.
Why
Envato Themeforst is a major .org theme seller. The default theme file they provide the users is in Zip format and it includes the theme files in a nested zip along with other files than the theme files (like licensing and documentation).
When uploading that default file users are met with a generic error message.
This is often translated as WordPress.com doesn't support that theme. Or there is an issue with the theme, which results in third-party theme support teams suggesting another host (wrongly).
This is so prevalent that we have a dedicated section on our documentation about that: Upload a Theme
I also had a case of churning for that exact reason: 8897937-zen
How
Better theme file handling:
Our system could extract the theme file and check for nested zips. For performance, we can limit the number of zip files checked, the depth of the search, and file names. Typically, the needed theme zip files are one level deep and inside a folder with the word "theme" on its name. This should address more than %50 of the cases (wrong theme file downloaded from themeforest).
More comprehensive error message:
It can be a dynamic message that checks if the file is suspected to be from Envato themeforst.net, and includes a link to our documentation: Upload a Theme Or just include a link to that support guide in all cases.