|
Craig Ferguson
|
October 6, 2014 at 11:39 am
Good Day,
I have recently purchased Event Espresso and it now says there is an update, but I am unable to update, and there is a message:
“Please log in to your Event Espresso account to manage your Support License Keys or purchase a support license right now.”
Any assistance would be appreciated.
|
|
Tony
|
October 6, 2014 at 11:50 am
Hi Craig,
What version of Event Espresso is the site currently running?
If you go to Event Espresso -> General Setting. Scroll down to the bottom, is the support license key currently within the Support License field?
|
|
Craig Ferguson
|
October 6, 2014 at 11:59 am
Hi I am running Event Espresso – 3.1.36.5.P
Yes the key has been entered.
I am also getting an odd error within the Event Espresso pages:
“Warning: TableTools 2 requires DataTables 1.9.0 or newer – http://www.datatables.net/download”
I am assuming the updated version will fix this.
Thank you for your swift response.
|
|
Lorenzo Orlando Caum
|
October 6, 2014 at 12:20 pm
Hi Craig,
I’ve just reset your Support License Key. In a few minutes, you’ll receive a confirmation to your email address on your Event Espresso account.
If you are using Event Espresso 3, please login to your WordPress admin and locate Event Espresso in the admin menu. Then click on General Settings. Scroll down to the bottom of the page and locate the area for Support License. Now copy the existing key. Then erase the existing key and click on Save Options. After the page refreshes, scroll back down to the Support License area and paste your support license key and click on Save Options.
These steps will refresh your Support License Key for Event Espresso.
Let us know if you are able to update.
—
Lorenzo
|
|
Craig Ferguson
|
October 6, 2014 at 1:00 pm
Thank you this worked.
I have run the updated but I still receive the modal dialog box that says:
“Warning: TableTools 2 requires DataTables 1.9.0 or newer – http://www.datatables.net/download”
Should I open a new thread for this?
|
|
Lorenzo Orlando Caum
|
October 6, 2014 at 1:20 pm
Could you capture a screenshot of where you are seeing this and then upload to WP Media or a free service like getcloudapp.com or tinygrab.com and link to it here?
—
Lorenzo
|
|
Craig Ferguson
|
October 6, 2014 at 2:03 pm
You should be able to see them here:
http://imgur.com/a/6aqbm/all
|
|
Lorenzo Orlando Caum
|
October 6, 2014 at 2:57 pm
Thanks. I’ve not seen those before so I’m checking with some team members for some feedback.
—
Lorenzo
|
|
Lorenzo Orlando Caum
|
October 6, 2014 at 3:11 pm
Do you see the same thing appear when only Event Espresso and add-ons are activated?
If not, could you reactivate a few plugins and a time until this issue appears again?
—
Lorenzo
|
|
Craig Ferguson
|
October 7, 2014 at 7:34 am
Hi Lorenzo,
I webnt throught he process and it does indeed appear to be a plug-in conflict.
It seems when both EE and the Woocommerce Donations plugin by IgniteWoo are active, the message comes up in all the EE pages.
It does not seem to impact the functionality, or I have not noticed yet, other than the annoying dialog box.
|
|
Josh
|
October 7, 2014 at 2:26 pm
Hi Craig,
It turns out that it does impact the functionality of EE3 because the data table scripts handle the live search and a few other list table controls. The plugin conflict can be avoided if the Donations plugin only ran its JavaScript on its own admin pages. It looks like it’s adding the JavaScript to every page in the admin, which affects the Event Espresso admin pages.
It may help to open a support ticket with Ignite Woo and ask them if their JavaScript can be enqueued only for their pages. If they are not willing to help, you can email a copy of the plugin to support@eventespresso.com and EE support staff can take a look at the code and see if it’s possible to dequeue their scripts from the Event Espresso pages.
|
|
Craig Ferguson
|
October 9, 2014 at 6:00 am
Thank you, they have now updated their plug-in to version 2.4.1 which remedies this issue!
Thanks again for your help!
|
|
Dean
|
October 9, 2014 at 6:22 am
Marking as resolved.
|
