hi, how long wordpress theme review process right now
4-5 days in general
If soft reject then again 2 days
wow, thanks
Looking up the wordpress.org requirements - seems like they allow 2 prefixes, one for the theme and one for the framework
Nope, I was told that we get the answers at the end of this week.
Hi Everyone,
Iâm sorry, but I wonât be able to provide an answer to this until early next week. Weâve started work on this but have been a little more delayed this week than expected.
I definitely havenât forgotten this and will keep you updated here (though hopefully my next post will be a proper response for you!).
Cheers,
Stephen
Anything new?
2 Likes
@mad_dog any news?
Hey guys!
We should wait for official response. The Envato team is discussing this issue.
2 Likes
Do the reviewers even read what explanations we post in the message field when submitting?
I am continuously getting soft rejected for stuff that wasnât even mentioned in my accepted theme about 3 weeks back.
Things like base64 (which i donât use), fopen etc that are used in some fallback functions in redux framework.
Iâve posted a link to the redux site with explanations of why themecheck returns those warnings and even a discussion where one reviewer, Japh, said itâs ok. (https://docs.reduxframework.com/core/theme-check/)
Stuff like âINFO: More than one text-domain is being used in this theme.â where the text domains are actually from the plugins that I use.
All my attempts of communication were ignored. They keep spamming the same message every time, Itâs starting to get insulting after being an elite author and having more than 20 themes developed:
âInstall and run Theme Check plugin to fix the followingâ
Really?
I asked my developer to create some themes for my website and i used one of them. Can i upload those theme for envato for reviews?
Only if you have their permission or if you have written ownership of the copyright.
Beyond that its not just about uploading - you need to be able to support/update etc. in the future so you also need to be very comfortable with the code
Took me ages to get through with stuff like you said, things thatâs are listed as ok on the requirements page that are only used as a fallback anyway. One reviewer told me itâs ok to have those things listed then the next told me to remove them. In the end I ended up removing the fallbacks to get through. Serious hit on my time and finances.
Hi Everyone,
First, thanks for your patience. I know it took much longer to get back to you about this than I originally promised. Weâve now discussed this and have come up with a common understanding that we will apply consistently.
The current requirement will remain as it is for now:
Use a unique prefix for all function names, classes, hooks, public/global variables, and database entries to avoid conflict issues with plugins and other themes.
However, because that can be interpreted in different ways, we will add the guidance to use the following:
themename_
OR
frameworkname_(where framework functions are being used)
If you follow this, then your theme will be accepted. If you use something else, then you may (or may not) be asked to use these, at the reviewerâs discretion.
If you use your own framework, weâd encourage you to choose a reasonably unique framework name. If your theme name is not unique and you want to make it more unique, then adding an additional prefix to themename_ will be accepted, although it is not required.
Background: One of the things we discussed was how unique a prefix should be. Ultimately, the more complex the prefix is, the lower the chance of a clash. We looked at asking for something more complex, but in the end we decided not to. Instead, we recognised that the very act of using a prefix, regardless of itâs complexity, greatly reduces the chance of a clash and is enough in most cases. This decision was based in part on your feedback of real life examples, so thanks!
Theme name has become the standard in many parts of the WordPress community, so that remains our preference. However, we understand this is not practical for those of you who reuse functions between themes and weâll accept framework name in those circumstances.
Hopefully this will give all of us a clear and common understanding of this requirement, that is practical for authors to follow, and which will reduce any confusion and frustration that may have been occurring. If you have any questions or concerns, please let me know! Thanks everyone.
Cheers,
Stephen
6 Likes
Great to hear that we now have official answer. One question, not completely regarded to this. Are review times back to normal?
Hi,
thanks for the info - this is most concrete answer for the matter so far.
Just to make clear - it is ok to use our theme framework name as prefix, instead of themeâs name ? So, instead of using themename_ prefix itâs ok to use our_uniqueframework_ prefix ?
Would it be wise to mention this to reviewer when submitting theme ? To avoid at least one soft reject ⌠
Thanks
2 Likes
Stephen!
Thanks for collaboration.
You can use both.
2 Likes