user submodule is borked

I don't know about 7 but for 6 it is pretty darn ugly. When the 'form' is loaded set a static cache of the account removing the form_build_id from the object, unserialize the object->$data and remove the form_build_id element from the array. On the 'after_update' move the $account variable to another variable in order to do the dance with form_build_id so that you can compare the before image and after image copies to know if you need an update. You have to remove the form_build_id because the values are different in the before and after.

HTH

I've added a note to Known Issues that will need removed once this is corrected.

Dave, I've been trying to determine why xmlsitemap_user module isn't saving the changes to include or exclude the user in the sitemap. I see that xmlsitemap_process_form_link_options() is added to the #submit array and it is called, however that function doesn't do the save. Instead it is waiting for xmlsitemap_user_user_update() hook implementation to do the save but the $account variable doesn't contain the changed value and neither does the $edit variable.

Is there a reason not to save the data on submit? What purpose is accomplished in waiting for the hook_*_update() function? I realize if we refactor this piece that we must do so for all entities.