Great, standards are always great.
* Inadmissible shortcodes, all the listed ones can be added using a plugin, right?
Yes, shortcodes are best living in plugins, not themes.
* All HTML needs to be validated via the W3C validator. – will this be MANDATORY to whole theme? Sometimes at demo, you need use a style switcher, that usually will create warnings at validator, can you be more specific about validation, please?
My understanding is that this will be the theme itself. Will get clarification for you though.
* No inline styles are allowed any where – this means we can’t use style attribute or <style type=”text/css”></style> in our code, even when necessary? If we use a plugin to provide shortcodes, the plugin can add these inline styles, right?
Inline styles are the ‘style=””’ attribute. Plugins can enqueue stylesheets, etc.
* TGM Plugin Activation requires that the plugin stay inside theme folder? If we send the plugins (to shortcodes, portfolio and other things) in a separated folder and explain how to install the plugins that user want only – will we be rejected? Some plugins have 2MB or more, including inside theme folder would increase a lot theme package size, can you please clarify it?
That sounds fine to me, but I’ll get confirmation for you from the review team.
For a while now we have been working towards updating our theme standards on ThemeForest. The goal is to have a consistent, public standard so every customer has a seamless experience using our products.
Today, we’re proud to announce to the community that we’re unveiling our new WordPress Theme Submission Requirements.
We began this process by analysing the constructive feedback we had received over the past few months, and looking at industry standards to ensure we’re meeting them. We’ve been working on a few key areas including:
- WordPress Core API
- WordPress Features
- WordPress Unit Tests
- WordPress Assets
- PHP Quality
- HTML/CSS Quality
The next step was to get input from a group of experienced ThemeForest authors, to give input on behalf of the wider community. Their feedback has helped us revise our theme requirements to best suit both the market and our authors. We really appreciate their insight, and the time they took to help us out with this project.
As this is a fairly major update, we don’t want to throw anyone in the deep end. For the next
three eight weeks we’ll be recommending, but not enforcing, that new and existing themes meet the standards outlined above. After that, these will become the standards for reviewing all new themes. We will eventually be asking that existing themes also be updated to meet them, with a separate grace period to be advised at the time. Those changes should be small and gradual, and we’ll work with affected authors to assist them through the process.
Thanks to everyone for your patience while we make our theme standards, and the marketplaces, better and better!
Wow, such an amazing collection of adventures!
My wife and I have had our share of adventures too, actually. When I first started at Envato, we were trekking around Europe on our way back to Australia from living in the UK.
@ToivoMedia: Lauterbrunnen is one of my favourite places. I’ve been back there a few times. Also called the Valley of the 72 Waterfalls, apparently it was where Tolkien got his inspiration for Rivendell!
Probably my two most intense moments were:
About to board a train from Gomel (Belarus) to Moscow (Russia), and I see a guy pull a gun from his trenchcoat pocket, check the magazine, and put it back in his pocket. Then he, with two big guys flanking him, walks over to us to ask where we’re from and why we’re in his country. We answered, and he turned out to be friendly enough, but we were scared to start with. Then he told us he’d drunk a litre of beer and a litre of vodka on the way to the train… and we were scared again
The other: my wife and I had hired a small boat from Hvar (Croatia) to go around the Pakleni Otoci islands and have some lunch. The guy we hired the boat from said to take it for the whole day, just be back before 6pm. We found a lovely bay and had lunch. It was absolutely beautiful! Then we decided to continue on around the island just to see what’s around. What the guy didn’t tell us, is that between about 1pm and 3pm, you should find a bay and stay there. The water started to get really rough, so we thought “crap, better head back to Hvar before we get stranded out here”... bad move. We made it back, but were VERY shaken up, and the boat was full of water, and we had very white knuckles.
We also had some awesome fun adventures: swimming in the blue lagoon in Iceland, a gondola ride in Venice, eating haggis in the Scottish highlands, an amazing street market in Budapest, spending a week driving around Wales, going to the Top of Europe in Switzerland, visting the Berlin wall…
Man I miss travelling! Better do some more… who’s going to come say hi to me at WordCamp Europe?
Back at home for now though: (Photo courtesy of my wife)
Now the code does not matter? I think you guys are protecting Salient ’s author a bit much. So if your design is similar, you cannot have same lines. However if the design is different, we can have the same functions?
I think we both know that’s not what I was saying.
You’ve violated a policy and your theme was hard-rejected. It must be frustrating, and I’m sorry it’s happened to you, I wish you the best of luck with your next theme.
Please remove all popular items using the same code then?
For example Avada uses two functions:
function kriesi_pagination($pages = ’’, $range = 2) and function kriesi_breadcrumb() word by word. Yes, word “Kriesi” appears as well.
Since GPL does not apply to copying of other themes, and can be applied to translation phrases, remove it.
Guys you undestand that IT IS ONLY 6 LINES? They are not functions, not classes. single file, 6 lines of code.I won’t post any more, but I will be filing support tickets for every theme that uses similar functions.
FuelThemes, after looking at the tickets involved and the code, I can see that it’s more than 6 lines.
Spamming an already busy support queue with petty tickets won’t help your cause either.
I believe the case of Kriesi’s released code to be quite different from the case we’re discussing here.
It certainly isn’t fun to have your theme hard-rejected, so I can see why you’re not happy, however as was explained in your support ticket, your theme was removed for violating Envato’s Content Policy.
Unfortunately just saying “but GPL” doesn’t excuse copying from another marketplace theme, especially without even changing the names of theme-specific constants.
I don’t think that was the sole reason for disablement either. It seems to me it was a cumulative situtation where your design was too close to another theme, and then it was discovered you also had code snippets from the same theme.
Its inconvenient, but hopefully you can take this as a learning experience and avoid it next time.