|
Vernon
|
March 19, 2019 at 10:56 am
I am unable to update my event espresso on my live site. Nor am I able to enter the license key on the live website. I was able to enter the license on the development site and on event espresso it says that it is not registered to any website.
|
|
Tony
|
March 19, 2019 at 11:03 am
Hi there,
Just to clarify, your thread title mentions an Event Espresso theme, but there is no EE theme it’s a plugin.
I am unable to update my event espresso on my live site.
What happens when you try to update?
Nor am I able to enter the license key on the live website.
Is the live site running on WordPress multisite? If so the key field will only show on the ‘main’ site of the network.
I was able to enter the license on the development site and on event espresso it says that it is not registered to any website.
The license system allows you to use the key on a dev domain (a domain containing ‘dev’) which I can see you are using, so it wont link the key to a dev domain.
|
|
Vernon
|
March 19, 2019 at 11:21 am
Correct Tony, plug in not theme.
On the plug in page : An automatic update for Event Espresso is available but your Support License Key has not been activated. For EE3+ users, please go to the Event Espresso General Settings page to set your Support License Key. For EE4+ users, please go to the Your Organization Settings page.( https://monosnap.com/file/n45i2GypF0r1IQMv422IplBdAOaZVk )
And in event espresso general settings on live site ( https://monosnap.com/file/10q4tY9CZPQCc70EVqk7SqsKSP2QHK )
I did unintentionally enter the support key on the development / dev site.
Thanks again for your quick response
|
|
Tony
|
March 19, 2019 at 11:23 am
I did unintentionally enter the support key on the development / dev site.
Its fine that you did, the dev site isn’t linked to your license.
So what happens when you add the key to that field on the live site?
|
|
Vernon
|
March 19, 2019 at 11:34 am
500 – Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
|
|
Tony
|
March 19, 2019 at 11:50 am
OK, so that’s usually a fatal error thrown in the background (Error 500 is a catch-all shown to visitors when there’s a fatal).
Can you check the servers error log around the time you threw the above error and see what the full error is pleased?
|
|
Vernon
|
March 19, 2019 at 12:10 pm
Was able to license. Then during update : (going to look at error log on server for further details)
Update Failed: <!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN” “http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd”>
500 – Internal server error.
<!–
body{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;}
fieldset{padding:0 15px 10px 15px;}
h1{font-size:2.4em;margin:0;color:#FFF;}
h2{font-size:1.7em;margin:0;color:#CC0000;}
h3{font-size:1.2em;margin:10px 0 0 0;color:#000000;}
#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:”trebuchet MS”, Verdana, sans-serif;color:#FFF;
background-color:#555555;}
#content{margin:0 0 0 2%;position:relative;}
.content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;}
–>
Server Error
500 – Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
|
|
Vernon
|
March 19, 2019 at 12:33 pm
** contents of access logs redacted **
-
This reply was modified 5 years, 8 months ago by
 Josh. Reason: portions of access logs should never be posted to a public forum
|
|
Tony
|
March 19, 2019 at 12:52 pm
First one looks like the error page source and second looks like an access log. Unfortunately neither of those help.
Does your host have an error log section in your control panel? Most show you the last x number of errors.
If not you’ll need to add some code to your wp-config.php file to enable error logging.
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
|
|
Vernon
|
March 19, 2019 at 2:15 pm
This reply has been marked as private.
|
|
Vernon
|
March 19, 2019 at 3:06 pm
This reply has been marked as private.
|
|
Tony
|
March 19, 2019 at 4:34 pm
I’m glad you got it up and running 🙂
Any further problems please let us know.
|
