alhelor

Thank you for your reply. It’s a bit more complex though.

1. The fact WP Engine support says it’s a problem with WordPress code kind of shows incompetence from their side.
2. I believe the thread from 9 months ago referenced in my post came with the same symptoms, but the reason (disk_free_space disabled, leading to this message) has since been fixed. Thus, the current Site Health (as of WP 6.5.4) does not throw this message if disk_free_space has been purposefully disabled. It’s pretty much the same as it doesn’t tell you an event is late when you disable WP_Cron. It just trusts that if you’ve done it on purpose, you know what you’re doing.

Thus, would be nice to know if there’s anyone here using WP Engine, getting the same message.

Hey @pierrelannoy

Just an update: Restoring from backup and upgrading from 3.8.0 to 3.8.3 causes the same issue on that site as with 3.8.1: site crash with no access to anything. Plugin needs to be disabled through FTP. That’s probably the same reason why 3.8.3 couldn’t be activated (or deleted) before in the first place. Other sites work fine, though.

Hey Pierre, no, I don’t. I guess I’ll have to investigate later. Worst-case scenario, I’ll just restore from a backup. All other addons seem to work fine, though.

Thank you for the feedback and the quick fix. On one of the websites, I cannot activate (or delete) it anymore, as this gives a fatal error. I was able to update from 3.8.0 to 3.8.3, though.

I deleted all apcm entries in the database. Still, when I try to activate, it says “Plugin could not be activated because it triggered a?fatal error.” And then I try to delete, it says, “Deletion failed: There has been a critical error on this website.Learn more about troubleshooting WordPress.”

Deleting through FTP obviously works. Any ideas how to fix it?