• carysma

    (@carysma)


    Hi
    I get a lot of PHP errors through WPappbox since the switch to PHP 8.0 or 8.1. WordPress version is 5.9.

    Here is an excerpt from Query Monitor:

    Veraltet	Return type of phpQueryObject::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice	1	
    wp-content/plugins/wp-appbox/inc/queryelements.php:4104
    Plugin: query-monitor
    Veraltet	Return type of phpQueryObject::next($cssSelector = null) should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice	1	
    wp-content/plugins/wp-appbox/inc/queryelements.php:4124
    Plugin: query-monitor
    Veraltet	Return type of phpQueryObject::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice	1	
    wp-content/plugins/wp-appbox/inc/queryelements.php:4110
    Plugin: query-monitor
    Veraltet	Return type of phpQueryObject::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice	1	
    wp-content/plugins/wp-appbox/inc/queryelements.php:4141
    Plugin: query-monitor
    Veraltet	Return type of phpQueryObject::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice	1	
    wp-content/plugins/wp-appbox/inc/queryelements.php:4089
    Plugin: query-monitor
    Veraltet	Return type of phpQueryObject::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice	1	
    wp-content/plugins/wp-appbox/inc/queryelements.php:2806
    Plugin: query-monitor
    Veraltet	Return type of phpQueryObject::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice	1	
    wp-content/plugins/wp-appbox/inc/queryelements.php:4149
    Plugin: query-monitor
    Veraltet	Return type of phpQueryObject::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice	1	
    wp-content/plugins/wp-appbox/inc/queryelements.php:4155
    Plugin: query-monitor
    Veraltet	Return type of phpQueryObject::offsetSet($offset, $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	1	
    wp-content/plugins/wp-appbox/inc/queryelements.php:4161
    Plugin: query-monitor
    Veraltet	Return type of phpQueryObject::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice	1	
    wp-content/plugins/wp-appbox/inc/queryelements.php:4168

    If any information is needed to fix the errors, please write briefly.

Viewing 1 replies (of 1 total)
  • Plugin Author Marcelismus

    (@marcelismus)

    Yes, phpQuery itself is no longer developed by the developers. Therefore, there are currently no adjustments to PHP 8.x and for my part, at least in the short term, none are possible to the phpQuery class. Update with #[ReturnTypeWillChange] is coming in the next days (at least for the upper notices).

Viewing 1 replies (of 1 total)
  • The topic ‘PHP errors with PHP 8.1’ is closed to new replies.