731 posts
  • Elite Author
  • Attended a Community Meetup
  • Has been a member for 4-5 years
  • Sold between 100 000 and 250 000 dollars
  • Bought between 50 and 99 items
  • Exclusive Author
  • Most Wanted Bounty Winner
+2 more
mordauk says




I always built auto-updaters into my plugins that I sold on Code Canyon and was never told I can’t. If TF does not allow it, then that should definitely change. You are also more than welcome to place your plugins in WordPress.org, which will automatically have an update system.

...so then everyone else in the world is free to use our plugins in their own themes (or whatever they like as it’s GPL) and profit off my hard work?

Good one.
Just saying it’s an option. If you do not want to share your plugin (which is fine), then include your own custom updater like @Astoundify mentioned. As far as I know TF does not prevent this, but if they do, it SHOULD be allowed.
I would say it’s likely allowed, the point I’m trying to make is that it shouldn’t be on authors’ shoulders to facilitate this kind of functionality.

Hey, I’m all for TF providing an easier updater solution.

5 posts
  • Sold between 100 and 1 000 dollars
  • Has been a member for 4-5 years
  • Bought between 10 and 49 items
  • Exclusive Author
  • United States
nhangen says





I always built auto-updaters into my plugins that I sold on Code Canyon and was never told I can’t. If TF does not allow it, then that should definitely change. You are also more than welcome to place your plugins in WordPress.org, which will automatically have an update system.

...so then everyone else in the world is free to use our plugins in their own themes (or whatever they like as it’s GPL) and profit off my hard work?

Good one.
Just saying it’s an option. If you do not want to share your plugin (which is fine), then include your own custom updater like @Astoundify mentioned. As far as I know TF does not prevent this, but if they do, it SHOULD be allowed.
I would say it’s likely allowed, the point I’m trying to make is that it shouldn’t be on authors’ shoulders to facilitate this kind of functionality.
Hey, I’m all for TF providing an easier updater solution.

In implementing these standards, they probably need to place a little bit of the burden on themselves and do exactly that.

90 posts
  • Elite Author
  • Sold between 250 000 and 1 000 000 dollars
  • Bought between 100 and 499 items
  • Exclusive Author
  • Has been a member for 4-5 years
  • Referred between 200 and 499 users
  • South Africa
Net-Labs says

@nhangen

Great to see you. Did not know that important people also frequent the forums.

Not even place a burden, just allow me to put my functionality in a seperate folder and prove to them that the theme works 100% without my code or allow my “plugin” to be activated as a function and not the usual plugin way.

no need to reinvent the wheel.

1999 posts
  • Elite Author
  • Sold between 250 000 and 1 000 000 dollars
  • Author had a File in an Envato Bundle
  • Has been a member for 5-6 years
  • Author had a Free File of the Month
  • Won a Competition
  • Bought between 10 and 49 items
+4 more
bitfade says

But you still have to update each theme independently when you make changes to the framework.
this is leading nowhere. Plugin or whole theme, end users would still need to update and, so far, only themes can be updated via envato api.
615 posts
  • Power Elite Author
  • Referred more than 2000 users
  • Power Elite Author: Sold between 2 000 000 - 4 999 999 dollars
  • Austria
  • Bought between 100 and 499 items
  • Has been a member for 5-6 years
+4 more
Kriesi says
Most of the discussion here is simply the result of bad communication by Envato if you ask me. The draft for those rules was available months ago and was sent to some authors for feedback. This is part of what I provided as feedback:

Rule: Plugins should be included via the TGM Plugin Activation class

Something which needs clarification I think. I will bundle the layerslider plugin with my next theme. I consider it much better user experience if it is included in a way that the user doesnt need to do anything to have the functionality available. So what I would suggest:
  • if a plugin can not be included directly into the theme (eg WooCommerce, too complex to call directly) the TGM Plugin Class needs to be used
  • if a plugin can be included directly because it was designed that way, the TGM Plugin class should not be required. BUT: the theme author needs to make sure that if the user has the plugin already installed or installs it later on, that the theme-included plugin no longer is used.
I have used this method for all of my previous themes and customers liked that behavior a lot, since it allows them to update plugins on their own without any problems, yet the still get what the buy, from the moment they activate the theme.

Rule: Inadmissible shortcodes:

If I am allowed to add this functionality with a plugin that is included the way I described it above? then I am ok with that.


I still think this makes sense and I think if it would have been added to the requirements this thread would probably have 15 pages less :P
731 posts
  • Elite Author
  • Attended a Community Meetup
  • Has been a member for 4-5 years
  • Sold between 100 000 and 250 000 dollars
  • Bought between 50 and 99 items
  • Exclusive Author
  • Most Wanted Bounty Winner
+2 more
mordauk says

That works really well, @Kriesi

90 posts
  • Elite Author
  • Sold between 250 000 and 1 000 000 dollars
  • Bought between 100 and 499 items
  • Exclusive Author
  • Has been a member for 4-5 years
  • Referred between 200 and 499 users
  • South Africa
Net-Labs says

@kriesi

that’s all that I ask. if that can happen i’ll be a happy camper.

Thanks for your support on this.

30 posts
  • Sold between 1 000 and 5 000 dollars
  • Has been a member for 3-4 years
  • Bought between 10 and 49 items
  • Europe
  • Exclusive Author
nilz_w says

Holy S*, I stopped reading at around page 18… I think Envato has to consider a lot of the authors criticism and than make a clear statement of where they are heading with the new upload requirements. A lot of people, me included, seem to be confused.

31 posts
  • Elite Author
  • Sold between 50 000 and 100 000 dollars
  • Has been a member for 1-2 years
  • Europe
  • Exclusive Author
  • Referred between 50 and 99 users
  • Bought between 50 and 99 items
lollum says

Ok, I can include my page builder functionality with a plugin. But if I want to use a page element in a theme and this element will not be used in another theme? How can I do this? A different “page-builder-plugin” for every theme?

7 posts
  • Bought between 1 and 9 items
  • Exclusive Author
  • Has been a member for 3-4 years
  • Serbia
WPCanyon says

Ok, I can include my page builder functionality with a plugin. But if I want to use a page element in a theme and this element will not be used in another theme? How can I do this? A different “page-builder-plugin” for every theme?

No, just make the plugin a bit flexible. Take add_theme_support() for example, you can activate certain features in the theme but not required to, just do the same thing for the page builder plugin.

by
by
by
by
by
by