- 🇦🇺Australia purencool
Registration really should be done on the parent site. This allows for all data to sync to the child site reducing the likelihood of polluting the dataset.
If someone attempts to register on a slave site (i.e. no user account on the master either), then the only form values passed to the master are the four in $allowed = array('name', 'mail', 'pass', 'timezone');. The end result is the user account on each site omits all other values submitted on registration. So, if a user wants to update their account, e.g. to set the password after using the one-time login link, then they need to re-enter all of the form values included on registration. On each site, potentially.
This practice seems a bit self-defeating in light of issues like #556666: Sync hooks: Enable sharing of arbitrary data → dealing with data syncing to the slave sites when user account is updated on the master.
Allow all form values to be sent to the master AND to be returned to the slave (if the slave requires email validation so that an account will also be established on the slave)? The form values will automatically be included in the calls to user_save().
Review, write tests, update documentation.
None, except that registration form values will show up on each site when viewing a user account.
None.
🐛
Support extra query arguments along with query destination and during registration
Closed: outdated
- this adds a special exception to send and return the query argument in the oatmeal cookie
- this seems very similar to sending all the form values on registration, as proposed here
#556666: Sync hooks: Enable sharing of arbitrary data →
Closed: outdated
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Registration really should be done on the parent site. This allows for all data to sync to the child site reducing the likelihood of polluting the dataset.