• Resolved Franky

    (@liedekef)


    – When activating the plugin, it doesn’t check if the tables already exist so it creates mysql errors
    – lots of deprecation warnings (causing about 3000 warnings in the logfiles):

    [18-Nov-2022 15:00:53 UTC] PHP Deprecated:  uasort(): Returning bool from comparison function is deprecated, return an integer less than, equal to, or greater than zero in /var/www/html/wordpress/wp-content/plugins/wp-ever-accounting/includes/class-collection.php on line 434
    [18-Nov-2022 15:00:53 UTC] PHP Deprecated:  Constant FILTER_SANITIZE_STRING is deprecated in /var/www/html/wordpress/wp-content/plugins/wp-ever-accounting/includes/ea-file-functions.php on line 123
    [18-Nov-2022 15:00:53 UTC] PHP Deprecated:  Return type of EverAccounting\Abstracts\Registry::offsetExists($offset) should either be compatible with ArrayObject::offsetExists(mixed $key): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/wordpress/wp-content/plugins/wp-ever-accounting/includes/abstracts/abstract-registry.php on line 121
    [18-Nov-2022 15:00:53 UTC] PHP Deprecated:  Return type of EverAccounting\Abstracts\Registry::offsetGet($offset) should either be compatible with ArrayObject::offsetGet(mixed $key): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/wordpress/wp-content/plugins/wp-ever-accounting/includes/abstracts/abstract-registry.php on line 135
    [18-Nov-2022 15:00:53 UTC] PHP Deprecated:  Return type of EverAccounting\Abstracts\Registry::offsetSet($offset, $value) should either be compatible with ArrayObject::offsetSet(mixed $key, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/wordpress/wp-content/plugins/wp-ever-accounting/includes/abstracts/abstract-registry.php on line 149
    [18-Nov-2022 15:00:53 UTC] PHP Deprecated:  Return type of EverAccounting\Abstracts\Registry::offsetUnset($offset) should either be compatible with ArrayObject::offsetUnset(mixed $key): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/wordpress/wp-content/plugins/wp-ever-accounting/includes/abstracts/abstract-registry.php on line 162
    [18-Nov-2022 15:00:53 UTC] PHP Deprecated:  Return type of EverAccounting\DateTime::setTimezone($timezone) should either be compatible with DateTime::setTimezone(DateTimeZone $timezone): DateTime, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/wordpress/wp-content/plugins/wp-ever-accounting/includes/class-datetime.php on line 85
    [18-Nov-2022 15:00:53 UTC] PHP Deprecated:  Return type of EverAccounting\DateTime::getOffset() should either be compatible with DateTime::getOffset(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/wordpress/wp-content/plugins/wp-ever-accounting/includes/class-datetime.php on line 72
    [18-Nov-2022 15:00:53 UTC] PHP Deprecated:  Return type of EverAccounting\DateTime::getTimestamp() should either be compatible with DateTime::getTimestamp(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/wordpress/wp-content/plugins/wp-ever-accounting/includes/class-datetime.php on line 187
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Sultan Nasir Uddin

    (@manikmist09)

    Hi @liedekef

    Thank you for reporting the issue. It seems you are running the WordPress instance
    with PHP v8.1, and our plugin is not compatible yet with that version; however, we are working to make it compatible soon. That is why you are receiving deprecated notice.

    Also, it seems you have turned on debug mode define( 'WP_DEBUG', true ); in the wp-config.php file, which is the reason behind these lots of logs.

    Thread Starter Franky

    (@liedekef)

    indeed true on both cases. But since 7.4 is almost deprecated, I would assume 8.1 support to be ready. Even 8.0 is almost on the “security support” only track, see https://www.php.net/supported-versions.php

    Hello @liedekef,

    This issue has been fixed in the latest version of the plugin. Please update the plugin to the latest version and let me know if you face any issues.

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Warnings on activation’ is closed to new replies.