From a conversation with Adam:
Adam: "...one error in a snippet and all of the sudden you have no manager access"
Mark: "What if this would be for frontend managers and the backend would still exist for emergencies and admin work."
Adam: "I think that would be great"
-
☆ A M B ☆
- 24,524 Posts
Can’t say that I care for the idea at all. What is so terrible about a completely separate management system? I can see not having to go to a separate page to login, but I like knowing that I"m in a management section when I’m doing management things. Maybe editing a page from the frontend has its advantages, but managing users or system administration doesn’t.
I think the idea has merit. A lot of CMSes do everything from the frontend and it has it’s nice points but it also has it’s downsides. I think this would be a great module or plugin but I think we’ll always have to have the backend around. Some people prefer the manager others don’t, it would be nice to have the option.
-
MODX Staff
- 10,725 Posts
I’d just like to point-out that separation of front-end and back-end does nothing but complicate and bloat the processing when it doesn’t have to. Users are users, and they have permissions to view specific content or take certain actions in the system, be they meant to be "front-end" or "back-end" content/actions, which to me, is just a very dumbed-down permissions system (you either are or aren’t a manager) that needs to be replaced.
Once I’m done with the web/manager-user merge, there will simply be users, groups, and permissions (and possibly roles, which would just be predefined sets of related permissions). What used to be manager-users will simply be users with membership in a Manager group, with a set of permissions based on the columns in the current role table (which will go away as well).
