[buddypress-trac] [BuddyPress Trac] #5575: Deleting Users in Manage Signups Leaving Database Entries

buddypress-trac noreply at wordpress.org
Wed Apr 23 18:35:49 UTC 2014


#5575: Deleting Users in Manage Signups Leaving Database Entries
-------------------------------------------------+-------------------------
 Reporter:  aaclayton                            |       Owner:
     Type:  defect (bug)                         |      Status:  new
 Priority:  high                                 |   Milestone:  2.0.1
Component:  Administration                       |     Version:  2.0
 Severity:  major                                |  Resolution:
 Keywords:  needs-testing has-patch reporter-    |
  feedback 2nd-opinion                           |
-------------------------------------------------+-------------------------

Comment (by aaclayton):

 So, I'm no longer 100% certain about what is causing the issue I
 originally reported. I created this ticket based on database behavior I
 was experiencing in a local test environment. I ended up rolling out my
 theme changes for BuddyPress 2.0 to my live site (expecting to deal with
 the same issues which prompted my ticket) only to find different (but also
 not-intended) behavior.

 I am at work all day today and can't dig too deeply into the code to track
 down what might be happening, so for the short term allow me to provide a
 lot of information about my setup in hopes that it will spark some ideas
 on your end.

 '''My Setup'''
 I'm running WordPress (3.9) single-site with BuddyPress (2.0) and bbPress
 (2.5.3). No other relevant plugins are in-play.

 '''On My Local Environment'''
 On my local test site, upgrading to BuddyPress 2.0 created a wp_signups
 table which had not previously existed. New user registrations would
 create the following:

 1) An entry in wp_users with user_status = 2 and user_activation_key =
 <key>
 2) Entries in wp_usermeta for default WordPress meta, activation_key =
 <key>, and registration_ip = <ip> (a custom usermeta I save for new
 accounts).
 3) An entry in wp_signups which was fully populated

 Deleting an un-activated user through the Manage Signups panel would
 remove item (3) but leave all records in (1) and (2) intact. Deleting an
 un-activated user with the BuddyPress Pending Activations plugin would
 remove all records in items (2) and (3), but leave (1) intact.

 I tested and replicated this process using both my own custom theme and
 the default WordPress 2013 theme.

 '''On My Live Site'''
 On my live site environment, upgrading to BuddyPress 2.0 '''did not'''
 create a wp_signups table. New user registrations are creating:

 1) An entry in wp_users with user_status = 2 and user_activation_key =
 <key>
 2) Entries in wp_usermeta for default WordPress meta, activation_key =
 <key>, and registration_ip = <ip> (a custom usermeta I save for new
 accounts).

 No un-activated users are displayed in the new BP2.0 Manage Signups
 interface, I presume this is because the wp_signups table was not created
 and no users are assigned the "pending" role.

 I am still able to use the BP Pending Activations plugin on my live site
 to delete both (1) and (2).


 I'm not certain why a wp_signups table was not created when BuddyPress was
 upgraded to 2.0. I assume this was the expected behavior? Is there any
 information I can provide that could help determine whether this is some
 flaw in BP itself or a peculiarity of my specific setup?

 Please let me know what would be the most helpful from my end.

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/5575#comment:5>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac


More information about the buddypress-trac mailing list