Does BPS Login Security & S2member conflicts still continue?

These are the only 2 issues that we are aware of:

1. Last Test Results: 8-2014: https://forum.ait-pro.com/forums/topic/bulletproof-conflict-with-s2member/#post-16727

S2Member version: 140725 and BPS Pro 9.2 test results:

BPS Pro Login Security works fine with S2Member as long as these 2 S2Member options below are not being used or have been set to “off” in S2Member (more explanation below for the meaning of off).

S2Member Restriction Options Menu:

Brute Force IP/Login Restrictions option
Unique IP Access Restrictions option

S2Member will override BPS Pro Login Security if the 2 S2Member options above are being used / are turned “on”.

How to turn “off” S2Member Brute Force IP/Login Restrictions & Unique IP Access Restrictions:

1. Go to S2Member Restriction Options and make sure these 2 options below are set like this:
2. Brute Force IP/Login Restrictions: Allow Infinite failed logins (Brute Force Restrictions disabled)
3. Unique IP Access Restrictions: Allow Infinite IP’s (All IP Restrictions are disabled)
4. Click the Save All Changes button/option.

Or of course you can turn Off BPS Pro Login Security and use S2Member login security features.

2. Last Test Results: 3-2014: https://forum.ait-pro.com/forums/topic/s2member-protected-page-403-error/

S2Member – Protected page 403 error
Create a plugin Skip/Bypass rule for the S2Member plugin in BPS Custom Code.

1. Copy the S2Member plugin skip/bypass rule below to this BPS Root Custom Code text box: CUSTOM CODE PLUGIN/THEME SKIP/BYPASS RULES
2. Click the Save Root Custom Code button.
3. Go to the BPS Security Modes page and click the Root Folder BulletProof Mode Activate button.
IMPORTANT Note: Add the actual path to where your S2Member protected page is, using the general example below.

# S2Member protected URL rewrite / redirect bypass
RewriteCond %{REQUEST_URI} ^/example-URI-path/example-registration-page/ [NC]
RewriteRule . - [S=13]

So this means the s2member login conflict/problem still continues?

I guess if you want to look at it like that. Basically what is happening is BPS and S2Member have standard login processing functionality in certain features that are very similar or the same and the S2Member protected page issue is a procedural whitelisting issue and not a conflict. Neither of these 2 issues are technically a conflict or problem.

Issue #1: The WordPress Login page and login processing is a special case that only allows one plugin or plugin feature to process/handle logins via a standard WordPress Login Hook. If 2 plugins use the same Login Hook then 1 plugin will always override the other plugin’s Login Hook. Or in other words, it is not possible to have 2 plugins using the same standard WordPress Login Hook and have both plugins process logins because whichever plugin’s action or filter Hook with the higher priority used in a login function will fire first and handle login processing.

Issue #2: S2Member protected pages cannot be automatically created by the new Setup Wizard AutoFix feature (we are not planning on digging into the S2Member code to figure out how to get all protected pages from the WP DB for S2Member) since technically this is not a “broke/fix” situation. So this falls under a procedural whitelist category. ie for each S2Member protected page add an individual specific unique whitelist rule with the URI of the S2Member protected page in BPS Custom Code.

• This reply was modified 7 years, 4 months ago by AITpro.
• This reply was modified 7 years, 4 months ago by AITpro.
• This reply was modified 7 years, 4 months ago by AITpro.
• This reply was modified 7 years, 4 months ago by AITpro.

Assuming all questions have been answered – the thread has been resolved. If you have additional questions about this specific thread topic then you can post them at any time. We still receive email notifications when threads have been resolved.