You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There looks to be a nasty bug in 2.32.0+ (not present in 2.31.2) that results in data loss. If a Person has an associated staff account, and you edit that staff account (e.g. to adjust their permissions, or mark them active/inactive), then all that person's custom fields are lost.
To replicate:
Add a custom field if none exists yet. E.g. here I've got a 'MultiCF' field:
On a Persons page for someone with an associated staff account, set the custom field. E.g. here the value is 'bar':
In Admin -> User Accounts, find the account and 'edit' it. This is the first sign of a problem: the custom field doesn't show, whereas previously (in 2.31.x) it did:
Fill in your 'current password' and click 'Update Account'.
View the Person record. You'll note the custom field is gone. The History shows it has been blanked out:
The text was updated successfully, but these errors were encountered:
As for the bug cause: I reckon it's the missing custom fields on the edit_user_account form. Jethro 2.31 showed all custom fields. In 2.32 only a handpicked 5 show. Perhaps, when submitted, the edit_user_account code sees "hm, no custom fields. Blank them all!"
The change may have originated in c7301ca where the $fields variable changed from containing all fields, to containing just 5.
There looks to be a nasty bug in 2.32.0+ (not present in 2.31.2) that results in data loss. If a Person has an associated staff account, and you edit that staff account (e.g. to adjust their permissions, or mark them active/inactive), then all that person's custom fields are lost.
To replicate:
Fill in your 'current password' and click 'Update Account'.
View the Person record. You'll note the custom field is gone. The History shows it has been blanked out:
The text was updated successfully, but these errors were encountered: