Site crashed after update to generateblocks pro 12.0

Hi there,

Was there a specific error you received when the site crashed? If not, can you check your error_log file on the server for an error?

Your site seems to be up and running at the moment.

Let us know :)

Hi Tom,

The site is reachable again cause i disabled gnerateblocks (regular and pro) lots of things that are missing now ofcourse like my foorter, buy buttons and other generateblocks styled elements.

I wil enable the generateblocks plugins again now hoping that you can take a quick look. The eroor i am seeing is just simply

- There has been a critical error on this website.

THe site is down now with gb plugins enabled. Can you take a look real quick cause i dont want to keep it down for long ofcourse. I'd rather have it reachable without footer and button etc than have it unreachable at all ofcourse...

Thanks,
Mario

I'm not seeing that (might be cached). However, you should receive an email from WordPress with the specific error.

If not, you need to check your error_log file on the server (or ask your hosting to) so we can know the exact error. That will allow us to suggest a fix.

Let me know :)

Hi Tom,

It took me some time to find the error log and had to contact my host I took a screenshot of the error log but cant find a way to upload a screenshot here

This is what i could copy/past:

APACHE ERROR LOGS
Search logs
[Tue Jun 21 00:23:43.064691 2022] [proxy_fcgi:error] [pid 31316:tid 140692785358592] [client 148.72.153.99:18660] AH01071: Got error 'the log buffer is full (1024). The access log request has been truncated.'
[Tue Jun 21 00:50:59.105474 2022] [proxy_fcgi:error] [pid 31316:tid 140692735002368] [client 148.72.152.104:20232] AH01071: Got error 'the log buffer is full (1024). The access log request has been truncated.'
[Tue Jun 21 00:52:45.147300 2022] [proxy_fcgi:error] [pid 31323:tid 140692743395072] [client 207.38.88.75:20338] AH01071: Got error 'the log buffer is full (1024). The access log request has been truncated.'
[Tue Jun 21 01:01:34.124594 2022] [proxy_fcgi:error] [pid 31323:tid 140692533577472] [client 148.72.152.218:20990] AH01071: Got error 'the log buffer is full (1024). The access log request has been truncated.'
[Tue Jun 21 01:09:13.140454 2022] [proxy_fcgi:error] [pid 31316:tid 140692315367168] [client 213.188.84.235:21810] AH01071: Got error 'the log buffer is full (1024). The access log request has been truncated.'
[Tue Jun 21 01:27:17.526611 2022] [proxy_fcgi:error] [pid 31316:tid 140692139120384] [client 207.38.88.177:24278] AH01071: Got error 'the log buffer is full (1024). The access log request has been truncated.'
[Tue Jun 21 01:40:27.025107 2022] [proxy_fcgi:error] [pid 31323:tid 140692583933696] [client 3.223.183.74:25670] AH01071: Got error 'the log buffer is full (1024). The access log request has been truncated.'
[Tue Jun 21 02:09:56.552774 2022] [proxy_fcgi:error] [pid 31323:tid 140692147513088] [client 148.72.153.159:28026] AH01071: Got error 'the log buffer is full (1024). The access log request has been truncated.'

Does that help?

Thanks,
Mario

Hmm, nothing there that would cause a site crash.

Was your hosting able to see the error in any of their logs? If WordPress displays that message it means there should be a specific error in one of the logs.

Those logs you shared are saying something about the log being full - perhaps this is something your host can fix?

Hi Tom,

Cloudways (my host) isnt very helpfull all they do is share urls with tutorials.

I copied a different part of the error logs, maybe they are more helpfull to you?

Can i revert back to the previous version of generateblocks? could that solve the problem for now?

Here's one more thing we can try first.

First, install this plugin: https://wordpress.org/plugins/wp-debugging/

Then activate GenerateBlocks Pro again so it creates the error. Then you can deactivate it so your site remains up.

Now, go to the wp-content folder and open the debug.log file - this file should have the error in it.

Let me know :)

Hi Tom

I installed the debugging plugin

After activating it this is what i see when i try to reach the website

Fatal error: Uncaught ArgumentCountError: Too few arguments to function GenerateBlocks_Render_Block::filter_rendered_blocks(), 2 passed in /home/698876.cloudwaysapps.com/datrgvtqrm/public_html/wp-includes/class-wp-hook.php on line 303 and exactly 3 expected in /home/698876.cloudwaysapps.com/datrgvtqrm/public_html/wp-content/plugins/generateblocks/includes/class-render-blocks.php:840 Stack trace: #0 /home/698876.cloudwaysapps.com/datrgvtqrm/public_html/wp-includes/class-wp-hook.php(303): GenerateBlocks_Render_Block->filter_rendered_blocks('\n

What version of WordPress are you running?

Oh man, i feel so stupid right now... I was running 5 point something and now that i updated to 6.0 everything is up and running again

I usually wait with the wordpress updates till they go automatically...

So sorry to have wasted your time (sort off)

Anyways, thanks for responding so soon!

Your suggestion resolved the issue

Thanks,
Mario

Not a waste at all! We need to fix this so there's no error on older installs. We'll be releasing GB 1.5.1 shortly.

Thanks!