I've ran into a little situation and would appreciate some direction...
The SilverStripe site I am working on has over 500 members in the members table. Spread across 3 groups (not including email lists). I have implemented a simple registration form that checks for existing email address's when a new member signs up. The registration form works good.
I noticed that when adding a member in the CMS, if the email address matches any in the member table that member is then replaced by the new submission, but there is no warning or confirmation of the replacement.
What would be the preferred way to add a prompt in the cms that alerts if the email address is all ready there. Something like..."That email address already exists, continue updating member" Yes,No
I haven't been working with SS for too long, but from what I understand members can belong to many groups. This makes sense because of the groups created with a newsletter. So I can understand the need to add a member (to a group) that already exists. I don't see enough separation between adding (creating new) members and assigning them to groups though. From my experiences when you add a member via the cms table (or cms popup) it will CREATE the member if they don't exist (no email match) and then write them into that particular group - and if the member exists already (email matches an existing email) it UPDATES the member and writes over everything in their member role.
I'll have to try this in some different SS setups and see if I can get a better idea of whats going on.