' This is not convenient for the developers because they need a fast active server with the capacity to serve many clients (more $ to spend on their side) but many developers are doing this to avoid piracy.'Īgain, this is just me and the fact that I run my site with 40+ plugins. Examples are Snip, Ali2Woo, WP Robot, FS Poster, and many others. They are really selling a service but through a plugin that really works as a portal (SaaS - Software as a Service) for such a service. ' A hint for the plugin maker: partially move the functionality of the plugin to your server, which will check the license towards the customer database.' I really prefer a more silent and faster method of nulling plugins, but that is just me. Some will also nag with other messages like 'verify your license'. Will nag you with the 'update available' as soon as an update is rolled in.ĥ. It all will be recorded in their statistics and errors will be eye-catching on that report.Ĥ. Will notify the developers who are using it and in which specific website(s) and IPs.

It has many checks for the license before doing many tasks.ģ. Some functions that check connection and license are called multiple times throughout the plugin's other functions. This translates to a slower website and it is looked as a bad SEO score for having too many PHP requests to other server(s).Ģ. Some plugins are programmed to retry many times when an error is found (like no real credentials). Will try to connect to an external server to check the license and check for updates.

It will not obstruct the plugin work, but:ġ.

It is leaving out the update functions and all other functions that could make a call to the developer's server. Yes, that will work, but here are my 2 cents.

Codecanyon purchase code crack