NO BUG: SiteGround updated their PHP to version 8.2.23 and the site went into critical error

Browser: Chrome 110
OS: macOS / Windows / Linux / etc.
URL: Link to a page that illustrates this issue
Video: Short screen recording that illustrates this issue (free tool: jam.dev)

[Please describe this bug in as much detail as possible so we can replicate & debug this bug]

Yesterday SiteGround updated their PHP to version 8.2.23 and the site went into critical error.

Bricks Builder is updated to version 1.10.3.

I tried with the default theme and the website works.

I report the problem but how do we solve it?

Thanks.

Hi,

we will need a bit more information. What was the previous version of PHP and what is the error? Is there anything in debug.log (make sure that it’s enabled). Is it happening only when opening a builder, or even on the front end?

Sometimes you just need to resave permalinks when you change the PHP version. Maybe it’s that.

Thanks for more info,
M

Hi,
ok then.

PHP working version: 7.4.33
SiteGround LOG file errors:

2024-09-03 05:04:04 UTC [apache][authz_core:error] [pid 79947] [client 44.240.37.43:12136] AH01630: client denied by server configuration: /public_html/wp-content/themes/bricks/Index.php

Only happens in front-end.

Saving permalink failed.

This seems to me like the Apache configuration changed, or was updated. There are some changes in 2.4 version of Apache that can cause this error message, so it might be that (Stack Overflow link: Apache2: 'AH01630: client denied by server configuration' - Stack Overflow)

https://httpd.apache.org/docs/2.4/upgrading.html#run-time

Let me know.

Best regards,
M

I looked into it more deeply and apologize in advance for my inexperience as a developer.

Since the same configuration is present in the main domain site and in the subdomain site and that in the subdomain the site works with PHP 8.22, I looked elsewhere.

In the functions.php file, in fact, I found a custom function that had errors or rather was not optimized for PHP 8.22 and therefore generated the critical error.

I corrected it and now it works.
Luckily it was not Bricks, in the end, that created problems.

Thanks again!

Hi,

thank you for your report back. I’m happy that the problem is now solved :slight_smile:

Best regards,
M