Doesn't hold new registrations for approval

Had your earlier post in my queue to respond to but hadn’t gotten to it quite yet, until now.

One of the bigger things I switched in the latest release is how a user is flagged. Before it was using the user_status field from the wp_users table. Now it should be setting a meta key/value in the wp_usermeta table and querying based on that. Specifically this key: _bprwg_is_moderated and a value of “true”.

Not sure if you still have any of those users that slipped through, but I’d be curious if that meta value was being set at all, and if it isn’t, then that’s the likely start of any bugs that somehow slipped through. If it’s not, then something later in the process isn’t working like expected.

Would be interested in seeing it happening firsthand if possible, as it was working in my test environment.

Thanks for responding.

Unfortunately, I deleted all the spam users. I’ve reverted to 4.1.3, which is working as before.

When I get a chance – maybe over the weekend? – I can try upgrading again and letting a few users through, then looking at them in the database.

I am also running BP XProfile User Sync – don’t know if there might be a conflict between it and the latest version of BP Registration Options… It gets along fine with 4.1.3.

Shouldn’t be a conflict with that plugin, ours isn’t touching anything that it would.

If you could gather some information for me, that’d be awesome to help me debug what may be going on. I’m in talks with someone else to see if I can repeat results you’re seeing. People who have active sites instead of my localhost “bare” version.

Actually, I have another site using the plugin – https://sunygeneseoenglish.org

It’s stopped working there since the upgrade, too. However, right now I’m limiting registrations to users from one particular domain, so it doesn’t matter that they’re able to bypass moderation.

What this means, though, is that the last few registrants are still there (since they’re not spammers), so I can look at them in the database.

Anything I should look for besides what you mentioned above about the value in wp_usermeta?

I think any information on that user meta key and how many users have or don’t have it set to “true” would be enough for the moment

I’m not an experienced SQL user, but here’s what I find when I browse wp_prefix_usermeta (this is a WP multisite installation):

For every user up through the last one that the plugin held for moderation, I see a meta_key of “bprwg_ip_address” with the user’s IP as meta_value.

For users since the plugin stopped holding for moderation, I see no key beginning “bprwg”

Hello.
I’ve just updated too and it lets new members straight in as soon as they click on the activation email that is sent out. I did a test to prove it. I also use User Manage Sign ups, not sure if there is likely to be a conflict there.

https://clandestinecakeclub.co.uk

Thankfully I have Spam captcha to help keep the spammers out.

I’ll see if I can get the previous version restored until the problem is resolved.

Thanks

Lynn

whatthedickens, the underscore at the front is important, if you were using an SQL query like SELECT * FROM wp_usermeta WHERE meta_key = 'bprwg_is_moderated' If there are meta key/values stored, you’ll need to search for _bprwg_is_moderated or do a LIKE search like so: SELECT * FROM wp_usermeta WHERE meta_key LIKE '%bprwg%'

Lynn and whatthedickens,

Just to be certain, you both have the “moderate new users” and “Only registered or approved members can view BuddyPress/bbPress pages” options checked, correct?

Also note, that our plugin doesn’t prevent people from accessing the site as a whole, it’s meant to prevent them from accessing the BuddyPress and bbPress areas only. They’d still be able to see the blog area for example.

If you are aware of that, and not what you’re getting at, then my apologies for that part. The next question is if they’re still showing up in the moderation queue list, or if they are not even touching that part at all.

Just trying to cover all bases.

In 4.2, they don’t show up in the moderation queue at all. In 4.1.3, the plugin successfully holds all new registrations for moderation.

I did have those two options checked.

The information I provided earlier about wp_prefix_usermeta came from browsing the table. I’m afraid I don’t know how to write queries. However, when I enter the query

SELECT * FROM wp_prefix_usermeta WHERE meta_key = ‘_bprwg_is_moderated’ (that is, with underscore included), I get an empty result.

When I enter the query

SELECT * FROM wp_prefix_usermeta WHERE meta_key LIKE ‘%bprwg%’ I get 150 results, showing umeta_id, user_id, meta_key, and meta_value. In all 150 results, the meta_key is ‘bprwg_ip_address’ and the meta_value is the user’s IP address.

Hold on.

I only have the first option checked: “Moderate New Members.”

I don’t have the second option checked on either of my sites.

On one site, I’ve reverted to 4.1.3, and the plugin successfully holds registrations for moderation with just the one option checked.

On the other site, running 4.2, the plugin doesn’t hold registrations and nothing appears in the queue. There, too, I only have the first option checked.

Hello Michael!

Thanks by the plugin!

A problem is occurring: After the last update it stopped working.

What could have happened?

I did a test with a fictitious user and noticed that he no longer sends email activation and the User is sent to pending.

Thank you for your attention.

Cheers

I have the same problem. New members go straight through. They are not held for moderation. This was working fine in the previous version. I did check the settings and they are correct, although the updated plugin is not holding new members for moderation. I have checked this many times with fictitious members.

Thank you everyone for the reported feedback. I assure you I was testing, but I realized now that a couple use cases slipped by me. I believe I have enough information to test those out and will be doing so soon, and will push out the update once ready. Hoping to get around to this tonight due to the urgency in it and amount of reports.

I apologize for the inconveniences so far. It was not intentional.

Michael,

Thanks for all that you do. I really appreciate your work on this great plugin. We are standing by for the updates.

Wayne Rowlands