Support

February 15, 2014 at 10:29 am

Hi – our license key system has been designed to prevent abuse of the one-click update system and to enforce our support license which entails support of one production domain install of Event Espresso per license key. This current setup has been carefully thought out because we want to balance the cost to us for providing support with ease of use for users. In order to keep the cost of the product down for everyone these are the necessary measures we’ve put in place.

With that said:

License keys are NOT required to ‘activate’ the product so you are able to use Event Espresso on multiple development/staging servers.

For professional/commercial applications, we are aware that the convenience of one-click updates does help when you have implemented an environment that involves development, staging and production servers. One option we do have for companies such as yours, is access to our private github repo. You can apply for access here. With this access you can link your development and staging servers to the master branch of the repo and ensure that you are up to date that way. Another suggestion would be to keep your development server on the related ‘beta’ branch and that way you’d be able to test upcoming versions as a part of your workflow. Then you can use the license key just to have updates on your production server (or even use git there too if you wish).

We currently use git for all our test deploys and have found its a very useful tool. Hopefully it will be useful in your situation as well. If you choose to go this route, when you apply for github access, reference this thread and that will accelerate our response.