- This topic has 1 reply, 2 voices, and was last updated 7 years, 11 months ago by
.
-
Posts
-
What sort of malicious behavior could this feature possibly prevent? Currently, it’s only preventing me, a paying customer, from being able to conduct the plugin updates I need to in a staging environment.
I have a purchase code for use on a single site. The search function has completely stopped returning appropriate results on said site. The plugin is out of date. I would like to update the plugin to see if this resolves the issue. Ideally, I would do this first on the staging server, to make sure nothing causes even worse breakage as a result of the update. Assuming everything goes well, and the update resolves the issues on staging, I’d like to be able to deactivate the license on staging, and install it on live so that I can then update the plugin on live.
I’m now locked out and unable to update the plugin on either environment.
This type of thing is why people invented piracy. Or, in this case, open sourcing.
Hi,
It prevents misuse of shared purchase keys. Without that, anyone could use a single key on unlimited sites, as well as pirated copies to be obtained via API calls from our servers. While it is not hard to obtain a pirated copy of any software these days, there is no guarantee that those copies does not contain any malicious code (which they usually do). Without this limitation, direct links could be shared for download to the update servers.
I understand that this can be very inconvenient, but it rarely causes any problems, as most staging environments are directly pushed to the live environments.
You can also download the latest copy from codecanyon anytime, it is exactly the same copy as on our servers. Actually, the codecanyon copy is always approved first, before we push the updates to the update servers.
Updating the plugin manually is not different from the WordPress auto-update method, it is essentially the same. WordPress uninstalls, deletes then installs the new version. The same method is used when installed/updated manually, although it is more convinient using the auto updater of course.
Also, you don’t have to have the plugin automatic updates activated at all, it does not lock any other features. In your case, I would recommend using the automatic updates on staging, and using the manual update method on the live environment, once it is surely working.
I am sorry for the bad experience, I hope I can improve this somehow in the future.
- The topic ‘30 Minute lock out period following deactivation is infuriatingly unhelpful’ is closed to new replies.