BulletProof Security Forum

Try locking your Root htaccess file to prevent other plugins and themes from “flushing” (doing a wp rewrite flush) or writing to your Root htaccess file.

1. Go to the BPS Pro > B-Core > htaccess File Editor tab page
2. Click the Lock htaccess File and Turn On AutoLock buttons.

If you cannot lock your Root htaccess file due to web host…[Read more]

Do not change the Site Address (URL) option setting.  Change the WordPress Address (URL) option setting to:  https://boydhanaleiako.me/boydhanaleiako

WordPress Address (URL) – is the WordPress installation folder URL. Internally (WP DB) what this option setting does is it contains the actual file/folder path to your WordPress installation f…[Read more]

So just change the “Site Address”. I’m not exactly sure how the two addresses are differently used.

Site address (URL) is the WordPress setting for the website URL that is displayed to visitors. So your website URL would still be the same.  Logically nothing would change except that since BPS uses the WordPress address (URL) option setting for the path to the actual WordPress installation folder then BPS would now write to the htaccess file in…[Read more]

I’m thinking more about bruting for other sub-directories…. There’s also the whole aesthetic of the URL.

You could turn Off all BPS Pro Dashboard Alerts on the BPS Pro > S-Monitor page, but for obvious reasons you would not want to do that.  Troubleshooting blind is no fun at all.  😉

The Additional Roles IP Whitelist tool is for automatically whitelisting the IP addresses for anyone that is logged in under one of your standard WordPress User Roles or any of your Custom User Roles.  That tool does not do anything with general BPS Pro Dashboard alerts.  I’m pretty sure that if one of Custom User Roles includes the standard W…[Read more]

LEGENDARY SUPPORT AS ALWAYS!!!

Added the user role and saved, and voila! They can no longer see BPS alerts and notifications!!!!

Both BPS Firewalls ok again. THANK YOU!!!!!!

These people are not administrators, but we created a new roll from scratch for them.

So if I add their roll to the firewall whitelist, does that mean they will be blocked from seeing the BPS alerts and notifications?

On the first site “church” the problem was that Plugin Firewall Test Mode was turned On. I turned Off Test Mode and that fixed the problem. On the “biblecollege” site I did not see a broken page layout, but went ahead and did the Plugin Firewall “reset” steps listed in my previous forum reply.

I see that you have several different Custom User…[Read more]

The BPS Dashboard alerts are only displayed to Administrators. Are these people Administrators?

On a separate note, can I disable BPS Pro Dashboard notifications and display for certain users? We limit them for things we do not want them to see so they are less confused etc.

No cloudflare or minify as per your previous suggestions. I have emailed login credentials for you to check.

Ok are you using a Cloudflare plugin or minifiying/combressing/combining js scripts?  These 2 other common things that break the BPS Pro Plugin Firewall that require additional configuration changes.  If you do not have either of these things going on then do the steps below to reset/fix this issue.  Note: Choose either the general fix steps or th…[Read more]

I have completely removed WP Hide & Security Enhancer PRO plugina week ago already, so it cannot be that.

When the BPS Pro plugin page layout is broken that means there is a problem with the BPS Pro Plugin Firewall.

You mentioned in one of your other forum topics that you have the WP Hide & Security Enhancer PRO plugin.  The Hide My WP plugin is known to break several things in BPS Pro including the BPS Pro Plugin Firewall.  So it is very p…[Read more]

From a Browser no one would be able to “poke” around in any of your hosting account directories.  If you are talking about someone “poking” around at your hosting account file/folder level then that would be game over. Only hosting account user accounts have access to hosting account file/folder/directory level stuff.