Advanced Access Manager and BulletProof Security

  • Resolved Roswebnet

    (@roswebnet)


    12 years, 2 months ago

    Hi everyone

    After installation and configuration of the Bulletproof Security plug-in on a website I got immediately strict standards errors in other plugins. Removing or deactivating the bulletproof settings does not resolve the problem.

    Only after disabling Advanced Access Manager 1.5.8.2 (beta) all things began to work in the right way.

    After short test I found that only Advanced Access Manager 1.5.6 working good with or without Bullet Proof .46.8.

    Maybe it is an server issue?

    Thank you

    P.S.: Advanced Access Manager is a great plug-in which improves WordPress functionality and security, but sometimes it cost too much to configuration it correct.
    P.P.S.: I really miss import export feature or it is another issue which appears by me?

Viewing 10 replies - 1 through 10 (of 10 total)
  • AITpro

    (@aitpro)

    12 years, 2 months ago

    From your troubleshooting steps it is not clear whether you completely removed BPS for Testing purposes. You would do this by putting the site in Default Mode and deleting the wp-admin .htaccess file on the Security Modes page.

    AAM deals with adding access to wp areas with Roles. BPS does not do anything with Roles besides Super Admins in MU for displaying the BPS menus. So I do not see any sort of direct conflict here, but i will test AAM to see if any conflicts exist.

    Thread Starter Roswebnet

    (@roswebnet)

    12 years, 2 months ago

    In first stage I completely removed the BPS and all BPS made htaccess files. it does not solve the problem.

    In second stage the clean install of the WP en the AAM does not helps me too.

    I think it is more about server. However, I have strange feeling about it, because just before installing BPS everything seems works ok.

    AITpro

    (@aitpro)

    12 years, 2 months ago

    Well if you don’t use Default Mode then what is left behind is an .htaccess file in your Root folder. Deactivating BPS deactivates the plugin files and deleting BPS deletes the plugin files, but these 2 things do not remove the .htaccess file and your website’s security. Putting your site in Default Mode adds a default WordPress .htaccess file in your Root folder and using Delete wp-admin file removes the wp-admin .htaccess file. In the past having the website security removed on deleting BPS resulted in peoples websites getting hacked so i decided not to automatically delete a website’s security when deleting BPS. The control is all within BPS now. This tends to be safer and people make less mistakes now and I rarely ever get a complaint any more about those types of mistakes.

    Once i test this plugin i will let you know if there are any conflicts. Thanks.

    Thread Starter Roswebnet

    (@roswebnet)

    12 years, 2 months ago

    Misunderstanding 🙂
    I put firstly everything on default mode, than I removed BPS and as last step I deleted and reinstall WP without BPS well with AAM 1.5.8.2. Obviously, I am continuing getting php strict standards error in whole site.

    Please see the screenshot:
    http://roswebnet.com/bugs/install.jpg
    http://roswebnet.com/bugs/aam.jpg

    Only version of AAM 1.5.6 with this fix works correct:
    http://wordpress.org/support/topic/plugin-advanced-access-manager-php-fatal-error-with-aam-156?replies=6

    AITpro

    (@aitpro)

    12 years, 2 months ago

    Oh ok this is not a BPS problem. Got ya. This is a problem with AAM only ok thanks.

    vasyl_m

    (@vasyl_m)

    12 years, 2 months ago

    Hi guys,
    I’ll check this issue as soon as possible and let you know the result.

    Regards,
    Vasyl

    AITpro

    (@aitpro)

    12 years, 2 months ago

    And i thought i would just throw in my 2cents explanation of why you are probably seeing these errors. PHP5 has new stricter coding standards so if you have backwards compatibility coding in a plugin for PHP4 then it will probably trigger these types of php errors. I think these days it is safe to get rid of all PHP4 backwards compatibility coding. I’m pretty sure all reputable web hosts have PHP5 as the standard default these days. And no one should be using PHP4 any more. 😉

    vasyl_m

    (@vasyl_m)

    12 years, 2 months ago

    Hi guys.
    Actually this is not a problems. This is just because in my last AAM release I have display_error mode ON. That is why u see all this warnings. To deactivate it just go mvb_config.php and comment next line:
    //ini_set(‘display_errors’, FALSE);
    In next release I already fixed this inconvenience.
    AITpro I guess u have error handling function in your plugin which just overwrite mine 🙂

    Regards,
    Vasyl

    AITpro

    (@aitpro)

    12 years, 2 months ago

    I did not actually test your plugin, but yep I have a custom php.ini file set up in BPS Pro. 😉

    Thread Starter Roswebnet

    (@roswebnet)

    12 years, 2 months ago

    Hi Vasyl

    by me ini_set was already commented, so this does not help me. Howevere, when I did:
    21| //error_reporting(E_ALL | E_STRICT);
    22| //ini_set(‘display_errors’, FALSE);

    in mvb_config.php file it fix my problem.

    Thank you for tip and great plugin.

    P.S.: AITpro, thank you too for help and great plugin which made my WP instalation much secure.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Advanced Access Manager and BulletProof Security’ is closed to new replies.