• Resolved fpablo

    (@fpablo)


    I have thousands of such errors in logs.

    [05-Dec-2024 20:40:17 UTC] PHP Deprecated:  Return type of AmpProject\Optimizer\ErrorCollection::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/***/domains/***.pl/public_html/wp-content/plugins/accelerated-mobile-pages/includes/vendor/tool/Optimizer/ErrorCollection.php on line 67
    [05-Dec-2024 20:40:17 UTC] PHP Deprecated: Return type of AmpProject\Optimizer\ErrorCollection::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/***/domains/***.pl/public_html/wp-content/plugins/accelerated-mobile-pages/includes/vendor/tool/Optimizer/ErrorCollection.php on line 57
    [05-Dec-2024 20:40:17 UTC] PHP Deprecated: Return type of AmpProject\Dom\Document::saveHTML(?DOMNode $node = null) should either be compatible with DOMDocument::saveHTML(?DOMNode $node = null): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/***/domains/***.pl/public_html/wp-content/plugins/accelerated-mobile-pages/includes/vendor/tool/Dom/Document.php on line 575
    [05-Dec-2024 20:40:17 UTC] PHP Deprecated: DOMDocument::createElement(): Passing null to parameter #2 ($value) of type string is deprecated in /home/***/domains/***.pl/public_html/wp-content/plugins/accelerated-mobile-pages/includes/vendor/tool/Dom/Document.php on line 2052

    How can this be fixed?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Akshay A

    (@akshaycode1)

    Hi,

    Thank you for reaching out to us. Could you please confirm which version of PHP you are currently using?

    Thread Starter fpablo

    (@fpablo)

    8.1

    Plugin Support Akshay A

    (@akshaycode1)

    Hi,

    We apologize for the delayed response. A GitHub ticket has been raised regarding this concern, and it will be addressed in the upcoming update. We kindly request your patience in the meantime.

    Here is the GitHub Ticket.

    Plugin Support Akshay A

    (@akshaycode1)

    Hi @fpablo ,

    Hope you doing well.

    We’ve recently released an update that addresses this issue. Please update the plugin to version 1.1.3, clear the cache once and give it a try. Feel free to reach out if you have any concerns.

    Thread Starter fpablo

    (@fpablo)

    Thank you!

    Plugin Support Akshay A

    (@akshaycode1)

    We are closing this thread. If you need any assistance, please let us know. Have a great day!

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.