• Resolved balvan64

    (@balvan64)


    Hello,
    We are getting these after updating to PHP 8.1:

    1:
    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
    wp-includes/Requests/Cookie/Jar.php:63
    
    2:
    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
    wp-includes/Requests/Cookie/Jar.php:73
    
    3: 
    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
    wp-includes/Requests/Cookie/Jar.php:89
    
    4:
    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
    wp-includes/Requests/Cookie/Jar.php:102
    
    5:
    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
    wp-includes/Requests/Cookie/Jar.php:111
    
    6:
    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
    wp-includes/Requests/Utility/CaseInsensitiveDictionary.php:40
    
    7:
    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
    wp-includes/Requests/Utility/CaseInsensitiveDictionary.php:51
    
    8:
    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
    wp-includes/Requests/Utility/CaseInsensitiveDictionary.php:68
    
    9:
    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
    wp-includes/Requests/Utility/CaseInsensitiveDictionary.php:82
    
    10:
    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
    wp-includes/Requests/Utility/CaseInsensitiveDictionary.php:91

    These are all marked under Plugin: post-smtp

    • This topic was modified 2 years ago by balvan64.
    • This topic was modified 2 years ago by balvan64.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support M Haseeb

    (@haseeb0001)

    @balvan64 Hi,

    I hope you are doing well.

    Can you please share Post SMTP diagnostic test report? So then I can reproduce this case on my staging websites.

    Thanks

    • This reply was modified 2 years ago by M Haseeb.
    Thread Starter balvan64

    (@balvan64)

    Hello,
    Can we share that privately?

    • This reply was modified 2 years ago by balvan64.
    Plugin Support M Haseeb

    (@haseeb0001)

    @balvan64 ok, please create a ticket on our Post SMTP website, then I will check and get back to you with a solution.

    Thanks

    Thread Starter balvan64

    (@balvan64)

    sent.

    Your reference is POST-239

    • This reply was modified 2 years ago by balvan64.
    Plugin Support M Haseeb

    (@haseeb0001)

    @balvan64 Thanks i will look into it shortly.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘PHP 8.1 deprecation warnings’ is closed to new replies.