Theme-Desert saidI have theme soft rejected right now for not using TGM, i think they made decision.
bitfade saidGreat job @bitfade !! Hopefully JAPH gives this the OK. It looks much cleaner than the TGM activation class.
Had some free time today, here’s the complete plugin install/update class github repo and a video showing how it works Japh, please let us know if we can use it instead of the TGM activation class.
As the new requirements don’t come in to affect until September, I find that unlikely. If you were using another class to activate plugins on install, it’s likely because they were not up to scratch. I doubt they’ve reviewed BitFade’s implementation yet!
Just as a heads up, your preview is messed up in FF (latest version): http://prntscr.com/1hue3b
our latest WP vCard got rejected because it didn’t have a WP native menu while almost all the WP vCards on themeforest including the latest ones do not have WP native menu, so are these requirements based on the new requirements ? (from what I’ve understood phase 1 will take place on Sept 9)
We have 7 projects in the pipeline being converted to WP so in order to avoid getting rejections based on unclear old/new requirements, where can we find the CURRENT WP requirementsthis link is for Sept: http://support.envato.com/index.php?/Knowledgebase/Article/View/472
Where can we find the requirements for July & August pleaseThanks UOU Apps
The requirements don’t come in to affect until September, but I would assume all WP themes require a menu to be defined. If it has no items assigned, just don’t show it and then you can display it as you wish on your demo.
We’ve had one one of ours held for three days before, but never five. We were getting a bit worried but all of a sudden it was approved, it’d be nice if they tagged a note saying why it was held just to satisfy eveyone’s curiosity.
Wow, you guys clearly have way too much free time!
You’ve stopped them!Hey Japh, i just had an idea: Some of us offer unlimited sidebars in the theme options. That’s a simple array where users add their own sidebars so they can be able to add them in whatever page. By thinking at portability, this would now go inside a plugin right? Because otherwise the users will be left without their sidebars on theme switch and only with a big list of inactive widgets. But how would this work with the next theme which might have it’s own way of creating custom sidebars?
I’d say sidebars should go in the theme, at least that’s where I’d like to put them. When they switch themes it’s highly unlikely they’ll use the same sidebar names so the widgets wouldn’t ever appear.
Pretty sure its main use comes in to play when creating complex JS apps. It provides the MVC concept in JS, in theory allowing for more structure and in turn making it easier to manage your app.
Does your web hosting have cURL enabled?
Theme-Desert saidI really don’t see what clarification you need. It’s written in black and white on the requirements page.
contempoinc saidNot stressed, just waiting on JAPH’s reply for clarification
Honestly think you’re stressing for no reason. It really doesn’t matter what all these different confused support staff are telling you, the newly posted req’s are correct.
you didn’t read my previous comments, before your 2 cents:
If you look on the requirements page under PHASE 2. It says it is only a DRAFT, and subject to feedback So it being a DRAFT, meaning that ENVATO SUPPORT is still sketching all the details out regarding PHASE 2.
I emailed ENVATO SUPPORT, if option pages need to go into a plugin since in their DRAFT it says Theme Option Frameworks. After several emails back and forth with support and the review team, they were telling me different from what was on the guidelines page. ENVATO SUPPORT told me that ANY additions and functionality to the theme will have to be refactored as plugin, that is not core. But that’s not until Phase 2 in November. So i contacted ENVATO SUPPORT to re-clarify and they checked with the review team again, and said the same thing. So after several days and several emails back and forth. I posted in this forum to ask JAPH regarding the confusion on how the requirements page show something different than what ENVATO SUPPORT tells you when you email SUPPORT. So JAPH asked me for my support ticket ID, (which i gave him). And he said he will look into clarifying with the support team about the differences of the requirements page, versus what Envato Support tell you.. so there is no confusion.
So the PHASE 2 guidelines are still a DRAFT and subject to change based on feedback.
I’d say with 99% certainty that theme options will obviously be in the theme. Clue is in the name, and as they only affect our own theme’s characteristics it’d be illogical to put them in a plugin.