Closed (duplicate)
Project:
Drupal core
Version:
7.0
Component:
user system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Feb 2011 at 20:11 UTC
Updated:
13 May 2011 at 15:09 UTC
Jump to comment: Most recent file
Comments
Comment #1
Chris Gillis commentedI am also having this issue.
It seems this would only be a matter of changing line 547 from
if (isset($edit['status']) && $edit['status'] != $account->status) {to
if (isset($edit['status']) && isset($account->status) && $edit['status'] != $account->status) {Comment #2
lyricnz commentedThe sample code above doesn't cause this error because you're not attempting to set status (which is where the notice comes from). Here's real sample code
In this case, I think the correct fix is to check the status being saved (in $edit) against the $user that was just loaded, not the one passed in $account.
Comment #4
lyricnz commented#2: user-save-status-change-1049090.patch queued for re-testing.
Comment #5
lyricnz commentedThere are other problems in the same area - this is probably covered by #999004: user_save() relies on $edit instead of $account.