Best practice regarding non-User or Member content creation using both html and content channels
Hi everyone,
I'm sure this has been asked before but i could not find a relevant post with much detail using google or the site search. I hope you can point me in the right direction....
I just started using umbraco and I have been looking for information about best practices regarding Users and Members for content creation via both web and channels.
I am creating an application that will have members who can all create content. These members will sign themselves up to the application using standard asp.net controls. So they will become 'Members' and will be in the 'Subscribers' member-group for example. I forsee maybe 2000 of these Members for the site (so 1/8 of that in reality;)). It is not for a company or internal and will be on the wild wild web.
Now I want the content channels (livewriter, word et al) to be available to the Subscribers and i obviously want the content they create to be associated with the specific User/Member who created it. To use the content channels i must have Users. So with the various Member created/updated events i want to map a new member to an associated User so that there will always be a User for each Member with the same password for both.
Basically, Is this the correct way of implimenting this? Is it madness mapping Members to Users and maintaing the passwords between members and users. Is having a few thousand Users what umbraco was designed for? Will it cause any problems?
I was thinking of having some sort of single 'publisher' user. This would work fine if i limit the content creation to the html using ascx controls but if I use the channels in this manner i cannot know the member name and could not secure this across 2000 people - effectivly strangers - if they all used the same username and password. Right?
Hopefully I can help a little, although I know there are experts out there with much more experience in this than myself ;)
I would probably write some code that hooks into the Members Create Event and create the User that way - a custom control will allow you to keep passwords synchronised as well. You could also use the Create Event to create the corresponding pages on which to base your Users content Channel (ie, assign the new page as the root of the Users tree for editing etc).
Given that pages etc are cached, performance wise I don't see any problems. However, it would be worth downloading the Umbraco source code and inspecting it, and there are heaps of examples relating to the Event model and performing actions when a page/member is created/updated... The Blog4Umbraco project for example has this kind of thing...
Best practice regarding non-User or Member content creation using both html and content channels
Hi everyone,
I'm sure this has been asked before but i could not find a relevant post with much detail using google or the site search. I hope you can point me in the right direction....
I just started using umbraco and I have been looking for information about best practices regarding Users and Members for content creation via both web and channels.
I am creating an application that will have members who can all create content. These members will sign themselves up to the application using standard asp.net controls. So they will become 'Members' and will be in the 'Subscribers' member-group for example. I forsee maybe 2000 of these Members for the site (so 1/8 of that in reality;)). It is not for a company or internal and will be on the wild wild web.
Now I want the content channels (livewriter, word et al) to be available to the Subscribers and i obviously want the content they create to be associated with the specific User/Member who created it. To use the content channels i must have Users. So with the various Member created/updated events i want to map a new member to an associated User so that there will always be a User for each Member with the same password for both.
Basically, Is this the correct way of implimenting this? Is it madness mapping Members to Users and maintaing the passwords between members and users. Is having a few thousand Users what umbraco was designed for? Will it cause any problems?
I was thinking of having some sort of single 'publisher' user. This would work fine if i limit the content creation to the html using ascx controls but if I use the channels in this manner i cannot know the member name and could not secure this across 2000 people - effectivly strangers - if they all used the same username and password. Right?
Thanks for your thoughts on this!
dar
Hi Darragh,
Hopefully I can help a little, although I know there are experts out there with much more experience in this than myself ;)
I would probably write some code that hooks into the Members Create Event and create the User that way - a custom control will allow you to keep passwords synchronised as well. You could also use the Create Event to create the corresponding pages on which to base your Users content Channel (ie, assign the new page as the root of the Users tree for editing etc).
Given that pages etc are cached, performance wise I don't see any problems. However, it would be worth downloading the Umbraco source code and inspecting it, and there are heaps of examples relating to the Event model and performing actions when a page/member is created/updated... The Blog4Umbraco project for example has this kind of thing...
Hope this helps,
Rob.
is working on a reply...