• I don’t know if this plugin is abandoned (or only the support forum is). Anyway, I post here some deprecations I casually found in my debug.log:

    PHP Deprecated: Return type of Ramsey\Collection\AbstractArray::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/q/www/wp-content/plugins/perfecty-push-notifications/vendor/ramsey/collection/src/AbstractArray.php on line 87
    PHP Deprecated: Return type of Ramsey\Collection\AbstractArray::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/q/www/wp-content/plugins/perfecty-push-notifications/vendor/ramsey/collection/src/AbstractArray.php on line 87
    PHP Deprecated: Ramsey\Uuid\Builder\BuilderCollection implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /home/q/www/wp-content/plugins/perfecty-push-notifications/vendor/ramsey/uuid/src/Builder/BuilderCollection.php on line 32
    PHP Deprecated: Ramsey\Uuid\Provider\Node\NodeProviderCollection implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /home/q/www/wp-content/plugins/perfecty-push-notifications/vendor/ramsey/uuid/src/Provider/Node/NodeProviderCollection.php on line 0
    Cron unschedule event error for hook: perfecty_push_cron_check, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[]}

Viewing 1 replies (of 1 total)
  • hi, get new versions of ramsey and guzzlehttp from gidhub. cant figure out the error for Cron unschedule event error for hook: perfecty_push_cron_check, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[]} just yet. After updating those errors were gone, but the cron is still an issue.

Viewing 1 replies (of 1 total)
  • The topic ‘Deprecations’ is closed to new replies.