[buddypress-trac] [BuddyPress Trac] #8139: Network Invitations and Membership Requests

[buddypress-trac]

#8139: Network Invitations and Membership Requests
--------------------------+-----------------------
 Reporter:  dcavins       |       Owner:  (none)
     Type:  enhancement   |      Status:  assigned
 Priority:  normal        |   Milestone:  6.0.0
Component:  Registration  |     Version:  5.0.0
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+-----------------------

Comment (by dcavins):

 Thanks for your feedback, Boone. Yes, it would be much simpler to not
 change the actual registration process, so let's start there.

 One question I have about your flow (which mostly matches what I was
 imagining, probably because I've used Invite Anyone for a long time), is
 that you say:

 ----
 When we detect key=12345 on the register page, we check for a matching
 signup, and perhaps pre-fill some of the info, like email.
 ----

 This makes it sound like when a user invites a new member, a bare record
 is created in the `wp_signups` table. Is this what you were intending? I
 was imagining that an invitation would be created, and the `wp_signup`
 would be created when the user responded (and the various hooks around
 signup would be fired then, rather than at invitation). In your scenario,
 when a user "registered" they'd be updating an existing signup, but as far
 as most plugins were concerned, it would be a registration.

 It's an interesting approach, and I'll think more about how we can
 interact with the `wp_signups` table as part of an invitations/request
 process and still keep the existing important hooks around registration
 intact.

 Thanks!

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