David S

Why was the issue arising in the first place? Was anyone ever able to determine why the error message was displaying as “critical” and why it’s shown? Why does this error message show in some sites and not others? If you have 10 sites hosted by the same hosting provider shouldn’t all sites show the same error?

I know it’s marked as “resolved,” but there’s no mention as to why it occurred as a critical error in the first place.

Thanks for your response.

So just to understand what you’re saying, go to Settings, General, Membership, uncheck Anyone Can Register and then if I do that… how exactly can I let new members join the forum?

Do they email me through the contact form, request membership and then I can send them a link or add them manually as Subscribers to the WP back-end and then they should also be members and able to post to BBPress forums?

If I add them manually they still won’t be able to do anything on the forum, though, right, since joining will still be disabled…?

I have a course that’s already gaining some traction so would love to have a forum to go with the course that could be members only. I’m just not sure if I can achieve that or how to do it.

I just want to be able to understand what you’re describing so I can make it actionable…and the fewer the plugins the better for obvious reasons.

• This reply was modified 4 years ago by David S.

Hi, @rogierlankhorst all I can tell you right now is that when I saw that error message I sent you, I took that screenshot, which I saw in other sites as well before. I then clicked refresh and it appeared to be normal. I have NOT updated to the next version of Really Simple SSL as many of my sites are running ClassicPress (the WP 4.9 fork) so I wanted to ask if that could have caused the error message or what may be going on. My sites are hosted w/Blue Host yet I have very strong wifi at home – just not great with SSL.

I can try updating the plugin on some demo sites in the meantime. I’ll read some more on it as well.

@markwolters I noticed everything in the back-end blinking out after updating actually to 3.2.1 and received this error message that took the entire page.

Is this a security issue we should be concerned with? Can you please update what’s going on?

Here is a screenshot:

https://www.dropbox.com/s/p7nzuhjwen2dosq/ClassicPress%20update%20Really%20Simple%20SSL%20glitch.png?dl=0

@yorman I appreciate your insights and am only asking as someone who is using ClassicPress to keep my older legacy sites alive. I did not want to risk breaking my sites with the 5.0 update and also had other concerns on switching over to 5.0/Gutenberg. So having 1 reliable security plugin to use with those sites is obviously a big deal. WordFence requires several settings be turned off or it sends off 80-something error messages constantly. If Sucuri could work for ClassicPress with minor adjustments I for one would certainly appreciate it and would pass that on to their community.

Thanks for whatever you can do. Please let me know what happens one way or another.

You should consider getting in touch directly because our post is likely to be banned or removed very soon as the other references were and we may be banned or removed as well for even mentioning it.

So far I have not seen a definitive response from WordFence. I’m sure they’re very busy dealing with Gutenberg bugs and fixes, and other issues. As far as I know so far WordFence works fairly well with ClassicPress (as it should since ClassicPress is just a fork of 4.9) but some changes need to be made to the settings so you don’t get 800 or so error messages. The changes WordFence needs to make on their side of things impact 2 settings primarily.

I’m also moving many older client sites over to ClassicPress out of necessity, as Gutenberg does not seem to have any backward compatibility for older sites.

Jeff’s plugin is a great blessing at the last minute. If there are any issues with it I’m telling my clients to switch to ClassicPress or doing it for them tonight for a minor additional fee. That way they don’t have to worry about any broken formatting or compatibility issues.

Did you just leave the 860 or so alerts or run a new scan to remove them?

Maybe I need more caffeine but I looked for it and could not find it. I’ll try again. I would like them to support CP as well. Don’t know what they need in order to consider it.

I have the same issues. I am letting the folks at ClassicPress know, and honestly trying to change these alerts as known will literally take weeks with 861 alerts.
WordFence is pretty much useless with ClassicPress with all the false positives,

Their input was:

After installing ClassicPress, uncheck this option: “Scan Options → General Options → Scan core files against repository versions for changes“. There will also be a few more errors if you have the “Scan wp-admin and wp-includes for files not bundled with WordPress” option enabled, because ClassicPress has added new files. Currently this is normal and expected.

The problem is that the “Scan core against repository versions” is no where to be found. Where is it?

You have to go into the Cpanel for your host and find the plugin folder and remove it from there or use FTP if you are familiar with that. Also, with Gutenberg coming out any day now, I would definitely check everything if you continue to use it. Just my humble opinion. I don’t know how the plugin developers feel….

Okay…so you do not have any issues any longer or you do? Sounds like everything is now okay. Maybe you updated, saw the issue, updated again and then the issue went away?

Jagrav when exactly did you update? I’m running this plugin on a few sites and have not seen the update yet.

Update: Blue Host ran some tests and said everything looked fine on their end but that somehow the “How does WordFence detect IP addresses” was unchecked. They said this could be a bug or caused by an update but by simply checking the appropriate box, the issues seems resolved.

But I don’t know if there is a weird glitch with a very recent update or something else that caused it – so just FYI in case you guys want to know.