• Resolved simbian

    (@simbian)


    Hi, i have two different WP installations, one in the root folder and another in a sub dir (the subdomain that i have created point to that folder), im in a shared hosting.

    I firstly have installed the plugin on the second wp installation (the one in the sub dir), i have activated it and when i tried to activate Full WAF mode it said that can’t be activated: “Make sure your HTTP server support the php_value auto_prepend_file directive in .htaccess files. Maybe you need to restart your HTTP server to apply the change, or simply to wait a few seconds and reload this page?”

    Then i disabled the plugin and installed the plugin in the first wp installation (the one in the root folder) with success and full WAF mode enabled. In the configuration i excluded the sub dir of the second wp installation.

    Now when i try to enable the plugin in the second wp installation it gives me an error that the plugin can’t be activated because there is a fatal error.

    I then disabled the plugin in the first wp installation and tried to activate it in the second wp installation but still gives me the fatal error message.

    How can i activate the plugin also on second wp installation and make the full WAF mode working?

    Thanks in advice.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author nintechnet

    (@nintechnet)

    Check the PHP error log, it will show what that error is about.
    If you don’t have a PHP error log, you need to enable debugging in WordPress:

    1. Edit your wp-config.php file.
    2. Search for:
      define('WP_DEBUG', false);
    3. Replace with:
      define('WP_DEBUG', true);
    4. Add this line below:
      define( 'WP_DEBUG_LOG', true );

    Try to enable the firewall until you get the error and then check the log that will be saved to “/wp-content/debug.log”.

    Thread Starter simbian

    (@simbian)

    Hello, i had Cloudflare active and maybe this was interfering with the activation of NinjaFirewall, now is all ok!

    Thanks for the support.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.