PHP 8.2.30

  • Resolved andreag100

    (@andreag100)


    3 weeks, 5 days ago

    Some error triggered twice:
    Un errore di E_COMPILE_ERROR è stato causato nella linea 21 del file /home/customer/www/startupgeeks.it/public_html/wp-content/plugins/wp-rss-aggregator/core/src/Logger/PostLogger.php. Messaggio di errore: Declaration of RebelCode\Aggregator\Core\Logger\PostLogger::log($level, $message, array $context = []) must be compatible with Psr\Log\AbstractLogger::log($level, Stringable|string $message, array $context = []): void

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Hendra Setiawan

    (@hendcorp)

    3 weeks, 4 days ago

    Hi @andreag100

    Thank you for reporting this, and for sharing the error message.

    To help us better understand your setup and narrow this down, could you please confirm the following:

    • Which version of Aggregator are you currently using?
    • If you’re on version 5.0.12, has the migration to version 5 been fully completed?
    • Did this issue start after updating PHP or the plugin?

    In the meantime, as a temporary workaround, you may try switching your site to PHP 8.1 to see if the issue is resolved.

    Once we have a bit more information, we’ll be happy to take a closer look and guide you on the next steps.

    Looking forward to your reply.

    Thread Starter andreag100

    (@andreag100)

    3 weeks, 4 days ago

    Hi, thank you for the quick reply. Seems happened randomly as it has stopped. The PHP version has not been downgraded yet, WP RSS Aggregator is on version  5.0.12, migrated.
    The error happened recently not specifically after an update.

    Thank you
    Regards

    Plugin Support Hendra Setiawan

    (@hendcorp)

    3 weeks ago

    Hi @andreag100

    Thank you for the update. It’s good to hear that the error has stopped on its own.

    Since the issue is not consistently reproducible and is no longer occurring on your end, it may have been triggered temporarily under specific conditions.

    For now, I’d recommend keeping an eye on it. If the error appears again, please let us know what action triggered it. This will help us reproduce the issue and investigate further.

    In the meantime, I’ve also shared this with our development team so we can review and ensure full compatibility with PHP 8.2.

    Thanks again for reporting this, and please don’t hesitate to reach out if it comes up again.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.