Edge case: Update Email

[jensscherbl]

I have a form which allows logged-in members to change their account data.

The corresponding event has the Members: Update Password-filter attached, so members can change data like name (default Input-field) etc.

They also can change their email-address (Member: Email-field), which I use as the primary identifier.

After saving the entry (with the new email-address), the member is automatically logged out, which is confusing.

If a member changes their password, the Members: Update Password-filter will log them back in automatically. This does also work when emai-address AND password are both changed or re-entered, but not if only the email-address was changed and the password-field was left empty.

I guess I can implement an additional Members: Update Email- or Members: Update Username-filter myself, but wanted to hear some feedback on this edge case before getting my hands dirty.

[designermonkey]

What about the username field? Does that have the same logging out behaviour too? If so then it should be resolved with a Members: Update Identity Field filter.

[jensscherbl]

Didn't test with the Member: Username-field, but I guess it would be the same issue.

Simpler solution would be to get rid of the Members: Update Password-filter as well and always force members to re-enter the password when editing their member-entry.

Question is, should we simplify the Members-extension or cater for every possible use-case?

[designermonkey]

I'm all up for simplification, had some troubles understanding how it all works myself so far, to the point of leaving loads ou for a later date.

[jensscherbl]

Had some troubles understanding how it all works myself so far

Third option would be, make how the filters work (password optional, re-login) the default behavior behind the scenes when updating an entry. This would make the extension easier to understand for developers and we wouldn't lose existing functionality.

Let's see what @brendo has to say about this.