Version 0.8.26 broken?

Hi,

The changes between -0.8.25 and 0.8.26 are very minor and shouldn’t be capable of those kinds of effects (which we’re not seeing on any testing sites). They sound like the sort of thing you might see if your WP site is running very close to the PHP memory limit, and one more plugin tips it over the edge. Do you get the same result if, for testing purposes, you re-activate UpdraftCentral and deactivate all other plugins?

What is logged in your hosting PHP log at the times of these errors?

David

Hi,
No other plugins are active, I see the following error in de debug:



Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u30355p24110/domains/valksictsupport.nl/public_html/mainwp/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u30355p24110/domains/valksictsupport.nl/public_html/mainwp/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u30355p24110/domains/valksictsupport.nl/public_html/mainwp/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u30355p24110/domains/valksictsupport.nl/public_html/mainwp/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u30355p24110/domains/valksictsupport.nl/public_html/mainwp/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u30355p24110/domains/valksictsupport.nl/public_html/mainwp/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u30355p24110/domains/valksictsupport.nl/public_html/mainwp/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u30355p24110/domains/valksictsupport.nl/public_html/mainwp/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u30355p24110/domains/valksictsupport.nl/public_html/mainwp/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u30355p24110/domains/valksictsupport.nl/public_html/mainwp/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

i.e. It happens on a blank WP install? What versions of WP and PHP do you have, and what theme?

It looks like you have recently upgraded to PHP 8.1+ version. It may cause these deprecated warnings because WordPress 6.1 is not 100% compatible with PHP 8.1.

If you recently upgraded to a newer PHP version, Canyou please downgrade the PHP version to the previous version and test it?

Hope it helps you..

I use WP 6.1.1. I tried PHP 8.0 and even reverted to 7.3. Same issue. I’m going to perform a clean install.

Reinstalled WordPress 6.1.1. (PHP 8.x) on a new subdomain, installed the Updraft Central plugin and activated it. Create a new page, put the short-code on it, save: error, Updating failed. The response is not a valid JSON response.

Page is saved however, but the same issue.

“The response is not a valid JSON response.”

If you open your web browser’s development tools, and look at what the response is to the HTTP request when you get that, what is it?
If it happens on a blank WP install with nothing else, then my guess is that your webserver (not WP site, webserver) has a security module of some sort that decides to wrongly block the request as suspicious. Try looking in your control panel for things like mod_security and do a test in which you turn it off.

The JSON response error appears only then the plugin is activated. When I disable the plugin, there is no error.

Can you please download and test the recently released UpdraftCentral version 0.8.27? According to our UpdraftCentral developer, this new version contains the fix for this issue.

Let me know what happens on your end.

Yes, this seems to fix the issues! Thanks for taking care of this nasty bug ??