What if I use Visual Composer plugin for shortcodes (elements) and want to override some default shortcodes with mine? Do I need to create an additional plugin just for that overriding stuff?
Wow! It looks very promising. Would definitely give it a try. Thanks for sharing!
That’s fast! Congratulations!
I’ve been using OptionTree in my theme and noticed that any custom fields of the meta box won’t be saved along with the WP autosave function. When I review the revision and restore the post, all data of the custom fields are gone. Could you please advise how to fix this?
This still doesn’t make sense for me. The whole idea of using plugins is so if/when the user decides to change themes, the functionality from the plugins will still remain. What if these plugins are only tailored to the theme it was purchased for? After the user switches themes a few times, they will have a huge clutter of useless plugins installed.
Hmm. I’m wondering the same thing. Also, supposed a user switches the theme from Kriesi’s to Peerapong’s then s/he will have all plugins of both authors installed which perhaps perform the similar tasks? Sounds strange.
@nagaemas, @carlhancock – Thanks for clarification!
I have a question: By using plugin for functionality, if I have 2 portfolio features for 2 themes and both portfolios are totally different in functions, it means that I need to create 2 separate plugins for each portfolio as well? Then I need to use TGM to point to the plugin zip that bundled with the theme. Am I correct about this?
Does the whole concept mean to just moving any functionality into the plugin? Just like that?
mordauk saidBut if all theme’s functionality need to rely on the plugins, I’m wondering how can theme authors push their ideas and creativity to the edge?
The mentality that “Standards” mean you can’t be creative is so horribly wrong. By embracing standards, theme and plugin developers can build things that work in tandem instead of constantly fighting conflicts.
Just because major functionality needs to be in a plugin doesn’t mean you can’t create your own plugins.
For example, if your theme is based around major portfolio features (filtering, categorization, grids, galleries, etc), build a portfolio plugin that is built specifically with the features you want, then style / implement the features provided by the plugin in your theme.
Just because the code exists in a plugin doesn’t mean you can’t be creative. The code is the same no matter where it exists.Also by placing your major features in a plugin, you can really easily include those features in all of the themes you build. Update the plugin once and all of your themes have the update. So much easier to maintain.
Thanks for your clarification.
Anyway, I still have some concern because by doing that, most authors will release their own plugins for their own creativity right? Wouldn’t it be a problem or strange when there are 1000 plugins by 1000 authors? Also I don’t think many authors will use other authors’ plugins to create such functionality because what they need is uniqueness (I’m not talking about generic elements like contact form or button but the unique functionality of the theme). What is your opinion on this?