If a feature (such as a CPT) needs to exist with and without the theme, then you just register it globally, regardless of what theme is active.
> I’d suggest taking a look at the work Mike McAlister does: http://themeforest.net/user/mikemcalister – He uses a single “Okay Themes Toolkit” plugin that houses all of his functionality, and each of his themes is very unique.
What happens if:
1.) His users only install theme and not the plugin 2.) His users go to another theme leaving plugin installed
I’m interested in how he handles that.P.S. Maybe that could be a topic in the new episode of Please Advise
If the plugin that provides a certain feature isn’t active, then the theme should act as a standard theme. In the context of this whole discussion, the theme would act as a “simple skin”, but then when the plugin is activated, the advanced features become available.
Excuse me mordauk but what you are saying is totally against to creativity’s basic rules. Those mentioned themes remain unique? in which way ? Are you a designer? Seems we’re in different sides. Creating something trully unique can’t be done with a single plugin you’ve made. I’ve been reading this thread since the begining. I’m totally agree with FinalDestiny. As a designer I don’t want to be stuck in boudries. I want to bring something fresh and complete solutions on the table and I don’t think I can do this with you way. just thinking outloud.
Show me an example.
I’m specifically talking about functionality. For portfolios, this means grids, sorting, dynamic filtering, etc. These are all features that can be included globally via the plugin, but the exact implementation and style of these features can be as unique as you want.
I’d suggest taking a look at the work Mike McAlister does: http://themeforest.net/user/mikemcalister – He uses a single “Okay Themes Toolkit” plugin that houses all of his functionality, and each of his themes is very unique.
You didn’t understand my question. Let’s say I’m just starting and I’m creating a plugin for the first theme. But the second theme is a real estate theme. And real estate themes have their own features and shortcodes, different than the first theme(that doesn’t need the real estate features). And maybe the real estate theme uses the pricing tables in a different way than the first theme. What’s to be done then? I’m talking about shortcodes here. Since we’re not plugin developers, we can’t create an extremely complex plugin to cover, for example, all the portfolio possibilities, we only create what we need for a specific theme. When a new portfolio theme comes in the discussion, we re-review what we have in the current plugin and discover we need some new features / functions / etc. So in the end we basically need a new plugin for each theme, which is extremely bad and very hard to maintain.
Ultimately I’d suggest that you have one plugin for each major “kind” of functionality. Create a plugin that handles all of the features needed by your real estate themes; create a plugin that handles all of the portfolio features. When you do that, you can use the plugin in one theme or in 15 themes. You can also mix and match them.
If you’re able to create those features in a theme, it’s really not hard to move them into a plugin. The code is identical, only the location is different.
mordauk, I got your point. Now, let me ask you a question. Not only to you, but to all the other that think this is a progress.
Me, as a developer, I may work with different designers. I don’t like doing the same blog theme over and over again with just a different face, but I like doing niche themes. Like, a restaurant theme, a one-page theme, a real-estate one, etc. Each one of those themes has different shortcodes. One may have a simple portfolio with not so many details while maybe another portfolio theme has lots of options and stuff related to the portfolio niche.Having one plugin globally used in all the themes simply doesn’t work. This may work for bigger companies like WooThemes, ElegantThemes that use the same principles and overall style in all the themes, but tell me how should I proceed in the above case? One plugin per theme? That’s definitely not productive and hard to maintain.
Using the same plugin over and over again actually does work exceptionally well. Just because it’s the same plugin doesn’t mean it can’t be unique.
There are many ways to turn features on/off that are provided by a plugin, and you can easily do this in your theme.
Just as an example, look at the WooCommerce category: http://themeforest.net/category/wordpress/ecommerce/woocommerce
Every one of those themes uses the exact same plugin to provide 99% of the functionality, yet each theme can still remain unique.
Whether you are using WooCommerce, another GPL or commercial plugin, or your own custom plugin, you can do the same thing.
“since when do the plugin developers make rules for us, the theme developers?”. Time to get off your high horse and gain a little humility. Plugin developers don’t make rules for theme developers and theme developers don’t make rules for plugin developers. The community builds rules and guidelines for everyone.
“The commuity” being the WordPress community?Envato isn’t bound to the WordPress community’s rules, nor do they have any obligation (as far as I am aware) to adhere to the community guidelines set out by the WordPress community.
Yes the WordPress community.
If you think you can sell a WordPress product (on any market) and completely ignore the larger WP community, you will have a rude awakening one day.
carlhancock saidYou can claim to have a lot of experience, but you aren’t showing much business nous.
You guys do understand that a theme is precisely a skin, right?
It’s been bastardized into what’s it’s become by theme authors that want to cram every feature under the sun into the theme. That was not the original nor the current intention of a WordPress theme.The theme is supposed to be the design layer of the site. The skin. They could have just as easily called them skins but they went with the term theme. Why do you think plugins exist?
Hehe, sorry to laugh, but Carl Hancock has probably made more money on Gravity Forms that the top 20 authors combined, perhaps more. No one can claim he doesn’t know business.
If you’d like to see a few examples of authors that have fully embraced both the standards AND the plugin functionality, take a look at these guys:http://themeforest.net/user/mikemcalister?WT.ac=search_profile&WT.seg_1=search_profile&WT.z_author=mikemcalister http://themeforest.net/user/ThemeBlvd?WT.ac=search_profile&WT.seg_1=search_profile&WT.z_author=ThemeBlvd http://themeforest.net/user/WPExplorer?WT.ac=search_profile&WT.seg_1=search_profile&WT.z_author=WPExplorer
“since when do the plugin developers make rules for us, the theme developers?”.
Time to get off your high horse and gain a little humility. Plugin developers don’t make rules for theme developers and theme developers don’t make rules for plugin developers. The community builds rules and guidelines for everyone.
I won’t go into detail on this, but I really believe that one of the reasons buyers want the all-in-one-solution is because we have conditioned them to think they do.
This is definitely not true across the board, but in general I think it’s true.