Closed (fixed)
Project:
U Create
Version:
6.x-1.0-beta2
Component:
ucreate.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Nov 2009 at 17:05 UTC
Updated:
5 Nov 2009 at 09:53 UTC
Jump to comment: Most recent file
Comments
Comment #1
marc.groth commentedChanging title to be more clear and changing status for patch to be reviewed
Comment #2
alex_b commentedYeah, this drupal_goto() needs to go.
Shouldn't $form['#redirect'] be defined in ucreate_user_form() ? I think it does not have an effect in submit callbacks.
Comment #3
tayzlor commentedWhy does the hook_user() even have to exist? Why do we have to redirect the user to change password upon login? If they want to change password they can go to their edit account page.
the hook_user does in fact break other login modules behaviour such as logintoboggan.
Comment #4
marc.groth commentedYou're right alex_b, an oversight on my part. Thanks :)
Attached is a new patch (to be rolled instead of the previous one) which removes drupal_goto() altogether and adds the code $form['#redirect'] = $_GET['q'] to the end of the code in ucreate_user_form() function.
Agree with tayzlor... ucreate_user() seems rather redundant and unnecessary. Can this be removed too?
Comment #5
marc.groth commentedAttaching patch...
Comment #6
alex_b commented#5 patches the original patch. Here is a patch against UCreate HEAD.
Comment #7
alex_b commentedCommitted, thank you.
Comment #8
tayzlor commentedre-opening.
This patch does not play nice with content_profile_registration module.
Again, i ask, is there a need for the hook_user() implementation here?
If someone really wants to go to change their password (again) they can through the edit profile link on their profile.
The problem occurs because the content_profile_user_register_submit() function which fires after the ucreate submit one does not get a chance to fire.
Comment #9
alex_b commentedHang on, isn't the hook_user() issue a different issue? The patch doesn't change anything with that.
If that's the case, please close this issue and open a new one with a description of the problem. I'm open to addressing the hook_user() issue, but I'd like to avoid issue drift.
Comment #10
marc.groth commentedalex_b you are correct, this is a separate issue which I have created here: http://drupal.org/node/624082
Closing this as the original issue has been resolved.