PHP Fatal error after v1.82 update

  • Resolved George Tasioulis

    (@georgetasioulis)


    8 months, 2 weeks ago

    Hello,

    After updating the plugin to v1.82, websites stop working with the following fatal PHP error:

    [11-Jul-2025 13:28:03 UTC] PHP Warning:  require_once(/home/[username]/sites/[domain]/wp-content/plugins/google-captcha/includes/forminator.php): failed to open stream: No such file or directory in /home/[username]/sites/[domain]/wp-content/plugins/google-captcha/google-captcha.php on line 34
    [11-Jul-2025 13:28:03 UTC] PHP Fatal error:  require_once(): Failed opening required '/home/[username]/sites/[domain]/wp-content/plugins/google-captcha/includes/forminator.php' (include_path='.:/opt/alt/php74/usr/share/pear') in /home/[username]/sites/[domain]/wp-content/plugins/google-captcha/google-captcha.php on line 34

    I checked the SVN repo, and it indeed looks like the forminator.php file is not there.

Viewing 12 replies - 1 through 12 (of 12 total)
  • wojsmol

    (@wojsmol)

    8 months, 2 weeks ago

    Hi @georgetasioulis

    /includes/forminator.php in not there because Forminator redintegration is a Pro feature. As a temporary fix you can replace line 34 in /wp-content/plugins/google-captcha/google-captcha.php from

    require_once dirname( __FILE__ ) . '/includes/forminator.php';

    to

    //require_once dirname( __FILE__ ) . '/includes/forminator.php';
    casper

    (@caspervoogt)

    8 months, 2 weeks ago

    Yes, there definitely should be a check e.g.;

    if (file_exists(dirname( __FILE__ ) . ‘/includes/forminator.php’)) {
    include_once dirname( __FILE__ ) . ‘/includes/forminator.php’;
    }



    Users of the free version should not be running into critical errors just from updating the plugin; the above should solve that.

    • This reply was modified 8 months, 2 weeks ago by casper.
    • This reply was modified 8 months, 2 weeks ago by casper.
    • This reply was modified 8 months, 2 weeks ago by casper.
    Moderator Support Moderator

    (@moderator)

    8 months, 2 weeks ago

    If you are not the original poster and you need support then per the forum guidelines please start your own topic.

    https://wordpress.org/support/forum-user-guide/faq/#i-have-the-same-problem-can-i-just-reply-to-someone-elses-post-with-me-too

    The many “I have this problem too” replies have been removed. Please start your own topic instead.

    martin9870

    (@martin9870)

    8 months, 2 weeks ago

    I am free user and it crashed my site completely. Do you test your updates before releasing them??? I doubt it.

    terry777

    (@terry777)

    8 months, 2 weeks ago

    I also just received messages both from Sucuri security and from wordpress. The site is down. Free version.

    jeremyckahn

    (@jeremyckahn)

    8 months, 2 weeks ago

    The update crashed my site as well. Please consider making @caspervoogt’s recommended change. I’m not familiar with this plugin’s development process but I would be willing to submit a PR if you could send me in the right direction.

    arga7

    (@arga7)

    8 months, 2 weeks ago

    after update new version
    same from me, fatal error
    temporary disable
    need fix please

    bigmikestudios

    (@bigmikestudios)

    8 months, 2 weeks ago

    Free version threw a fatal error on my site also. I am following this thread. I have had many years enjoying this plugin problem-free, and will re-install it when it looks like it’s been fixed.

    glodenox

    (@glodenox)

    8 months, 2 weeks ago

    I’ve gone for the approach to add a dummy (empty) forminator.php in the includes folder of the plugin. But commenting out the require_once or adding a file presence check also solves the issue. It looks like they didn’t test the free tier properly and then made the classic mistake of deploying a change on Friday 😅.

    Tushar Sharma

    (@richeal)

    8 months, 2 weeks ago

    Just comment this line in plugin main file, google-captcha.php at line no. 34. It will sort out issue.
    //require_once dirname( __FILE__ ) . '/includes/forminator.php';

    • This reply was modified 8 months, 2 weeks ago by Tushar Sharma.
    tripledm

    (@tripledm)

    8 months, 2 weeks ago

    Did you even test the free version? Appreciate your work and contribution but you literally crashed a ton of sites on few servers for me as no more auto update for sure and definitely wait a month before updating the plugin.

    Plugin Support andrewsupport

    (@andrewsupport)

    8 months, 2 weeks ago

    Hi,

    Thank you to everyone who helped and responded to questions on our behalf while we were working on fixing the vulnerability.
    We truly appreciate your support and would like to sincerely apologize once again for any inconvenience caused.

    If you are still experiencing any issues with your site or our plugin after the latest update, please don’t hesitate to contact our support team — our specialists will be happy to assist you: https://support.bestwebsoft.com/hc/en-us/requests/new

    Thank you — you are the best!

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

The topic ‘PHP Fatal error after v1.82 update’ is closed to new replies.