Archived topic
Fatal error: Uncaught Error: Cannot access offset of type string on string
4 replies · Started by Hans-Gerd on December 26, 2022
Hi,
after upgrading to PHP 8.0.25 I get the following error:
Uncaught TypeError: Cannot access offset of type string on string in D:\laragon\www\lindenschule\wp-includes\media.php:779
After deactivating GP Premium, the fatal error no longer appears.
I have additionally migrated the website to my local development environment (laragon), enabled debug and additionally also installed and enabled the Query Monitor plugin. Even there I get the above error.
More information is available in private information.
Thanks and best regards
Hans-Gerd
Hi,
one more addition:
We also use Generatepress and GP Premium at the same hoster on other WordPress instances. There are no issues of the kind described with PHP 8.0.25.
Cheers,
Hans-Gerd
Hi there,
one more addition:
We also use Generatepress and GP Premium at the same hoster on other WordPress instances. There are no issues of the kind described with PHP 8.0.25.
I'm not able to replicate the issue and I don't believe we've received other reports on this as well.
I'd assume it's something specific to this install so let's go through some proper debugging steps here:
First, can you disable ALL plugins and custom functions except GP Premium to test?
Make sure the parent theme is activated if you are using a child theme.
Let me know :)
Hi Leo,
thanks for answer.
Extremely curious: I just noticed that in the menu item "Posts" were initially displayed to me only the first 4 posts. I then deleted the following posts to the trash. After I restored the posts, the website was basically displayed correctly. However, when I go to the trash, the following message appears: "There was a critical error on your website. Please check your site administrator email inbox for further instructions." There is obviously a post there, but it is not displayed.
After that, I clicked on the "Empty Trash" button and now the website seems to be ok.
BTW: I had a repair of the database via define('WP_ALLOW_REPAIR', true);
already done before. Without success.
Amazing that the problem was not obvious with PHP 7.4.x.
Cheers,
Hans-Gerd
Glad to hear that it's resolved :)