Essentially, the longer you’ve been earning money on Envato, the more work you have to do now if you wish to hold on to that income. If you have a dozen, two dozen, three dozen themes up on TF, you’ll be facing busy times indeed. It’s like a retroactive law; you’re kind of being punished for something that was completely permissible at the time you did it…
Maintenance is a part of selling themes. Over time, they need to be updated. Themes that were accepted when standards were low affect the reputation of the marketplace as a whole if they aren’t brought up to meet the standards.
We ran these guidelines by a number of authors, some who do have more than two dozen themes.
Do you expect that forcing authors to move features from theme to bespoke plugins will allow end users to switch from this to this seamlessy ?
More likely, each theme will include its own set of custom plugins that would need to be mandatory installed to replicate the demo and to mix them with previous themes custom plugins will lead to anything but a seamless experience for buyers and authors.
Who’s going to deal with raging buyers when everything will break horribly (because it will) ? Who’s going to bear the burden of support ? old theme author ? new one ? you think buyers will accept “we can only support our own theme/plugins when used together” kind of answer ?Who asked for this changes ? buyers ? I doubt so, having dealt with thousands of them myself and not yet having found one who cares about the issues you’re trying to address with these new rules.
You make some interesting points, and we’ll definitely be discussing them.
You’re trying to enforce wp.org rules on TF when TF products are anything like wp.org ones.
Interesting distinction you make. Do you believe your customers will only use a ThemeForest theme and its bundled plugins, without any plugins from wp.org? And that plugins bought from CodeCanyon will only be used with ThemeForest themes, and not themes from wp.org?
Shouldn’t they all play as nicely together as possible?
First of all, 3 weeks is a joke and even further grace period is a joke for existing themes. We simply needs MONTHS to apply these changes gradually.. like a few per update.
Three weeks was our initial thoughts before we start applying all these to newly submitted themes. We’re happy to take your feedback into consideration on this though, of course!
As for existing themes, we know it’s going to take months, and you’ll have them
“Inadmissible shortcodes” will not be allowed in “shortcode” plugins If that’s true do you know how buyers will react?
That’s not what we said, so let’s assume it’s not what we meant
These will be inadmissible in the theme. Shortcodes should be in plugins, not the theme itself, as much as possible.
Hi, Japh: I do not agree with this view. If you set the post counts options for category, not mean it will change the global posts_per_page parameter. Also If the theme has portfolio and blog, then the layouts of portfolio and blog are different, the users need to set each post count for the portfolio and blog.
Good point, thank you. Will take this into consideration.
7. Themes are not permitted to add options that define the number of posts to show on archive or category pages.
Is there any reasons why we can’t do this? We can filtered the ‘pre_get_posts’ to change posts_per_page value for archives and category. Problem will raise with the theme that have many post types, or theme that provide option to choose columns layout per category.Anyway this is a great news, thanks!
WordPress itself already provides a feature for this.
Also, themes that do add this option can break plugins. For example, some plugins might break because the theme is setting a global
posts_per_page parameter and so a “number” parameter in the plugin becomes useless.