Timeline for Store information from hook_form_alter to be used in later hook_user_update?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 23, 2013 at 12:45 | vote | accept | Software Prophets | ||
| Nov 23, 2013 at 0:57 | answer | added | Joe Corall | timeline score: 3 | |
| Nov 22, 2013 at 22:15 | comment | added | Software Prophets | I hesitated to mention that I'm interested in password information because that opens the door to all kinds of comments about worries regarding doing anything with a password. It seems like everyone becomes a security expert when the word password shows up. So, I opened the door, I'm hoping that anyone viewing this can just stick to the question and not get all worried about passwords! $form_state['input']['pass']['pass1'] would be the primary thing I'm after. I have some secondary targets, but I may be able to get that information from hook_user_update | |
| Nov 22, 2013 at 18:42 | comment | added | m1r1k |
It would be much easier to provide a good advice if you give some more information about data, that's available in hook_form_alter and not available in hook_user_update. Also if you just add custom #submit callback to user_profile_form_submit form, it will run AFTER drupal saves user and invokes hook_user_update.
|
|
| Nov 22, 2013 at 16:02 | history | tweeted | twitter.com/#!/StackDrupal/status/403916403855880192 | ||
| Nov 22, 2013 at 13:16 | history | asked | Software Prophets | CC BY-SA 3.0 |