Problems with the “Subscribe To Comments Reloaded” plugin

The new Setup Wizard AutoFix whitelist rule added for the Subscribe To Comments Reloaded plugin would not cause this problem. If it was causing the problem then your WordPress Dashboard would have gone blank when you ran the BPS Setup Wizard and not when you upgraded BPS.

Things that can cause this type of problem:
* A direct coding conflict with plugin code – we tested these 2 plugins together and did not find a direct coding conflict problem.
* You are close to using your maximum PHP configuration memory limit and when performing plugin upgrades, activations or installations you exceed your maximum PHP configuration memory limit. Check the BPS System Info page > PHP Configuraion Memory Limit.
* You have some invalid/bad htaccess code saved in BPS Custom Code – not very likely since the problem would occur when running the Setup Wizard.

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

Typo|Correction: “…and did not find a direct coding conflict problem…”

Hi, thanks for the quick response.

With respect to php this is what I have:
PHP Actual Configuration Memory Limit: 256M
PHP Ver.: 5.6.30

The same day that BulletProof was updated, these plugins were also updated:
Yoast SEO
Relevanssi
EWWW Image Optimizer
Accelerated Mobile Pages
WP-Optimize

I do not understand why this happens, until version 2.9 everything worked wonders.

I only have the wordpress menus in the dasboard, when I click on any of the menus it does not show me anything in the center, except if I deactivate bulletproof that returns everything to normality.

Can it be a css failure or one of the improvements introduced?

Update: I discovered that if I go to: BPS Security – Setup wizard – Setup wizard Options, and changing AutoFix On by AutoFix Off, the problem no longer occurs.

What do I lose if I leave AutoFix Off?, is it safe to leave it like this?

Great clue! I found the bug (dumb typo) in the new Setup Wizard AutoFix checking code for the Subscribe To Comments Reloaded plugin (was looking at BPS code in the wrong place). I will get a new version of BPS out ASAP with the fix. For now it is fine to turn off AutoFix and that just means that if you add/install any new plugins or themes and a fix is needed then AutoFix will not display a message to run AutoFix. For any existing plugins and themes installed there is no impact.

BPS Pro uses this code for AutoFix checks:

	if ( $sctocr_active == 1 || is_plugin_active_for_network( $sctocr ) ) {
		if ( ! preg_match( $marker2, $bps_customcode_bpsqse ) || ! preg_match( $marker3, $bps_customcode_bpsqse ) || ! preg_match( $marker4, $bps_customcode_bpsqse ) ) {
			$autofix_message = bpsPro_autofix_message($autofix_message);
			$debug_BPSQSE .= __('CC Root Text Box 12: Subscribe To Comments Reloaded Plugin', 'bulletproof-security').'<br>';
		}		
	}

And BPS free uses this code for AutoFix checks:

	if ( $sctocr_active == 1 || is_plugin_active_for_network( $sctocr ) ) {
		if ( ! preg_match( $marker2, $bps_customcode_bpsqse ) || ! preg_match( $marker3, $bps_customcode_bpsqse ) || ! preg_match( $marker4, $bps_customcode_bpsqse ) ) {
			$autofix_message = 1;
			$debug_BPSQSE .= __('CC Root Text Box 12: Subscribe To Comments Reloaded Plugin', 'bulletproof-security').'<br>';
		}		
	}

The mistake was actually a copy and paste mistake from BPS Pro to BPS free. Forgot to change: $autofix_message = bpsPro_autofix_message($autofix_message);
to: $autofix_message = 1;

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

The person who did the final BPS free Live site test forgot to test with the Subscribe to Comments Reloaded plugin installed. Oops. It happens. ??

Hello, I had this exact problem with screen blanking in wordpress after updating to BPS 3.0 today. I have “Subscribe to comments reloaded” installed and thus found this great support thread.
Amending the line:

$autofix_message = bpsPro_autofix_message($autofix_message);

to

$autofix_message = 1;

in the file “plugins/bulletproof-security/includes/hud-autofix-whitelist.php” solved the issue and all returned to normal. Thanks for the information and the great plugin.

BPS 3.1 has been released with the fix for the Subscribe To Comments Reloaded plugin.

Confirmated! This Bug is solved in the 3.1 version.