Archived topic
Weird critical error after 3.2.4 update
7 replies · Started by Dan on November 30, 2022
Last night I updated to 3.2.4, and everything seemed fine.
This morning my site experienced a critical error. I'm posting the log report for the error in the private section. I'm not 100% certain Generatepress has anything to do with this, but it is mentioned several times in the log relating to the critical error.
Strangely, after a few minutes, everything came back again.
Firstly, I have never seen such a delayed issue after an update. Normally a critical error will happen immediately. Secondly, I've never seen a critical error like that fix itself. Usually, you have to roll back a theme or plugin. Right? very weird.
Do you see anything in the log that would explain this?
Hi there,
I don't believe this is related to GP - at least we haven't had any other reports on this since the last update came out on Nov 22, 2022.
Maybe some sort of caching issue?
If it happens again then we can go through some debugging tests.
Let me know :)
That is strange because my host support (Kinsta) says the specific fatal error is caused by /www/REMOVED/public/wp-content/themes/generatepress/header.php(26): do_action('wp_body_open')
And yes, it happened again and threw the same errors in the log.
I can't see how this line would trigger any errors at all:
https://github.com/tomusborne/generatepress/blob/master/header.php#L26
We have not changed the header.php file in the recent updates.
What PHP version are you using?
I was running 8 and have been for months. After seeing the error the first time, I went to 7.4 briefly but still got the same error again.
We would need to go through some debugging tests as there are no other reports on this.
Can you start a staging site and keep all plugins and custom functions disabled and see if the error still occur?
I have been playing with this further, and it seems to be related to Cloudflare APO. I'm still determining exactly what is going on, but if I disable APO, the site doesn't crash anymore. Perhaps it has nothing to do with Generatepress and is entirely an APO issue. I'm just posting this here for completeness in case anyone else has a similar issue.
Thanks for sharing!
