Themeforest Review TimeTopic Forest Review Period
The same applies to dishonest reviews or simply false reviews from shoppers who are sometimes too dumb or too rotten to even look at the doc. More elite writers are taking part in these debates, not just small people. You have become a large company and like almost every company you do not have to worry about staff or writers in this case.
Think it'?s a little unaccountable to act like that. Three weeks of queuing for a business is a long time. But if you have staff and other project, it really isn't that easy. It'?s really weird, 19 consecutive years.
Topic Forest Review Process
Lately there have been many contributions in the Themeforest forum about the topic review proces, review time, tough refusals, smooth refusals and many disappointed writers, so we thought we'd be writing a brief contribution on this topic. We have been part of Themeforest for over 4 years now and we are also elite writers, which means that over the years we have had our own fairly good proportion of denials, so, as you would expect, we have a pretty good understanding of the major grounds for denial and hopefully this contribution can help you.
Check times. Okay, so the first grievance we began to see a great deal about is review time. Now, first you must realize that the market place has been growing at an exponential rate in recent years, with 4 million members, 6 million articles for purchase and a small review group. Obviously, the number of articles posted is enormous, so it will take time to move through the review line, it's just the way it is.
Send your article and continue, take a rest, launch another topic, get to know new things, everything is much better than sit at your dashboard and wait for the review, use your time constructive instead. Okay, let's continue, the next grievance is the number of denials an writer has. Now, think about it, think about it, think that the examiner would sit down and go through every topic and write a listing of every edition, you would be much longer in the review line than the actual 7-day mean, and you would feel even more disappointed.
Or how about if the appraisers are just people? The first time you did, you just skipped it. That's reasonable, isn't it? However, there is an advantage over many software refusals because the bug is captured before your article goes on sale. It also tells us that many writers like to know when their article will be released for commercial use, and maybe Envato could take a look at that, possibly an opportunity for an writer to go online at any time after approval, which can only help with the entire review lifecycle.
In fact, if your article has problems, then it will have denials, no matter what happens, the simplest way to get no denials or decrease the amount of denials is to make sure that the article is correct at all. Therefore, the next section of this article will discuss frequent grounds for refusal and a check list of things you should do yourself before you submit your article.
Okay, so the verification methodology is something like this: Considering this, the first thing you want to review is the final look, after all, if the auditors see a really bad look, they won't even get into the coding review.
OK, then you post your article for review, everyone says it's as fantastic as you knew it was, good shit, now to review the coding. Most of this section concentrates mainly on WordPress topics, but you can also take away some of the HTML template tips. validating: If your first verification should be your validations, validates your codes?
Don't get too involved with validating, yes, you should eliminate as many validating bugs as possible, but some bugs will simply appear no matter what you do, whether it' error code error or problems with interleaving because of a dynamical section being added, all you have to do is make your own judgment about what is OK and what isn't.
Several of our own theme have about 10 validating flaws, just because of interleaving problems, or WordPress does the common p-tag packing routine where they are not needed, which happens, but some them have more than 200 flaws, which is just not tolerable. Features: If you are building user-defined features, you should log into your own script in your own script, and execute your features as soon as the topic is initiated. add_action('after_setup_theme','my_theme_setup'); it is also recommended to prepend all your features to avoid plugin named conflict.
Not only is this very important that it is a big ground for refusal, it is also a good exercise to ensure that your topic is as safe as possible. Again, it is advisable to make any text in the topic translateable so that the users, even if they don't want to compile the topic, can modify the value of the text in the entire layout by using.mo/. po instead of searching through them.
WordPress features: Ensure that you use the WordPress defaults properly. Your designs are original and up to date? Is your validated password?
Your source documenting well? Is your function preset? Can your topic be translated? Do you use WordPress features properly? Did you test your topic with your test units? Did you enable debugging in wp_config. and test it with the themes checked plug-in? Compliance with this schedule does not ensure initial authorisation, but should lead to a reduction in the number of refusals.