I have a worse problem, when i’m around to 90% pop in my head some new idea and start to work to another plugin saying “Ok finish the other one when have the structure for this one before i forget it…” and at the end have 100 plugins at 90%
Hello, i’m allowed to make a free and premium version of a my item and put the premium one on envato?
I’m doing like this: Let’s say i have a team showcase plugin which use CPT. Now i can not integrate it in my themes and have to move it as standalone plugin. So let’s call the plugin “webcaos-team-showcase”. I provide the plugin with a basic template/styling, so if a user switch theme the plugin will continue to work without problems even if will not be styled as the same way of the new theme. But i provide the chance to override the plugin’s template in the same way a child theme override his parent, so creating in the new theme a folder called “webcaos-team-showcase” you will have a “child” template for the plugin’s template, and each matching file inside this folder will override the plugin’s main template, exactly at the same way of child themes. In this way a user could easily edit the plugin for make it looking good with the new theme without the risk to break the plugin, and at the same time offer an easy chance to other authors to support my plugin in their themes. I think this would be a good standard for all envato authors, and i’m even up to open some rep on github for create some of these basic plugins to be used in envato themes.
But speaking about doubts i would like to have some clarification from envato staff about metaboxes for standard posts, there is no way for these to guarantee a compatibility with other themes so i guess they should stay in themes and not in plugins even if they store data.
Today had my first small sale, but still be the first milestone! Just wanted to share with you all
Weel, i think shortcodes related to the plugin have to stay in the plugin. What i understood about phase two is this: Themes have to be related to the styling of the “website” without add new functionality to WP, unless the functionality is styling related (See Option Panels or default wp galleries styling, etc.). All what add new functionality to WP have to stay in a plugin, and after all is for this reason if WP have “plugins” and “themes”, are two different things, one have to think at the website styling and the other one have to add new functions on top of it
How about custom meta boxes? I make a large use of CMB in my themes, for insert videos, define sidebars, layouts, labels, custom comments templates slideshows, and everything related to posts and pages. Not use shortcodes at all in them but just custom functions. Is this allowed?
Hey there, probably the question is kinda dumb I’m developing a WP theme to sell in here, and i’m using my own framework based on bootstrap. Included in my framework i have a gpl framework for options(heavily custmized) and a gpl meta boxes framework for speed up the developing . The question is: I’m allowed to include these framework on my theme or violate some rule?
Thanks in advance for answers guys