• Resolved batters22

    (@batters22)


    After updating to 3.0.1 immediately generated fatal error on the site:

    An error of type E_PARSE was caused in line 128 of the file /home/simonbat/public_html/subdomains/dartefacts/wp-content/plugins/paid-memberships-pro/includes/level-groups.php. Error message: syntax error, unexpected ‘)’

    Running WP 6.4.3 on PHP 7.2.

    Editing line 127 of the above file to change from:

        array( '%s', '%d', '%d', '%d' ),

    to

        array( '%s', '%d', '%d', '%d' )

    seems to have fixed the issue.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Jarryd Long

    (@jarryd-long)

    Hi there, thank you for reaching out to Paid Memberships Pro and sharing this feedback.

    Do you have any steps on how I can replicate this error? Would I need to save a level or do anything else to recreate this?

    Kind Regards,
    Jarryd
    Support Manager at Paid Memberships Pro

    Thread Starter batters22

    (@batters22)

    Hi Jarryd

    All I did was install the update, previously running 2.12.10. The error appears immediately on installing the update.

    Plugin Support Jarryd Long

    (@jarryd-long)

    Thank you for your feedback. I’ve shared your feedback with the development team for further review and testing.

    In the meantime you can continue using the plugin with those changes in place, or consider updating to PHP 8.1 if you can as this would also likely resolve the error.

    Feel free to reach out if there’s anything else we can assist with.

    Kind Regards,
    Jarryd
    Support Manager at Paid Memberships Pro

    Thread Starter batters22

    (@batters22)

    Thanks for the response. By experimentation the issue disappears in PHP7.4 and higher.

    Plugin Author Andrew Lima

    (@andrewza)

    This is an issue related to PHP 7.2 and resolved from PHP 7.3+

    We are looking to fix this by removing the trailing comma to help sites running PHP 7.2 and should be included in a future release of Paid Memberships Pro.

    I’m sorry for the inconvenience caused by this.

    +1. Please remove the trailing comma with the next update.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Fatal error after updating to 3.0.1’ is closed to new replies.