Support » Alpha/Beta/RC » Deprecated: Return type of Requests_Cookie_Jar

  • Resolved Bjarne Oldrup

    (@oldrup)


    Hey!

    Testing WordPress 6.1 RC1 on a LiteSpeed webserver with PHP 8.1 and wp_debug on. That throws the following warnings:

    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/sustain2/example.net/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/sustain2/example.net/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/sustain2/example.net/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/sustain2/example.net/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/sustain2/example.net/wp-includes/Requests/Cookie/Jar.php on line 111
    
    Deprecated: http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated in /home/sustain2/example.net/wp-includes/Requests/Transport/cURL.php on line 345
    
    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/sustain2/example.net/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/sustain2/example.net/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/sustain2/example.net/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/sustain2/example.net/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/sustain2/example.net/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

    PHP 8.0 leaves active support in a few weeks (security updates for another year still)

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thanks for your feedback. According to this ticket here, this is already known and is being addressed in this ticket here. If you have further questions, I would recommend that you report there in the ticket so that the developers can respond themselves.

    Thread Starter Bjarne Oldrup

    (@oldrup)

    Thank you, @threadi, for pointing me in the right direction. I’ll take a look 🙂
    Bjarne

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.