I'm currently developing a site that has multiple user types and member groups. The members are of course used for locking down certain content on the website frontend, whilst different users are to edit different parts of the site.
My problem appears when a user is editing a page where member access is required. The logged in user cannot see the content without being logged in as a member (even though they have edit rights), and they cannot log in as a member while being logged in as a user. This means they cannot preview their edits before publishing, which kind of breaks the idea of a CMS in my opinion. Is there any workaround for this? I fail to understand why you would separate members and users into two different objects at all.
My only idea right now is to completely remove the whole member-part of umbraco and extend the users-part to store "members" there as well, with limited access rights. This seems like a whole lot of work for a workaround that shouldn't be necessary from the start.
Users vs Members and how to use them
Hi!
I'm currently developing a site that has multiple user types and member groups. The members are of course used for locking down certain content on the website frontend, whilst different users are to edit different parts of the site.
My problem appears when a user is editing a page where member access is required. The logged in user cannot see the content without being logged in as a member (even though they have edit rights), and they cannot log in as a member while being logged in as a user. This means they cannot preview their edits before publishing, which kind of breaks the idea of a CMS in my opinion. Is there any workaround for this? I fail to understand why you would separate members and users into two different objects at all.
My only idea right now is to completely remove the whole member-part of umbraco and extend the users-part to store "members" there as well, with limited access rights. This seems like a whole lot of work for a workaround that shouldn't be necessary from the start.
Shed some light on a newcomer?
Hi Oscar
What version of Umbraco are you using?
I think it makes perfect sense to have Users and Members since they serve different purposes.
In short Users are able to login to the Umbraco backoffice and edit content. And that's the sole purpose of users.
Members are intended for granting access to protected pages on the public facing website.
I don't think it would make any sense at all to merge the two into one.
However regarding your issue I think it sounds like an edge case bug, which should probably be reported at the issue tracker
Just my 2 cents.
/Jan
is working on a reply...