予期せぬエラーが発生しました。

[mimi]

PHP8.1以降に設定すると「 予期せぬエラーが発生しました。strip_tags(): Passing null to parameter #1 ($string) of type string is deprecated」と表示されます。
解決方法をお願いします。

[mhawke]

What page is crashing? Can you cut’n paste the line in the error message that says what PHP file it crashed on? Also, what version of concrete are you running?

[mimi]

Thanks.
It appears when I press the button to add a new blog page (with sidebar).
It does not occur when adding a new page (full page).
Maybe it is right_sidebar.php and left_sidebar.php.
Concrete version is 9.3.5.
If I change the PHP version to 7.4 or 8.0, it will not show up.

[mhawke]

The top line of the error message contains the actual PHP page within the system (not the page in your navigation) where the crash occurred. Can you paste the top few lines of the error message.

[mimi]

No, there is not.
Send error logs and messages displayed in the browser console.

[mhawke]

Aw. Try going to Dashboard->Environment->Debugging and set it up to show the errors.

[mimi]

[mhawke]

I realize this can be confusing but you’ve posted the ‘example’ from the dashboard debugging page. That’s not really what we need. Now that you’ve turned debugging on, visit a page on your website that was giving you the original error and post the error message that shows up on that page.

[mimi]

Sorry.
I checked debugging with the specified settings, in which case I could operate normally.
There were no error messages.

[mhawke]

So this is good news and bad news. The good news is that the panic is over and the site can operate. The bad news is that the error is still there but it’s no longer crashing your site. Eventually, when you upgrade the PHP version again, the site will crash again. The ‘error’ you are suffering from is actually supposed to just be a ‘warning’ in PHP 8.1. Since you cleared the box labeled “Consider warnings to be errors” then the warning is just a warning right now and will not crash the site. If you want to fix the underlying problem now, you need to click “Consider warnings as errors” so that the warning becomes an error again and you’ll get a message that tells you the actual line number of the actual PHP file that’s causing the problem and then you can fix that line. I highly suspect it will be in an add-on that is not fully compatible with PHP 8.1 but we’ll see.

[mimi]

Thank you.
I will check again when I upgrade PHP and Concrete cms.
See you.