I'm implementing a site for a client that has a members area requiring a member to be logged in before the content is available. I've also got back office editors (Umbraco users) that can edit content on the public site as well as the members area. My content editors are also considered members in that they need to be logged in before they can view the member only content. But the public access settings on content don't pay attention to Users.
From what I can tell I need to give my content editors 2 username/passwords to be able to a) access the members only area and b). edit content. Has anyone else run into this? My first thought was just create a member group "Editors" and allow those members to edit content, but it doesn't appear that I can give a member access to the WYSIWYG editor provided by umbraco.
Thank you in advance for any advice and suggestions.
users and members are two completely different concepts, so it's best to not mix up the two. On the frontend, you need members to be logged on to view protected content, users can only access the admin backend (and be restricted to specific content).
Yes, you need a member and user for editors that need to edit content (backend) and be able to view member content (frontend)
You could automate a few things (create a member login for each new user or editor that gets created) and sync usernames/passwords to those editors only have to remember a single combination...
Another way - If you want to implement a solution that allows your visitors to add/update content in the website front ( in the designed website ) then you use the membes for that. To authenticate your visitors (as members) you can use:
- the visual studio login controls (if you're that kind of guy) - or the member control package in the repository (if you're the download and customize kind of guy)
You path forward could contain developing usercontrols for input and storing your data in the Umbraco or a db model. And you'll use xslt for retrieving and displaying the stored information. You might even develop som xslt extension to ease retrieving your data from Umbraco or from db.
You could go in another direction and do all input with html forms, jquery, umbraco base (for ajax posting).
In addition there's a lot of packages that helps you with specific tasks.
User vs Member Best Practice
I'm implementing a site for a client that has a members area requiring a member to be logged in before the content is available. I've also got back office editors (Umbraco users) that can edit content on the public site as well as the members area. My content editors are also considered members in that they need to be logged in before they can view the member only content. But the public access settings on content don't pay attention to Users.
From what I can tell I need to give my content editors 2 username/passwords to be able to a) access the members only area and b). edit content. Has anyone else run into this? My first thought was just create a member group "Editors" and allow those members to edit content, but it doesn't appear that I can give a member access to the WYSIWYG editor provided by umbraco.
Thank you in advance for any advice and suggestions.
Bo,
users and members are two completely different concepts, so it's best to not mix up the two. On the frontend, you need members to be logged on to view protected content, users can only access the admin backend (and be restricted to specific content).
Yes, you need a member and user for editors that need to edit content (backend) and be able to view member content (frontend)
You could automate a few things (create a member login for each new user or editor that gets created) and sync usernames/passwords to those editors only have to remember a single combination...
Hope this helps.
Regards,
/Dirk
Hi Bo,
Another way - If you want to implement a solution that allows your visitors to add/update content in the website front ( in the designed website ) then you use the membes for that. To authenticate your visitors (as members) you can use:
- the visual studio login controls (if you're that kind of guy)
- or the member control package in the repository (if you're the download and customize kind of guy)
You path forward could contain developing usercontrols for input and storing your data in the Umbraco or a db model. And you'll use xslt for retrieving and displaying the stored information. You might even develop som xslt extension to ease retrieving your data from Umbraco or from db.
You could go in another direction and do all input with html forms, jquery, umbraco base (for ajax posting).
In addition there's a lot of packages that helps you with specific tasks.
/Jesper
is working on a reply...