373 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Located in Australia
+4 more
Japh says

Japh, look at my badges, I’m an author, I know about all this stuff and I won’t pirate my own themes. I’m talking about the same people that ‘share’ our themes on warez sites.

I see your badges (and you’re from Poland! I’ve always wanted to visit Poland!)

I think people who pirate themes are most likely quite happy with their own methods rather than using our plugin and handing out a trackable API key. At least if they pirate with an API key, we can simply revoke it.

177 posts
  • Has been part of the Envato Community for over 3 years
  • Has referred 10+ members
  • Has sold $5,000+ on Envato Market
  • Has collected 50+ items on Envato Market
+1 more
xdkd says

Well, updating pirated theme used to be somewhat of an issue for illegitimate users, now you are basically making it easy for them, and also provide no incentives for “legitimate” users to actually honor license terms and buy multiple licenses if they need to deploy on several sites. I think this can definitely be a source of author’s concern. Also, given the amount of customizations users generally perform, overwriting all files seems like a bad idea anyway.

373 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Located in Australia
+4 more
Japh says

For those who were having problems with the their username and API key in the plugin, this issue has now been fixed. If you download the plugin again from GitHub, at version 1.2, everything should work for you.

Thanks again for the detailed error report, and please let us know if you have any further issues :)

119 posts
  • Has been part of the Envato Community for over 6 years
  • Has referred 50+ members
  • Has sold $75,000+ on Envato Market and is now an Elite Author
  • Had an item featured in an Envato Bundle
+8 more
valendesigns Envato team says

Hey Guys,

Sorry for any frustration I caused with the API connection bug! During the name changes made in v1.1 I inadvertently made a very small alteration to the register_settings arguments. I was not aware of the bug because I had already made an API connection previous to the update. It’s been fixed and you will not have trouble connecting to the API with a proper username and api-key now.

22 posts
  • Has been part of the Envato Community for over 4 years
  • Has collected 10+ items on Envato Market
  • Sells items exclusively on Envato Market
  • Located in Japan
halogenic says

Many thanks. It’s working for me now.

It’s a great idea – makes updates so much easier.

IndustrialThemes
IndustrialThemes Recent Posts Threads Started
153 posts
  • Has sold $500,000+ on Envato Market
  • Has been part of the Envato Community for over 6 years
  • Has collected 100+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+6 more
IndustrialThemes says

I run a multisite network and when I install the plugin and click Save User Settings on the Envato Toolkit page I get the following error:

The requested URL /wp-admin/network/options.php was not found on this server.

3503 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $750,000+ on Envato Market
  • Located in United States
  • Helps us moderate the forums
+10 more
sevenspark Moderator says



We now have a plugin for WordPress that will show you when a theme you’ve purchased from ThemeForest has an update available. You can then choose to automatically download and install the update. Even better than that though, the plugin will show you all the WordPress themes you’ve purchased on ThemeForest, and allow you to install them too.

Doesn’t this violate the license?

If I buy ten themes and install the plugin on ten sites won’t it appear that I can use install all themes on all sites? In reality you need 100 licences.

Seems like this will cause confusion. Buyers already don’t have to disclose the URL of their project so authors can verify legitimate license usage. I think this needs more thought.
Hey GravityDept, the plugin itself does not violate the license in any way. As it has always been, it is a user’s responsibility to ensure they do not install a WordPress theme on more sites than they have license to do so. That still applies, whether they are using this plugin or not.

I agree that this will cause extra confusion on an already confusing issue for some buyers. I believe that a large number of customers are unaware of licensing restrictions (either because they don’t take the time to read them, don’t understand them, or make inaccurate assumptions based on the licensing options from other theme vendors which may be more lenient), and for those customers it will seem that this plugin gives them tacit permission to install the theme on any of their sites, as many times as they want (it’s reasonable to conclude that if a piece of software provided by a company allows me to do something – i.e. download a product to multiple sites – that I’m within my rights to do so. Otherwise, it would be restricted, right?)

For the customers who understand the license, they will either choose to follow it or not – and there’s nothing we can do about that (via this plugin at least), so it doesn’t concern me. What does concern me is confusing buyers who are already unsure of their usage rights after purchasing a license. I have had plenty of customers using a product on several sites, and once I asked for their licenses, they were surprised to hear that they were doing something wrong.

Basically, I think it’s a mistake to assume that all customers understand the licensing; and therefore it’s a bigger mistake to indirectly (and inadvertently) imply that multiple installs of a single-use license is acceptable. I think some basic DRM needs to be implemented before this becomes official – even if it’s just a simple alert rather than a programmatic restriction: “You have already installed this theme on another site, please note that each license is single-use”. Not trying to be negative, but I think it’s important to have this conversation before things are made “official” :)

Also, separate question: is this compatible with plugins (CodeCanyon)? If not (I assume it’s not), is that an intended feature down the road?

Thanks for your hard work, guys! We all just want to make sure that these solutions don’t have too many negative side-effects :)

To address another point, I believe there is some confusion here (re: @dyspersion) – I think that uploading the separate theme file will now be mandatory, however integrating the library is not yet a requirement. Is that correct? The former makes sense, the latter wouldn’t.

Thanks!

Chris

1055 posts Best-dressed man at PressNomics 2013
  • Has sold $1M+ on Envato Market and is now a Power Elite Author
  • Power Elite Author: Sold more than $1M on Envato Market
  • Made it to the Authors' Hall of Fame
  • Had an item featured on Envato Market
+10 more
Parallelus says

It would be helpful if you can clarify what is mandatory if anything.

I estimate I’ve had 10 requests in the last 3 years for automatic updates. As far as I’m concerned this is not even close to a top priority for the marketplace. It feels a lot like a waste of resources unless there are future plans related to this which I’m not aware of.

The current system protects against overwriting modifications. Not to generalize too much, but most WP users aren’t all that knowledgeable when it comes to coding. If they make a customization it’s likely they won’t realize it can be wiped out by 2 clicks to update the theme. This is further exaggerated when a developer uses a theme and turns it over to a client.

For the time being, if we’re not forced to participate in this, I would rather not. Over time I might test it with new themes but currently I feel the system we have is working. Put an automatic backup/restore system in place along with the update and I’m all in. :)

373 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Located in Australia
+4 more
Japh says

I run a multisite network and when I install the plugin and click Save User Settings on the Envato Toolkit page I get the following error: The requested URL /wp-admin/network/options.php was not found on this server.

Thank you for reporting this. We’ll look into it and get back to you.


I agree that this will cause extra confusion on an already confusing issue for some buyers. I believe that a large number of customers are unaware of licensing restrictions (either because they don’t take the time to read them, don’t understand them, or make inaccurate assumptions based on the licensing options from other theme vendors which may be more lenient), and for those customers it will seem that this plugin gives them tacit permission to install the theme on any of their sites, as many times as they want (it’s reasonable to conclude that if a piece of software provided by a company allows me to do something – i.e. download a product to multiple sites – that I’m within my rights to do so. Otherwise, it would be restricted, right?)

For the customers who understand the license, they will either choose to follow it or not – and there’s nothing we can do about that (via this plugin at least), so it doesn’t concern me. What does concern me is confusing buyers who are already unsure of their usage rights after purchasing a license. I have had plenty of customers using a product on several sites, and once I asked for their licenses, they were surprised to hear that they were doing something wrong.

Basically, I think it’s a mistake to assume that all customers understand the licensing; and therefore it’s a bigger mistake to indirectly (and inadvertently) imply that multiple installs of a single-use license is acceptable. I think some basic DRM needs to be implemented before this becomes official – even if it’s just a simple alert rather than a programmatic restriction: “You have already installed this theme on another site, please note that each license is single-use”. Not trying to be negative, but I think it’s important to have this conversation before things are made “official” :)

I really appreciate your feedback. We’ll give this some further thought and see if we can come up with a good solution.


Also, separate question: is this compatible with plugins (CodeCanyon)? If not (I assume it’s not), is that an intended feature down the road? Thanks for your hard work, guys! We all just want to make sure that these solutions don’t have too many negative side-effects :)

Currently this only works for themes on ThemeForest, but yes, we do intend to add support for plugins from CodeCanyon down the road too.


To address another point, I believe there is some confusion here (re: @dyspersion) – I think that uploading the separate theme file will now be mandatory, however integrating the library is not yet a requirement. Is that correct? The former makes sense, the latter wouldn’t.

Ah, well picked up. You are correct, it is only uploading a separate theme file that is now mandatory. Use of the plugin and/or library is not mandatory.


It would be helpful if you can clarify what is mandatory if anything.

I estimate I’ve had 10 requests in the last 3 years for automatic updates. As far as I’m concerned this is not even close to a top priority for the marketplace. It feels a lot like a waste of resources unless there are future plans related to this which I’m not aware of.

The current system protects against overwriting modifications. Not to generalize too much, but most WP users aren’t all that knowledgeable when it comes to coding. If they make a customization it’s likely they won’t realize it can be wiped out by 2 clicks to update the theme. This is further exaggerated when a developer uses a theme and turns it over to a client.

For the time being, if we’re not forced to participate in this, I would rather not. Over time I might test it with new themes but currently I feel the system we have is working. Put an automatic backup/restore system in place along with the update and I’m all in. :)

Hopefully I’ve clarified this above on what is mandatory.

Perhaps we could implement some kind of warning for users when an update is available to let them know any customisations will be lost. I think this needs some more thought also.

1058 posts It's in the pipeline!
  • Has sold $500,000+ on Envato Market
  • Has been part of the Envato Community for over 6 years
  • Elite Author: Sold more than $75,000 on Envato Market
  • Sells items exclusively on Envato Market
+7 more
purethemes says

Ah, well picked up. You are correct, it is only uploading a separate theme file that is now mandatory. Use of the plugin and/or library is not mandatory.

Good, I have similar thoughts about this as Parallelus. I’m happy something moved on with that problem, I just prefer to wait until this will be 100% ready and bulletproof.

Also I’m not sure it’s the best solution, I always thought that simple notification by sending email to buyers after theme is updated would be enough. As most of themes are bought by developers and then sold to their clients, it would be their job to update it, and they would be the ones who get email with update info. With my limited imagination I can’t think of solution good enough to not confuse many users.

Helpful Information

  • Please read our community guidelines. Self promotion and discussion of piracy is not allowed.
  • Open a support ticket if you would like specific help with your account, deposits or purchases.
  • Item Support by authors is optional and may vary. Please see the Support tab on each item page.

Most of all, enjoy your time here. Thank you for being a valued Envato community member.

Post Reply

Format your entry with some basic HTML. Read the Full Details, or here is a refresher:

<strong></strong> to make things bold
<em></em> to emphasize
<ul><li> or <ol><li> to make lists
<h3> or <h4> to make headings
<pre></pre> for code blocks
<code></code> for a few words of code
<a></a> for links
<img> to paste in an image (it'll need to be hosted somewhere else though)
<blockquote></blockquote> to quote somebody

:grin: :shocked: :cry: Complete List of Smiley Codes

by
by
by
by
by
by