Error mysql warnings and duplicate emais

Do you have any other plugins active as you try #1? I don’t use that function directly at all, and any DB interactions I do are through the WordPress API or the wpdb class. Also, could you screenshot the email received that is causing this? I know there will be multiple emails sent out with the whole process because of BuddyPress activation, and then also ours. The only links I can recall that we send ourselves are just to WP admin urls. So I’m curious if it’s not directly related to ours. However, I can’t tell for sure without a stack trace of calls used.

Which version are you using? I know I have a new version that I need to release, and that may fix the issue above with the multiple emails, though I can’t guarantee.

Hi I waited for the release of your new version, this has seemingly fixed the random error message I was getting…..BUT!

When in the admin area its telling me that I have two new users awaiting awaiting approval when I go to the approval page it shows no users.

Have tried clearing the cache but to no avail.

The email situation is the same, get two emails sent one with the user details the other with out, both emails have the same heading
‘New Member Request’

I moved the “Pending Users” count to a transient, which isn’t going to be cleared by browser cache.

However, it should only exist up to 5 minutes. I also have it set up that the transient *should* be getting deleted after approving/denying. May not be perfect, but it’s pretty simple.

Regarding the emailing. Do you have a development copy of the website anywhere that you could disable all other plugins for, except BuddyPress and BPRO.

Hi Michael, I tried the script on my beta website with no issues inc email whatsoever with all plugins apart from buddypress de-activated, once activated it is fine.

However even disabling all plugins on my main website and ensuring your plugin is not affected by my cdn, w3tc or cloudflare it was still showing as two users pending and also creating duplicate users when i test it.

Im starting to wonder if its a database issue?

Just to help me confirm things from a different thread, your 4.2 copy still catching and queuing users correct?

Transients are stored in the wp_options table.

Example:

1995 _transient_timeout_bpro_user_count 1409169960
1996 _transient_bpro_user_count a:1:{i:0;s:1:”2″;}

Each transient has 2 fields, one for when it is supposed to expire by, and one for the actual stored data.

If you could check for those and report back what you find, that’d be awesome.

Yes it is still catching a queuing users but duplicating them and then once I approve them the usernames vanish and it then still shows as two users awaiting approval but with no names?

73010 _transient_timeout_bpro_user_count 1409246449
73011 _transient_bpro_user_count a:1:{i:0;s:1:”0″;}

Is this what you’re looking for?

Looks legit, the transient is storing “0” which it should be if there’s none new. Why it’s showing two somewhere is a good mystery though.

Is there any chance at all you’d be willing to let me in and see first hand? Or is that asking a bit too much? Thus far I haven’t seen consistent issues, anyone who’s reported something has been different.

I’m more than happy to give you access

If you could send me the credentials necessary to michael @ webdevstudios.com that’d be awesome.

As it turns out, the user ID of 1 got the meta key intended to denote spam as well. The issue with this is that you don’t have any existing users with that ID right now. Because of that, the values couldn’t end up being changed by clicking around, and were stuck.

So, a couple things need to be done by me, and the sooner the better.

1) I need to check that the user does indeed exist before updating the meta table.
2) I need to make sure to only have 1 field with this value in it. While I was looking around, I noticed you had duplicate listings which led me to see that there were 2 matching key/values but different meta table IDs.

Thank you for letting me in, and even more for the hosting access because that’s what helped out the most. Access to the database to check on values there. Hopefully I can get a 4.2.1 release out soon. I’m certain I’ll be having some other things fixed as I have had people tell me it’s not catching like it should.

Look forward to updates ?? and glad to help out with the errors in anyway i can

out of interest when and if will the next version be released to the general public?

Once I’m done double checking things and ready to release the 4.2.1 version ??

I have now uninstalled this plugin pending an updated version of the plugin with fixes.