Settings page blank & not referencing wp-config constants

  • I recently updated to WP-Fail2ban 4.2.2 and my previously recognised constants are no longer visible in the WP-fail2ban settings window.

    The settings are either blank even though they have defined constants, or they are using the default WP-fail2ban constants. I am running PHP 7.2. I am bit confused as to why this is happening and I wouldn’t mind rolling back WP-Fail2ban to the last version that worked for me. If that is an option.

    • This topic was modified 5 years, 10 months ago by overturn.
    • This topic was modified 5 years, 10 months ago by overturn.
Viewing 4 replies - 16 through 19 (of 19 total)

  • Hi,

    In my case it’s running on a Debian 8 environment, PHP 7.1, Apache 2.4 with a Nginx reverse proxy.

    The _load function seems to set the WP_FAIL2BAN_PROXIES to false in my case (which it does when it can’t find a certain variable I believe, I don’t have the code in front of me right now).

    I can run it through a debugger if you can’t find it but I’ll need some more time, let me know.

    Thanks!

    Plugin Author invisnet

    (@invisnet)

    Yes, it should set it to false if it’s not been defined and there’s no default value; the question is why the define isn’t being found.

    Can you change line 35 in lib/loader.php to:

    if ( !defined( $define ) ) {

    and see if that works?

    Plugin Author invisnet

    (@invisnet)

    @overturn and @sjhand – are you using OpCache?

    Thread Starter overturn

    (@overturn)

    Hi, sorry for the delayed reply. I am using Redis Object Cache

Viewing 4 replies - 16 through 19 (of 19 total)
  • The topic ‘Settings page blank & not referencing wp-config constants’ is closed to new replies.