I think there are many interesting aspects of this topic. I’ve seen both good arguments against it and for it.
I might be prejudiced because we already created a plugin, which allows theme authors on Themeforest to implement the plugin into their theme and then offer new flexibility for add-ons to their theme. And it allows authors on Codecanyon to create add-ons for the main plugin.
We currently work with two theme authors on Themeforest, one who already purchased an extended license and the other will soon – to incorporate the plugin into their theme.
They will then add their own Shortocdes and we will also be able to develop add-on (new features) that easily can be added, because of the main plugin that is incorporated. We simple “white-label” it so our name won’t occur under plugins or it won’t show up under plugins, but its a core feature. Only in the readme.txt would it be mentioned that an Extended license has been acquired for our plugin to incorporate certain functionality.
I hear some authors saying they don’t want other authors to build add-ons unless they agree on it. I don’t see the big problem. We build our plugin because we wanted other authors to take advantage of this and build add-ons.
If you don’t want other authors to build add-ons to your plugin then you simply don’t offer a API that would allow it.
Of course there is also the question about support. My opinion is that the developer of the plugin (add-on) should support their own work. Of course as the author of the main plugin I’m interested in seeing the add-on work.
I another thread someone suggested that we could offer support subscriptions. There are many possibilities.
Great to see so many authors engaged in this. We all want to see the Envato market places become even better than they already are.
Is the item being stolen from a Envato Market place and sold somewhere else ?
Take a look at these articles http://wiki.envato.com/support/what-to-do-if-you-have-found-your-marketplace-files-being-distributed-or-used-illegally/http://wiki.envato.com/selling/copyright-selling/copyright-policy/
I’ve worked with WordPress for several years and recently started developing premium WordPress plugin on Codecanyon. When you say WordPress plugin usually its a script (plugin) that is installed under plugins and then it has some settings in the wp-admin. Some plugins have their own entire menu and sub-menus with lots of settings and other just have a simply configuration panel (settings).
Common for them would be that they can easily be used in WordPress from the wp-admin when you compose your Posts or Pages. Or configure the content of your widgets, menu’s etc.
I haven’t seen any plugins where you will have to access a external website if that is what you had in mind.
I don’t know if this made any sense, but if you give an example of what you had in mind it might be easier to provide some real advise
Hi Jeffrey, Great idea!
I’ve been an exclusive author since March 2009.
I have a few items I would like to offer the following:
Styles with Shortcodes for WordPress
Launched: November 29, 2010
Rating: 5 Star
URL : http://codecanyon.net/item/styles-with-shortcodes-for-wordpress/142221
White Label Branding for WordPress
Launched: September 17, 2010
Rating: 5 Star
URL : http://codecanyon.net/item/white-label-branding-for-wordpress/125617
These items can be found in my Portfolio: http://codecanyon.net/user/lawley/portfolio
We already offer first class support, so that should not be a challenge.
ive bought all your items from the cc marketplaceyou do execellent work, i would love to know your rates.
feel free to contact me through my personal profile and we can talk about it. It all depends on the scope of the project and what type of project.
I would also be in both categories.
However I talking about this from producing WordPress plugins where they user only needs to “activate” the plugin and then do no more.
So I guess the two situations are quite different. With a WordPress plugin if it solves the same purpose I would always just create an upgrade.
I hope I didn’t just repeat my self, but made it more clear
Some of my plugins are already in version 2.0.2 and have had major changes since the beginning. However I have not launched a new version which the client needed to pay for again in order to get the new features.
Unless the plugin suddenly does satisfy a totally different need then I would not launch a new version and charge money again. We specialize in WordPress plugins and there are thousands of free plugins for WordPress, so if you want to create something that you expect client to pay for you need to support your plugin.
A happy customer will gladly buy from you again. A unhappy customer will never buy from you again. That is my philosophy when it comes to plugin development.