Deprecation errors with PHP 8.4

  • Resolved John

    (@dsl225)


    1 month ago

    Hello,

    When upgrading to PHP 8.4 from 7.4 I got those errors:

    Deprecated: Forminator_Admin::clear_pages_cache(): Implicitly marking parameter $post_id as nullable is deprecated, the explicit nullable type must be used instead in /wp-content/plugins/forminator/admin/classes/class-admin.php on line 1328

    Deprecated: forminator_replace_lead_form_data(): Implicitly marking parameter $entry as nullable is deprecated, the explicit nullable type must be used instead in /wp-content/plugins/forminator/library/helpers/helper-fields.php on line 2666

    Deprecated: forminator_replace_form_payment_data(): Implicitly marking parameter $entry as nullable is deprecated, the explicit nullable type must be used instead in /wp-content/plugins/forminator/library/helpers/helper-fields.php on line 2359

    Deprecated: forminator_replace_form_payment_data(): Implicitly marking parameter $custom_form as nullable is deprecated, the explicit nullable type must be used instead in /wp-content/plugins/forminator/library/helpers/helper-fields.php on line 2359

    Deprecated: forminator_replace_form_data(): Implicitly marking parameter $entry as nullable is deprecated, the explicit nullable type must be used instead in /wp-content/plugins/forminator/library/helpers/helper-fields.php on line 561

    Deprecated: forminator_replace_form_data(): Implicitly marking parameter $custom_form as nullable is deprecated, the explicit nullable type must be used instead in /wp-content/plugins/forminator/library/helpers/helper-fields.php on line 561

    Deprecated: ActionScheduler_QueueCleaner::__construct(): Implicitly marking parameter $store as nullable is deprecated, the explicit nullable type must be used instead in /wp-content/plugins/forminator/library/external/src/Forminator/woocommerce/action-scheduler/classes/ActionScheduler_QueueCleaner.php on line 35

    Deprecated: ActionScheduler_Abstract_QueueRunner::__construct(): Implicitly marking parameter $cleaner as nullable is deprecated, the explicit nullable type must be used instead in /wp-content/plugins/forminator/library/external/src/Forminator/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php on line 34

    Deprecated: ActionScheduler_QueueRunner::__construct(): Implicitly marking parameter $async_request as nullable is deprecated, the explicit nullable type must be used instead in /wp-content/plugins/forminator/library/external/src/Forminator/woocommerce/action-scheduler/classes/ActionScheduler_QueueRunner.php on line 39

    Anything I can do?

    Thanks.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Amin – WPMU DEV Support

    (@wpmudev-support2)

    Hello @dsl225

    Hope you are doing well today.

    Thank you for bringing this issue to our attention, I asked our development team to review and investigate further.

    Please note these are warnings and should not cause any issues with form functionality and you can ignore them at this point.

    Kind Regards
    Amin

    Plugin Support Amin – WPMU DEV Support

    (@wpmudev-support2)

    Hello @dsl225

    I would like to update you regards the current issue, we confirmed it is a bug in the plugin and happens when using PHP 8.4, unfortunately, the fix requires updating the plugin code but we already reported it to our developers.

    We can’t give an estimated time yet for the fix but subscribing to our roadmap https://wpmudev.com/roadmap/ is a good way to be posted about upcoming versions, once they are released, it is going to be described at changelog found on https://www.ads-software.com/plugins/forminator/#developers

    Since the bug was acknowledged, reported and tasked to be fixed, we are marking this as resolved, but feel free to let us know if you have any additional questions.”

    Kind Regards
    Amin

    Thread Starter John

    (@dsl225)

    Great, many thanks!

    Please note that the current WP version 6.7.1 is not yet fully compatible with PHP 8.4 and this is, I think, scheduled for the next version. So maybe this issue is related.
    Also, I tested with PHP 8.3 and those deprecation errors do NOT exist anymore.

    Plugin Support Amin – WPMU DEV Support

    (@wpmudev-support2)

    Hello @dsl225

    I passed the information to our development team, and it is normal that PHP 8.4 is new, so many plugins, themes, and even WordPress may not yet be fully compatible with it.

    You can use PHP 8.3 for now and give the developers some time to get their codes fully compatible with the new PHP version.

    Best Regards
    Amin

    Thread Starter John

    (@dsl225)

    Many thanks for your kind feedback.
    I confirm, I did that and switched to 8.3 and those notices stopped and everything woks fine.
    I also learned that WP 6.7.1 latest version is not yet fully compatible with version 8.4.

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