Using Trigger "After a user's profile has been updated" to redirect to another page will keep you from being able to update your users username or other user account settings.

From the users profile page (using the core profile module) I wanted users to verify their info and upon confirmation (saving the form) they would be redirected to the front page. This did not work at first. Trigger and Profile have the same module weight and the trigger redirect was happening before the profile save. I had to set trigger's weight higher in the system table to get it to work as expected. I set it to 20 in my case.

(I see there are numerous issues being logged related to this problem. Please see http://drupal.org/node/403446 for example.)

After this though the users main Account page (user/uid/edit) will not save any changes (the page containing the username, password, etc). Trying to save changes will fire the redirect before the save occurs and this is not related to the modules weight as far as I can tell.

To replicate create a user, add an action to redirect the user to any URL, add the action to the Trigger "After a user's profile has been updated" under the User tab at 'admin/build/trigger/user' and then try to update the user's account information.

I'm posting this for others who might run into this problem or the mentioned module weight issue as it seems common without very many responses indicating that being the cause.

Comments

andypost’s picture

Status: Active » Closed (duplicate)
Anonymous’s picture

Had the same problem, fixed as above by changing the weight in the system table of "trigger" module to 20.

Anonymous’s picture

Status: Closed (duplicate) » Active

Update - this works for profile fields, but not for updating the user's email address or password. Stumped! Anyone?

Anonymous’s picture

Quick update - I got around this issue by using the Rules module instead. It doesn't seem to interfere with updating the password or email address and you can set up a redirect that way.

Status: Active » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.