I have a suggestion.
So, according to new Submission Requirements, functionalities such as widgets, CPT, shortcodes etc. should come as seperate plugins. By doing this, users will be able to preserve their data after switching from one theme to another. However, since there are hundreds of different plugins for each functionality, most of the time user wont be able to just install their new theme and use old data right away.
So, here’s my suggestion. Envato (as an authoroty) posts a public list of most common or endorsed plugins and authors make their theme compatible with those plugins. That way, when user switches from one theme to another, he/she can not only keep their data, but they can start using it right away. And authors can focus on creating themes, instead of constantly reasearching the market to comply their themes for every slightly popular plugin out there.And yeah, that way we can avoid authors who participate in “who can support more plugins” competition and therefore overblow their themes with templates and css code, as we all know, this is bound to happen.
This is a horrendous idea. It would limit the creativity of the authors to the functionality in those plugins, thus making all themes (in terms of functionality) pretty identical.
Experiencing a very strange issue on a theme we’re working on. If you search (using WordPress’ default search) and it returns results… all is well, $post is set normally and there are no problems.
Then when I try throwing in a search term that returns no results, all hell breaks loose. Even in the header file, trying to access the global $post variable doesn’t work and returns NULL. Same for the top of the functions file, it’s NULL at that point.
I’ve tried commenting out includes/blocks of code with no luck, as far as I’m aware only bits in the functions file would be called and I removed everything (exc. options framework) from my functions file and tried that and still the global $post variable is NULL.
I’m hoping someone has had a similar issue and has some pointers! As a note, I’ve tried the standard wp_reset_postdata() etc. functions and that’s not fixed it either.
As a final test I tried removing everything from the functions file, simply declaring the global $post; and trying to var_dump() that and still it’s NULL. It’s truly bizarre!
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?