Closed (fixed)
Project:
LoginToboggan
Version:
7.x-1.5
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
15 Jun 2009 at 19:24 UTC
Updated:
29 Aug 2017 at 19:02 UTC
Jump to comment: Most recent
Logintoboggan overwrites $form['#submit'], squashing my previously defined custom user_register_submit function. The code is set up to not clobber the function, but during my testing this was the case. I've attached a patch which fixes the issue.
| Comment | File | Size | Author |
|---|---|---|---|
| logintoboggan_user_register_submit.patch | 536 bytes | mikehostetler |
Comments
Comment #1
hunmonk commentedcommitted to 6.x-1.x-dev and HEAD.
thanks and sorry for the delay!
Comment #3
tayzlor commentedre-opening this as i am still experiencing this problem.
if i use the content_profile_registration function in conjunction with logintobban and do the following -
expose a content field to the registration form.
on submit what should happen is -
- logintoboggan_user_register_submit should run and process the login.
- content_profile_user_register_submit should run after the above and process the extra content fields on the form and save the node in the database.
if i set immediate login to ON the 2nd function does not run. If i set immediate login to OFF - it will process the 2nd submit function and save the node. I'd ideally like to use immediate login.
Also changing the version as i've upgraded to 1.6 and the problem persists.
Comment #4
tayzlor commentedupon further inspection it seems another module i have installed is messing up the process - UCreate, if i comment out the hook_user in that module, logintoboggan runs its course fine. Moving this to the UCreate issue queue and will expand on the issue there.
Comment #5
tayzlor commentedactually, closing this, will re-open another issue over there.
Comment #6
threegI still seem to be experiencing an issue with this if "immediate login" is turned on.
I've written a module that's adding it's own submit callback to the user_register_form. It's adding it after logintoboggan_user_register_submit (I am altering the module's weight, but I get the same issue even if I don't do this).
Right now, all that callback is doing is dpm'ing a message to see if the callback is fired.
With "immediate login" on it doesn't fire. If I turn it off, or comment out line 533, then it fires.
Digging a little deeper, it actually seems the act of loading the user in logintoboggan_process_login, seems to cause the other callbacks to stop firing.