Hi @valentinb,
Thanks for reaching out, and sorry for the trouble!
The error you quoted points to the code of one of your own snippets, not to Woody itself. The class.execute.snippet.php(808) part is the place where Woody runs your PHP snippets, and eval()'d code on line 4 means the problem is on line 4 of one specific snippet. Woody runs fine on PHP 8.3, but when one snippet stops with an error, it takes the whole page down with it, which is why it looks like none of your snippets are working.
Here’s how to get things running again:
- While logged in as an administrator, open this address (replace example.com with your domain):
https://example.com/wp-admin/edit.php?post_type=wbcr-snippets&wbcr-php-snippets-safe-mode
This turns on Woody’s Safe Mode, which pauses all snippets for you so you can work in the dashboard.
- On the snippets screen, you should see a “Snippet Error Detected” notice with the name of the snippet that failed and an Edit Snippet link.
- Deactivate that snippet, then click “Disable Safe Mode”. All your other snippets will run normally again.
One common cause when a host switches PHP versions: the new version doesn’t always have the same PHP extensions enabled (for example mbstring or intl), so code that worked before suddenly calls a function that no longer exists. If that’s the case, your host can enable the extension for PHP 8.3 and the snippet will work again without any changes.
Let us know how it goes…