|
tyler
|
December 8, 2022 at 1:33 pm
Hi, our client just reported that they’re seeing an error 502 when they try to view messages that have been sent from the EE admin messages panel. They said this just started happening in the past 48 hours and aren’t aware of any system changes that have been made. The site is hosted on WPEngine and I’ve reviewed the error logs after getting the 502 and do not see any logged errors. The error also pops up almost instantly, which doesn’t seem like a real timeout. I’ll post a private reply next showing a video of the issue. Any ideas on what could be causing this?
|
|
tyler
|
December 8, 2022 at 1:33 pm
This reply has been marked as private.
|
|
tyler
|
December 8, 2022 at 1:39 pm
This reply has been marked as private.
|
|
tyler
|
December 8, 2022 at 2:16 pm
This reply has been marked as private.
|
|
tyler
|
December 8, 2022 at 2:59 pm
EE Support: I’ve confirmed this is an issue with EE compatibility w/ WP 6.1 and 6.1.1. The problem exists on 6.1.1 and persists on 6.1. However, a downgrade to 6.0.3 clears the issue. This affects other areas such as view invoice and view receipt links as well.
This is with EE 4.10.40.p and PHP 8.
Please let me know when an update will be released.
|
|
Tony
|
December 9, 2022 at 4:45 am
Hi Tyler,
I’ve been using 6.1.1 on multiple different test sites for a while now (I run the beta tester plugin on some of those) and don’t run into this issue.
502 errors are server side, there’s something WP Engine doesn’t like about those requests here and why that’s only happening on 6.1+ is odd, afaik we haven’t changed anything on those requests in a long time.
Have you opened a ticket with WPEnging regarding this at all? I’m curious as to what their thoughts on this are so far.
If you right-click on the icon and do ‘Copy Link Address’ you’ll get the full URL which you can load in a tab (it will almost certainly load the same error), send one of those to WPEnginge along with an Invoice URL and check they aren’t blocking those requests on their end.
|
|
tyler
|
December 9, 2022 at 9:59 am
I can check with them on this, but it doesn’t make any sense that if WPEngine was blocking it why it would work fine on 6.0.3 and NOT on 6.1 or 6.1.1… Same environment – works on 6.0.3, doesn’t work on 6.1+
|
|
tyler
|
December 9, 2022 at 10:09 am
This reply has been marked as private.
|
|
tyler
|
December 9, 2022 at 6:22 pm
Hey Tony,
Here’s what I got back from WPEngine support: In looking over the logs, I am seeing the 502s mentioned. I don’t see any fatal errors that may be contributing to this, however I did see that the plugin is performing slow queries:
1 /nas/content/live/…/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php:2379
Seems as the plugin is making queries that are taking too long. I don’t see any high autoload, so you’re fine there. You can also pass this along to the plugin author to see if they have any insight on a cause.
|
|
Tony
|
December 10, 2022 at 5:47 am
I can check with them on this, but it doesn’t make any sense that if WPEngine was blocking it why it would work fine on 6.0.3 and NOT on 6.1 or 6.1.1… Same environment – works on 6.0.3, doesn’t work on 6.1+
I kinda agree but at the same time EE doesn’t changed between those versions on your site either, so it makes no sense that it works on one and not the other, we have no code that relies on those versions. Nor does it make sense that every one of my sites works and we’ve had no other reports, that’s why I was curious on their thoughts 🙂
however I did see that the plugin is performing slow queries
Again this dont change between versions and the timeout seem WAY to quick for that to be the actualy issue here. If the slow query was the case you’d get that in both WP versions.
I assume you have a staging site?
If you test this with only Event Espresso activated there does it do the same?
|
|
tyler
|
December 12, 2022 at 12:48 pm
Hey Tony, thanks again for your great help and support!
Turns out this was a theme issue causing issues viewing public URLs when logged in which wasn’t logging any error.
Found it and got it fixed up. Thanks again!
|
|
Tony
|
December 13, 2022 at 4:16 am
Oh, nice find!
I’m curious as to what the issue was, can you share any additional details?
|
