Update to 3.0 causes critical error

  • Resolved maximiliana1

    (@maximiliana1)


    6 months, 3 weeks ago

    Hello,

    I have updated the plugin to 3.0 but this causes a critical error so that I had to return to the last version before (2.15). I use Contact Form 7 (5.9.8) with the plugin.

    The following is the error log:

    [26-Aug-2024 19:06:46 UTC] PHP Fatal error: Uncaught Error: Call to undefined function forge12\contactform7\CF7DoubleOptIn\createTableOptOut() in /var/www/html/wp-content/plugins/double-opt-in/OnUpdate.php:23

    Stack trace:
    #0 /var/www/html/wp-content/plugins/double-opt-in/OnUpdate.php(29): forge12\contactform7\CF7DoubleOptIn\onUpdate()
    #1 /var/www/html/wp-content/plugins/double-opt-in/CF7DoubleOptIn.class.php(30): require_once(‘/var/www/html/w…’)
    #2 /var/www/html/wp-settings.php(522): include_once(‘/var/www/html/w…’)
    #3 /var/www/html/wp-config.php(133): require_once(‘/var/www/html/w…’)
    #4 /var/www/html/wp-load.php(50): require_once(‘/var/www/html/w…’)
    #5 /var/www/html/wp-admin/admin-ajax.php(22): require_once(‘/var/www/html/w…’)
    #6 {main}
    thrown in /var/www/html/wp-content/plugins/double-opt-in/OnUpdate.php on line 23

    I would appreciate your help. Thank you!

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

  • Hello,

    Thank you for bringing this to our attention. It seems that the issue is related to the function createTableOptOut() in the OnUpdate.php file. As a workaround, you can manually edit the OnUpdate.php file by removing the line containing createTableOptOut() (line 23) to prevent the critical error.

    Alternatively, if you’re not comfortable with making changes to the code, we are releasing an update later this month that will address this issue.

    We apologize for the inconvenience and appreciate your patience. Please let us know if you need any further assistance.

    Best regards,
    Marc

    Thread Starter maximiliana1

    (@maximiliana1)

    Thank you very much for the new update.

    Everything works fine now. ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Update to 3.0 causes critical error’ is closed to new replies.