Hi there,
When my administrator account creates a new users, everything works great with bio. A new user is created with a new biography. I have bio set to takeover the profile and it's doing great.
But when a new user comes to the site and registers....no biography is created for that user. They have to go in and make it themselves.
What's the hold up? How do I fix this? thanks.
Comments
Comment #1
bflora commentedI just sank 4 hours into testing this.....
1. I've got two biography fields exposed to the registration form. Both required.
2. When a user fills them in and submits the form....they're taken ot their profile page instead of the bio.
3. The bio hasn't been created. The settings they put on the registration form were not saved.
My Theory: The settings form the submissions form aren't being saved for some reason...and so Bio doesn't know to create a biography module for the new user.
What could cause the settings from the registration form to not be saved? That might be the root of the problem.
Comment #2
bflora commentedI think I'm sorted out. I was using LoginTobbagan to let users login immediately upon signing up...and so the bio node wasn't being created when they first showed up on the site. Ok.
Comment #3
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #4
joshk commentedThe issue here is that node.module in core sets the $form['uid'] to be a value on the back-end if a new node is being created, and this is synced with the global $user. So the admin ends up creating more bios for him/herself.
Adding a single line to bio_form_alter will fix this:
Hopefully this will get added. Otherwise, it's not hard to do via a different form_alter.
Comment #5
allie mickaSeems reasonable. Committed! Thanks!
Comment #6
bflora commentedYou're on a roll!