• Resolved dwdonline

    (@dwdonline)


    These errors show in both the free and premium. I’ve put in multiple tickets (that are essentially ignored) for the paid licenses, but we also have some of the free versions running.

    DeprecatedReturn 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 notice1+wp-includes/Requests/Utility/CaseInsensitiveDictionary.php:40Plugin: ajax-search-for-woocommerce-premiumDeprecatedReturn 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 notice1+wp-includes/Requests/Utility/CaseInsensitiveDictionary.php:51Plugin: ajax-search-for-woocommerce-premiumDeprecatedReturn 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 notice1+wp-includes/Requests/Utility/CaseInsensitiveDictionary.php:68Plugin: ajax-search-for-woocommerce-premiumDeprecatedReturn 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 notice1+wp-includes/Requests/Utility/CaseInsensitiveDictionary.php:82Plugin: ajax-search-for-woocommerce-premiumDeprecatedReturn 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 notice1+wp-includes/Requests/Utility/CaseInsensitiveDictionary.php:91Plugin: ajax-search-for-woocommerce-premiumDeprecatedReturn 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 notice1+wp-includes/Requests/Cookie/Jar.php:63Plugin: ajax-search-for-woocommerce-premiumDeprecatedReturn 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 notice1+wp-includes/Requests/Cookie/Jar.php:73Plugin: ajax-search-for-woocommerce-premiumDeprecatedReturn 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 notice1+wp-includes/Requests/Cookie/Jar.php:89Plugin: ajax-search-for-woocommerce-premiumDeprecatedReturn 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 notice1+wp-includes/Requests/Cookie/Jar.php:102Plugin: ajax-search-for-woocommerce-premiumDeprecatedReturn 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 notice1+wp-includes/Requests/Cookie/Jar.php:111Plugin: ajax-search-for-woocommerce-premiu

Viewing 1 replies (of 1 total)
  • Hi @dwdonline

    These alerts are issued by the core of WordPress and its remote request library. Currently, WordPress 6.1 is not fully compatible with PHP 8.1, which may result in these warnings. However, the upcoming version 6.2, set to be released on March 28, 2023, will bring significant improvements in this area.

    Here is a topic about WordPress 6.2 Beta 1 where you can download it and test if these notices will still occur.

    Regards,
    Kris

Viewing 1 replies (of 1 total)
  • The topic ‘Not compatible with php8 – Deprecated’ is closed to new replies.