|
Erica Vandiver
|
October 9, 2017 at 9:26 am
After updating EE from 4.8.26.p to 4.9.46, clicking on the ‘Register’ button fails to load the registration page. I increased the memory per https://eventespresso.com/topic/getting-error-after-saving-event/ from 40M to 96M (single site), and turned on full logging. Nothing is reflected in the log.
This was done with maintenance mode off, and after the site’s app pool was restarted.
|
|
Tony
|
October 9, 2017 at 9:35 am
Hi there,
When you say the page doesn’t load, what actually happens on the site? A whitescreen?
Can you let me know which site this is happening on? Or link me to an event I can see this on?
|
|
Erica Vandiver
|
October 9, 2017 at 9:38 am
Thanks Tony! The error message is : “online.stlcc.edu is currently unable to handle this request. HTTP ERROR 500 ”
The event is at https://online.stlcc.edu/events/test-event/
Thanks!
|
|
Tony
|
October 9, 2017 at 9:56 am
Error 500 usually means a fatal error is happening on the server.
If you have access to the servers error logs you can view the error there.
If not ou can add this snippet:
https://gist.github.com/Pebblo/8787f5530ea777c84aaf62f075e55b32
To your sites wp-config.php file to log the errors so we know what is happening.
|
|
Erica Vandiver
|
October 9, 2017 at 10:11 am
PHP logs:
For your session (13:47 UTC), I got a ton of “WordPress database error Unknown character set: ‘utf8mb4’ for query…” and and then “PHP Fatal error: Maximum execution time of 300 seconds exceeded in …\wp-includes\wp-db.php on line 1889”.
I also have IIS logs if needed (I don’t see anything in there, but I don’t work on servers, so I wouldn’t).
|
|
Erica Vandiver
|
October 9, 2017 at 10:29 am
A question from the server team: “Does the new EE use the xmlrpc?… not sure if it is related, but we are blocking it on the iis side”
|
|
Tony
|
October 9, 2017 at 10:39 am
I also have IIS logs if needed (I don’t see anything in there, but I don’t work on servers, so I wouldn’t).
Whilst installing and using WordPress on IIS is possible, it’s less than ideal. WP (and therefor EE) is developed and tested on Linux based stacks.
I’m guessing this was a limitation from your IT department and you can only use IIS?
Unknown character set: ‘utf8mb4’ for query
Which version of MySQL is used on the server? I’m guessing an older version that doesn’t support uff8mb4:
https://stackoverflow.com/questions/21911733/error-1115-42000-unknown-character-set-utf8mb4
A question from the server team: “Does the new EE use the xmlrpc?… not sure if it is related, but we are blocking it on the iis side”
I’ll double check but as far as I’m aware, EE does not use xmlrpc.
That’s not what is causing the above error either way.
|
|
Josh
|
October 9, 2017 at 10:47 am
Hi Kris,
Can you install this plugin:
https://wordpress.org/plugins/health-check/
Then go to the WP Dashboard’s Health Check page that’s added by that plugin and see what it says for MySQL utf8mb4 support. What does it say there?
|
|
Erica Vandiver
|
October 9, 2017 at 12:12 pm
It says
WordPress’ utf8mb4 support requires MariaDB version %s or greater
WordPress’ utf8mb4 support requires MySQL client library (mysqlnd) version 5.0.9 or newer.
I can ask IT about the mysql library, but what is the MariaDB version supposed to be?
|
|
Erica Vandiver
|
October 9, 2017 at 12:17 pm
Can the encoding be set to use utf8? Updating the components would take more time than I have for this update.
|
|
Josh
|
October 9, 2017 at 12:53 pm
what is the MariaDB version supposed to be?
MySQL server is version 5.5.3 or higher (including all 10.x versions of MariaDB).
Can the encoding be set to use utf8?
That’s not recommended.
|
|
Erica Vandiver
|
October 9, 2017 at 12:55 pm
What version of EE requires these changes? We were having no problems on 4.8.26.p, so I guess I’ll just revert to that.
|
|
Josh
|
October 9, 2017 at 1:08 pm
I don’t think that was actually a requirement added by Event Espresso, there was support for utf8mb4 introduced in WordPress version 4.2.
You may also need to revert back your database and your version of WordPress in order for the reverted version of Event Espresso to function correctly. One reason for this is the older version of EE isn’t compatible with the newer versions of WordPress.
|
|
Erica Vandiver
|
October 9, 2017 at 1:54 pm
What version is ‘the older version’? I have 2 similar sites, and the other one has been running fine with 4.9.28 and WP 4.8.2.
I have reverted the site and it is testing fine with the same versions – it is upon upgrading Event Espresso that the issue appears.
|
|
Josh
|
October 9, 2017 at 1:58 pm
The older version you had was 4.8.26.p.
|
|
Erica Vandiver
|
October 9, 2017 at 2:01 pm
But 4.8.26.p & 4.8.28.p are working fine for us with WP 4.8.2. It’s the upgrade of EE that caused the error.
|
|
Josh
|
October 9, 2017 at 2:55 pm
I think you meant 4.9.28.p is working on your other site. May I ask is that other site hosted on the same server? If so, then you can try 4.9.28.p on your other site, all other things being equal it should work there too.
|
|
Erica Vandiver
|
October 9, 2017 at 3:03 pm
My sites are running…
online.stlcc.edu: WP 4.8.2, EE 4.9.26.p
orientation.stlcc.edu: WP 4.8.2, EE 4.9.28.p
What I’m trying to find out is why my upgrade to 4.9.46 failed on online.stlcc.edu.
The conversation so far had made me think something about EE 4.9.46 required utf8mb4, but you are saying it’s WP since 4.2. If that were true, I’d be having issues on one of the two sites listed above, right?
|
|
Josh
|
October 9, 2017 at 3:08 pm
I didn’t say WP required utf8mb4, I said it added support for utf8mb4.
|
|
Erica Vandiver
|
October 9, 2017 at 3:09 pm
Thanks for that clarification. So what is the reason my update failed?
|
|
Josh
|
October 9, 2017 at 3:32 pm
I don’t know, but I can tell you that it probably would not have failed if your server met the recommendations from the WP Health Check plugin and the requirements listed here:
https://eventespresso.com/requirements/
|
