|
sbabar
|
November 14, 2016 at 2:37 pm
We purchased a support license key today. Despite following instructions to delete the old key, save as blank, then enter new key and save, the plugins area of WordPress continues to display the following message:
A new version of Event Espresso is available. View What’s New with version 3.1.37.10.P. A valid Support License Key is needed to enable automatic upgrades. The key you have entered is invalid or has expired. Please log in to your Event Espresso account to manage your Support License Keys or purchase a support license right now.
|
|
Josh
|
November 14, 2016 at 3:10 pm
Hi there,
Your support license is actually for EE4. You can switch your support license to be for EE3 by selecting an EE3 license plan on your account page. You’ll find that selector on your account page, under “Switch Your Support License:”.
|
|
sbabar
|
November 30, 2016 at 9:19 am
Josh,
OK, my client’s credit card was charged an extra $28.63 (not sure why this was necessary) to convert to an EE3 license plan.
In spite of that, the license key number has not changed. And when I reopen WordPress and check the Event Espresso plugin, it still says “The key you have entered is invalid or has expired.”
I’m sure it is nobody’s intention to make upgrading Event Espresso such a miserable experience. However, it continues to be true that no other plugin I use causes me this amount of trouble (including free ones). I say this as a long-time user, hoping that you’ll more devote resources to debugging this process.
Now that I’ve vented a little, I just need to know soon you can fix this (or give me instructions on what to do that I haven’t thought of).
|
|
Josh
|
November 30, 2016 at 11:10 am
Hi there,
I can let you know that the license key number should not actually change when you change your account from an EE4 to EE3 license. I’m going to assign a new key to your account and remove the old key, can you try the new key? The new key is on your account page.
|
|
sbabar
|
November 30, 2016 at 12:50 pm
Josh,
Thanks for the reasonable response even after I got a little crabby. That worked.
Ken
|
