Fatal Error: Call to a member function getGlobal() on null

  • Hi there –

    My site started returning 500 results for every request with the following error and stack trace:

    PHP Fatal error: Uncaught Error: Call to a member function getGlobal() on null in /wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/rules.php:1809#012Stack trace:

012#0 /wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/rules.php(1823): wfWAFRuleComparisonSubject->getRootValue('request.cookies')

012#1 /wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/rules.php(1806): wfWAFRuleComparisonSubject->getValue()

012#2 /wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/rules.php(1823): wfWAFRuleComparisonSubject->getRootValue(Object(wfWAFRuleComparisonSubject))

012#3 /wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/rules.php(719): wfWAFRuleComparisonSubject->getValue()

012#4 /wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/rules.php(1478): wfWAFRuleComparison->evaluate()

012#5 /wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/rules.php(159): wfWAFRuleComparisonGroup->evaluate()

012#6 /wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php(376): wfWAFRule->evaluate()

012#7 /wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php(281): wfWAF->runRules()

012#8 /wp-content/plugins/wordfence/waf/bootstrap.php(985): wfWAF->run()

012#9 /wordfence-waf.php(10): include_once('/li…')

012#10 /usr/local/share/auto_prepends/auto_prepends.php(55): require_once('/li…')

012#11 {main}#012 thrown in /wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/rules.php on line 1809

    Can you please advise?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support wfscott

    (@wfscott)

    Thanks for your patience. We’ve identified a Premium rule that was released earlier today that was causing conflicts on some sites that updated to the latest rules. We’ve implemented a fix on our side to prevent the issue from occurring on sites that have not yet been updated and we are continuing to work on a fix for sites that have updated to the latest rules. In the meantime, if the site is down, you can rename the Wordfence folder in wp-content/plugins to deactivate the plugin temporarily. We will post here shortly with more information.

    Plugin Support wfscott

    (@wfscott)

    Thanks again for your patience. At this point, it appears only sites utilizing a MySQL storage engine are affected. Sites hosted on WPEngine are likely to be affected.

    One way to fix this issue manually while we look towards an automated solution is to manually run the following query on your database, which should clear the rule and remove any errors:

    DELETE FROM wp_wfconfig WHERE name='wafRules'

    We recommend taking a backup of your database prior to running the query. If you are unsure of how to run a manual query on your database, we recommend reaching out to your hosting provider for assistance.

    Plugin Support wfscott

    (@wfscott)

    One more update — unfortunately, due to the nature of this issue, it does not look like we will be able to offer an automated solution to resolve the error on affected sites.

    As mentioned previously, if your site is currently down, you can use FTP or file manager to rename the wordfence folder in the wp-content/plugins directory (rename wordfence to wordfence.disabled for example) to bring the site online. At that point, we recommend trying to use the option provided in my last message to manually update the database in order to restore normal functionality to the site. If you are not comfortable working with the database, please reach out to your host as they should be able to assist you with that. At that point, you can reactivate the plugin going forward.

    While using the database query from my last message, if you notice the issue is not resolved, confirm if your table instead has an uppercase C (wp_wfConfig), in which case you would need to use the following:

    DELETE FROM wp_wfConfig WHERE name='wafRules'

    Being that this only affected Premium users, please be sure to reach out to us in Premium support using the Get Help button under your license in our Licenses area if you have any questions.

    Plugin Support wfpeter

    (@wfpeter)

    Please follow the instructions provided by @wfscott above if you are affected, although we are now aware (as others here are reporting) that this seems isolated to the premium version.

    However, we cannot respond to further issues or supplementary questions about the premium plugin here on the forums provided for our free product by www.remarpro.com so please open a support ticket at https://support.wordfence.com if you do need to know any more.

    You can also access premium support via the Help menu item in the plugin, Help link on the plugin’s Dashboard page, on our documentation homepage or via the HELP link in the footer of all wordfence.com pages.

    Thanks!

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    However, we cannot respond to further issues or supplementary questions about the premium plugin here on the forums provided for our free product by www.remarpro.com so please open a support ticket at https://support.wordfence.com if you do need to know any more.

    Good reply. I archived all of the many “I have this problem too” replies and I am closing this topic.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Fatal Error: Call to a member function getGlobal() on null’ is closed to new replies.