Evan Donovan
Forum Replies Created
-
Ok, thanks – as long as 1) premium plugins are also checked for security updates, and 2) they are checked even if already installed, our issue is addressed.
What if you already have a plugin installed and a security vulnerability is identified in the version that you have installed? Does a critical alert get sent out for that also?
Thanks – I don’t think we need this feature enough to pay for the cloud version, but it is good to know it exists.
Thanks for the quick reply – do you have a link to a description of that functionality, or at least could you let me know how many days it would cover?
I’m thinking about switching to WP Supercache, since I actually had tried that before in development briefly, but we were recommended WP Rocket, and so we switched.
However, with some other caching plugins in addition to it, it seems WP Supercache might actually have been faster and more reliable, so it might be worth switching back.
The only reason I’ve stuck with WP Rocket so far is that we paid for it.
I enabled WP Rocket within an hour or so of making the site live, to deal with the traffic, but I don’t recall seeing it before I enabled WP Rocket.
I have a ticket open with them, but since I can’t get more specific logging details they weren’t able to give me much guidance.
Unfortunately, I can’t really disable WP Rocket on live because some of the pages are too slow for a production environment without page caching, since they have so many queries / extensive use of a page builder (Elementor).
Thanks – I haven’t been able to cause the error to happen again today. It seems extremely unpredictable – there’s not particular pages that I can visit that will reliably trigger it.
So are you saying the PHP “white screen of death” is not technically considered a 500 error?
In either case, my point is that the PHP errors, if that is what it is, are not being logged anywhere. Normally, when there are memory exhaustion issues with a PHP script, I can enable something to get that logged, but I don’t seem to be able to do that with WordPress.
Is there something with WordPress 5.2’s error handling that makes it harder to get the regular PHP fatal errors like “memory limit reached” into the logs?
The browser says something about “this page could not be displayed” before redirecting – typically that is a 500 error.
What other circumstances could cause that, do you think?
Thanks – my specific question was about how to get the 500 errors to show up in a log.
Right now, I am not seeing them in:
- the regular PHP error log (which I have enabled)
- the WordPress debug.log under wp-content (also enabled)
- the email notifications of fatal errors that are new to WordPress 5.2
- the Apache error log
I have access to all those and I have seen other fatal errors in them when they occurred.
Is there anything else I could do to try to get the error into a log?