1 result found
206 votesgordonread supported this idea ·
An error occurred while saving the commentgordonread commented
I have a very similar problem to that explained by Ian MacDonald. In fact, it is, for all intents and purposes identical.
I am setting up a database for club membershup for an Ice Skating club in the UK. We have several levels of membership "Skating", "Non Skating" and "Family". The Family membership fits the group (bundle) membership type exactly.
We have, however, the difficulty that many parents set themselves up as a "Non Skating" member and also their child as a "Skating" member (Family membership is only really meant for those with two or more children). In the case of our club, many of the children simply do not have their own email address - several are under the age of 6 for example - and it is not possible for a parent to register their child with the same email address as they have.
Neither, as far as I can tell, is it possible for a Family bundle membership to use the same email address for all members as it appears that it is necessary for each member to register individually.
We have experimented with the "firstname.lastname@example.org" email address format (which should arrive at "email@example.com"), however there are too many email providers that do not support this format to make it a viable option.
This is extremely unfortunate, as we now find ourselves paying for something (WA) that does not fit our needs.
Is there any progress with regards to any potential fixes for this problem? I have searched the forums and it has come up as an issue many times since at least 2008.
My own suggestion would be:
(1) During registration, permit the user to enter a "username" field which defaults to the users email address if not specified and is to be used for login, or
(2) Allow the user to use anything in the e-Mail field (so that it does not have to be an email address) and modify the WA system so that a site administrator can specify the field in the DB that is used to send emails to (which would default to the e-Mail field). This would mean no change to the backend logon system (which would still have to validate the entered login name against the e-Mail field), and permit individual members to select whatever email address they require for emails to be sent to - these, can therefore be the same for different members. The only downside I can think of to this is that the name of the "e-Mail" field is not strictly an e-Mail address any more.
Isle of Wight Ice Dance And Figure Skating Club