4.3.0 and fatal errors in crons

  • Resolved Vincent Poirier

    (@magikweb)


    1 year, 1 month ago

    On multiple sites, we now get a “Uncaught ArgumentCountError” fatal error.

    Here are two examples:

    Fatal error: Uncaught ArgumentCountError: 8 arguments are required, 7 given in /home/customer/www/magikweb.net/public_html/wp-content/plugins/popup-builder/com/helpers/AdminHelper.php:1208

    Fatal error: Uncaught ArgumentCountError: 5 arguments are required, 4 given in /home/customer/www/librairiewilsonlafleur.com/public_html/wp-content/plugins/popup-builder/com/helpers/AdminHelper.php:999

    These two sites are “Multisites”, maybe it has something to do with it. The crons are executed by the server (we don’t use the native WP crons).

    Thank you for your help!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Jawad Ahmed

    (@jawada)

    1 year, 1 month ago

    Hi @magikweb

    We apologise for the inconvenience. We are currently investigating and working to resolve the reported issue. In the meantime, we recommend using an older version of the plugin.

    https://wordpress.org/plugins/popup-builder/advanced/

    Please follow these steps to download it:

    1. Visit the provided link.
    2. Scroll down to “Advanced Option.”
    3. Under “Please select a specific version to download,” click on the dropdown menu and choose the version you wish to download.
    4. Upload this version to your WordPress site and replace the existing plugin.

    This workaround should address the issue temporarily. We expect to release a permanent fix in the next version of the plugin.

    Thank you for your patience and understanding.

    Best regards,

    Popup Builder Team

    Thread Starter Vincent Poirier

    (@magikweb)

    1 year, 1 month ago

    Thank you! That was very good support. ♥

    Thread Starter Vincent Poirier

    (@magikweb)

    1 year ago

    The error persists after 4.3.2, is it still a known bug or it was possibly fixed with the latest updates?

    Just asking to make sure this isn’t ignored or thought as fixed.

    Thanks for the great work!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘4.3.0 and fatal errors in crons’ is closed to new replies.