Wordfence autoloader problems on Google App Engine standard

  • Resolved marcinkrawiec

    (@marcinkrawiec)


    3 years, 1 month ago

    Hi!

    I have problems with activating Wordfence on Google App Engine standard, runtime php74.

    I’m getting the following error when trying to activate the plugin:

    Fatal error: Uncaught Error: Call to a member function getStorageEngine() on null in /workspace/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/config.php:16
Stack trace:
#0 /workspace/wp-content/plugins/wordfence/lib/wordfenceClass.php(591): wfWAFConfig::set('wafDisabled', false)
#1 /workspace/wp-content/plugins/wordfence/lib/wordfenceClass.php(88): wordfence::runInstall()
#2 /workspace/wp-includes/class-wp-hook.php(307): wordfence::installPlugin('')
#3 /workspace/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)
#4 /workspace/wp-includes/plugin.php(474): WP_Hook->do_action(Array)
#5 /workspace/wp-admin/plugins.php(194): do_action('activate_wordfe...')
#6 /workspace/gae-app.php(63): require('/workspace/wp-a...')
#7 {main}
  thrown in /workspace/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/config.php on line 16

    The vendor subdirectories are uploaded (double checked in app source in the cloud console).

    It has nothing to do with the fact that GAE has not writable file system. I got similar errors for other plugins as well.

Viewing 1 replies (of 1 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @marcinkrawiec, thanks for reaching out to us.

    With setting up on Google, we need to make sure that the AllowOverride is set for the directory or the WAF will not have the access it needs. However, this is traditionally required for firewall optimization rather than activation of the plugin. I feel that it would be worth trying in your case regardless so we can rule it out as a cause.

    Navigate to your wordpress.conf file and add the following:

    <Directory /var/www/html>
Options -Indexes
AllowOverride All
</Directory>

    You should also check the config files in /etc/apache2/sites-available/. If one of those has its own AllowOverride set to a different value for /var/www/html, it would need to be changed in that file instead.

    Let me know if you have any further issues or information about your configuration. You do mention that this is happening for other plugins also, so there’s a chance WordPress itself is encountering the problem rather than specifically Wordfence.

    Thanks,

    Peter.

Viewing 1 replies (of 1 total)
  • The topic ‘Wordfence autoloader problems on Google App Engine standard’ is closed to new replies.