Email seems to be required for a Memebr in Umbraco
Hello,
I’m using Umbraco now as a wrapper around a program I’m
making. But I have a little problem. In the design of the product an e-mail
address is optional for a member. But in Umbraco it is required. Is there any
optional setting to make the e-mail in Umbraco optional for a member?
Don't know if it's possible to make it optional. But how do you handle the member creation in Umbraco? If you create members using the API I think it should be possible to not fill out this detail.
First let me explain why the email
address needs to be optional. We have a Group Decision Support System as a product
(see www.spilter.nl ). At this moment I’m developing the new version of this
product. Sometimes we get requests from our customers to make some additional
pages around our system. We can do that in VS2010 but the additional pages are basically
functionality that you can find in Umbraco. The new Spilter version supports multi-channel
presentation. And the first channel is a HTML variant. So we decided to build
the first presentation channel as plugins for Umbraco.
I see no problems with that and I like
to use the member functionality in Umbraco as leading for this (presentation) channel as far as access rights are concerned. So the backend server accepts a
secret key added with the recordID of the Umbraco member as a valid (trusted)
session.
Now within Spilter a Spilter-user is a
username and a password. Properties like an email address are optional. And the
channel (in this case Umbraco) needs to implement the functionality of Spilter
and not the other way around.
I did notice that you can create a
member (at that moment the email address is required), save the record, then
edit the record and delete the email address and save it again. That’s legal. I
also found the code that shows how you can add a member with your own code and
then the email is not required.
But what I don’t know is: Is email
address in any way used by the Umbraco code in a way that this explains why it
is required. In other words. If I add members without an email address will
that result in an error in Umbraco at another point in the code.
Ok, so it seems you now have a notion about how you can create members without the e-mail address.
The missing e-mail address will not cause Umbraco to crash. But if you ever need to create some content, which you need to restrict using public access you will probably not be able to provide your users access out of the box since this would require a loginname and an e-mail address.
How are you? Great to see your are using Umbraco. I'm sure the emailvalidation is only an UI based validation. There is no need to have an emailaddress other than using it for a password retrieve functionality. So you can use your workaround.
@Jan Skovgaard Do you say:
if you want to use member access to parts of your website it requires an email
address for the user to logon to that part of the website? I did try out a member’s
only part and I made a login page with the Microsoft login control and that
control only asked a username and a password. So how does the email fit into
that? Or do you mean something else?
@Richard
Hi!! Long time no see. Yes Umbraco add great functionality to our product. It’s
a lot of work to rebuild the Spilter code to fit into this model. But when it’s
completed the combination will be a great proposition for our current and
future customers. And it makes it possible to ask other programmers to help
with customer specific parts of our projects.
If you use the default Microsoft Membership Provider, the email address is indeed not required. It is actually a setting you can put in the definition of your provider in the web.config file. Like you say, the Login control from Microsoft only requires login and password.
The "email required" setting would typically be used if you would use the "Create user" control from Microsoft as well. There it would check if an email address is required or not and display error messages if needed. Also, if you create your user programmatically using the Membership classes from Microsoft, you would also have a check on the email address being required or not. But here you would most probably use the Umbraco classes sinc you need to pass the Umbraco MemberType when creating the member.
So, from what I read above, my guess is that, if you don't need to be able to actually contact the users via email, you can work further without having the email address being required.
I was thinking if you at some point need to actually make use of the members on a website where there should be som "I forgot my password" functionality...then it's not possible to benefit from the "send me an e-mail" stuff etc.
Email seems to be required for a Memebr in Umbraco
Hello,
I’m using Umbraco now as a wrapper around a program I’m making. But I have a little problem. In the design of the product an e-mail address is optional for a member. But in Umbraco it is required. Is there any optional setting to make the e-mail in Umbraco optional for a member?
Met vriendelijke groet,
Frank Gillebaard
Hi Frank
Don't know if it's possible to make it optional. But how do you handle the member creation in Umbraco? If you create members using the API I think it should be possible to not fill out this detail.
But why do you need it to be optional?
/Jan
Hi,
First let me explain why the email address needs to be optional. We have a Group Decision Support System as a product (see www.spilter.nl ). At this moment I’m developing the new version of this product. Sometimes we get requests from our customers to make some additional pages around our system. We can do that in VS2010 but the additional pages are basically functionality that you can find in Umbraco. The new Spilter version supports multi-channel presentation. And the first channel is a HTML variant. So we decided to build the first presentation channel as plugins for Umbraco.
I see no problems with that and I like to use the member functionality in Umbraco as leading for this (presentation) channel as far as access rights are concerned. So the backend server accepts a secret key added with the recordID of the Umbraco member as a valid (trusted) session.
Now within Spilter a Spilter-user is a username and a password. Properties like an email address are optional. And the channel (in this case Umbraco) needs to implement the functionality of Spilter and not the other way around.
I did notice that you can create a member (at that moment the email address is required), save the record, then edit the record and delete the email address and save it again. That’s legal. I also found the code that shows how you can add a member with your own code and then the email is not required.
But what I don’t know is: Is email address in any way used by the Umbraco code in a way that this explains why it is required. In other words. If I add members without an email address will that result in an error in Umbraco at another point in the code.
Frank.
Hi Frank
Ok, so it seems you now have a notion about how you can create members without the e-mail address.
The missing e-mail address will not cause Umbraco to crash. But if you ever need to create some content, which you need to restrict using public access you will probably not be able to provide your users access out of the box since this would require a loginname and an e-mail address.
But it should not make Umbraco fail in anyway.
Hope this answers your question.
/Jan
HI Frank,
How are you? Great to see your are using Umbraco. I'm sure the emailvalidation is only an UI based validation. There is no need to have an emailaddress other than using it for a password retrieve functionality. So you can use your workaround.
Cheers,
Richard
@Jan Skovgaard Do you say: if you want to use member access to parts of your website it requires an email address for the user to logon to that part of the website? I did try out a member’s only part and I made a login page with the Microsoft login control and that control only asked a username and a password. So how does the email fit into that? Or do you mean something else?
@Richard Hi!! Long time no see. Yes Umbraco add great functionality to our product. It’s a lot of work to rebuild the Spilter code to fit into this model. But when it’s completed the combination will be a great proposition for our current and future customers. And it makes it possible to ask other programmers to help with customer specific parts of our projects.
So your still work for yourself? J
Gr Frank
Hi Frank,
If you use the default Microsoft Membership Provider, the email address is indeed not required. It is actually a setting you can put in the definition of your provider in the web.config file. Like you say, the Login control from Microsoft only requires login and password.
The "email required" setting would typically be used if you would use the "Create user" control from Microsoft as well. There it would check if an email address is required or not and display error messages if needed. Also, if you create your user programmatically using the Membership classes from Microsoft, you would also have a check on the email address being required or not. But here you would most probably use the Umbraco classes sinc you need to pass the Umbraco MemberType when creating the member.
So, from what I read above, my guess is that, if you don't need to be able to actually contact the users via email, you can work further without having the email address being required.
Cheers,
Michael.
@Frank and off topic,
Yep still working for myself, 100% umbraco development :)
Hi Frank
Basically what Michael said.
I was thinking if you at some point need to actually make use of the members on a website where there should be som "I forgot my password" functionality...then it's not possible to benefit from the "send me an e-mail" stuff etc.
That's all :-)
/Jan
is working on a reply...