Community Support Forums

Hey Guys, hadn't heard back from the contact form submission and wanted to followup. Thanks!

Thanks for your patience.
I'm just about to take a look this now.

Thanks for your patience.
I've just finished taking a look at your database.

This problem is caused by a corrupted database.
If you load up phpMyAdmin for your database, and go to the SQL tab at the top.

Paste this in and press GO.

Code: Select all

SELECT * FROM `wp_usermeta` WHERE `meta_key` LIKE 'wp_capabilities' ORDER BY `wp_usermeta`.`user_id` DESC

You'll notice there are duplicate entries for wp_capabilities in your wp_usermeta table, and this is why the numbers are coming out wrong within WordPress. You can rid yourself of this problem, by going through the list of entries and deleting the duplicates.

How did this happen? I'm not sure. I can tell you this is the first time this issue has been reported, and I'm not aware of anything in the s2Member plugin that would cause this. My best guess is that the plugin you're running W3 Total Cache, which has "Object Caching" enabled, somehow caused this, either directly or indirectly, but it's really difficult to say for sure, that's really just a wild guess at this point. If you can pin this to a specific plugin or plugin combination, please report back and let us know!

RE: Your email. No I hadn't seen this. I'll try your solution and I'll pretty quickly if it keeps happening. Just disabled object caching W3 Total Cache as well.

Also, find it incredibly odd it only happens with the subscriber level and no others

Ok, still having the problem.

Of course, removing all the duplicates reports the numbers correctly and it now lists 20 users on the page instead of 11 like before. I added a test user and the count only increased by one but that was through the 'Add User' form in wp-admin

Tried using the Pro Form here: http://bit.ly/pulOZn and it added two entries again. So the issue still remains.

Once again, disabled object caching and it still only happens for the subscriber level. Back to square one

Have you tested this with a default theme for WordPress® too? Like plugins, themes come with a functions.php file which could potentially cause conflicts as well. If you can please run your test with the default theme for WordPress® and report back with your findings. If the problem persists, I'll be happy to take another look at your database.

Just tested it again before changing theme per your suggestion and it worked fine. Who knows man. Maybe the object caching wasn't being respected yet when I tested it before. Will let you know if something else happens but something tells me object caching was the problem. Thanks so much for your help and wonderful support! Anyone reading should buy the Pro version.

This issue is happening again. It's creating 3 entries for first name and last name.

Should have been more specific. The exact thing were capabilities are added twice is happening again. It didn't happen on the first few and then it started again. Nothing changed on our end. I have no idea here.

You're using the auto-login after registration hack, right? Have you tried without it to see if that's what's causing this problem?

That hack is turned off because of the other outstanding issues I have

Thanks for the follow-ups. Sorry for the delayed response.
OK. Can you please submit a Dashboard login for me here?
http://www.s2member.com/contact/

Never mind. I found your previous email.

seofeed wrote:That hack is turned off because of the other outstanding issues I have

Got it.

OK, regarding this problem, are you using a caching plugin? Have you tried disabling it to see if that solves the problem?

In case that was the cause, you may want to try another caching plugin like Jason's Quick Cache. https://wordpress.org/extend/plugins/quick-cache/

Thanks for the updates.

I've taken a closer look at this, but so ar I've been unable to reproduce this behavior outside the installation reported in this ticket. If anyone has this problem, please report it here so we can continue to look for anything within s2Member that may or may not be causing this.

At this time, I have to assume this behavior is a result of object caching plugins not keeping SQL updates in-sync properly, possibly leaving a corrupted database in its path. My advice, don't use W3 Total Cache for object caching. Either that, or don't use W3 Total Cache at all, go with Quick Cache.