Great CMS but ....
Its easy for some to generally edit etc and works reasonably well.
Direct front end editing makes life easy for the non tech types, etc.
The backend is seriously limited, and the reason why, yet again, I need to shift a site away from C5 is user management and general permissions.
Why can't I simply add a user as a editor who can add content?
The only way is doing the dance with editting PHP files and hacks where other CMS I simply select the user group, edit access to various sections and assign users!
Permissions are seriously flawed and overly complex.
like I say C5 is great for single user operations etc, where you don't need to worry about users fiddling with settings etc. but ...
i've looked up the help to no avail, and the closest i found to any fom of permission and user management is on a page by page basis, or by editing and hacking source! All I want is to add administrators and then content editors without the need to edit permissions on every single page!
Please, please please, add a basic admin, publisher, editor, registered user, public with appropriate permissions! Why can't we simply add a user to a group and edit their permissions! (I know there probably is a secret method to do this but its definately not documented (well) and brings me to the second pet hate!
Fix the &*%&[email protected] backend so you can have the dashboard stay up on screen with real meaningful options. (Like user management / Permissions)
Not everybody knows the obscure commands and options for the search system.
It is so frustrating!
C5 a great CMS, but .....
The place to start reading is:
There are examples in the howtos.
Having said that, what you seek is such a common requirement that it may help to have a standard 'editors' group created with the default install, like there is an administrators group. The only disadvantage I can think of is that 'editors' means different things to different people, so once there was a standard editors group, there could be even more grouches that it allows too much and too little.
There may even be room for someone who is into editing permissions programmatically to create an addon that sets up a few common groups.
We use these permissions to manage complicated applications like training websites, digita asset management, secure extranets, and even this site. We do it without ever touching code....
It sounds like some more work on our documentation might be in order, because you're definitely doing it wrong on this one.
Sent from Mailbox for iPad
I didn't realize you only need to set the top level pages.
I still find it awkward and confusing compared to other systems.
I think the confusion lies in the wording and layout of the dashboard - such as Dashboard->Members->User Group which seems to just add a group name. Then you go to Dashboard->System & Settings->User Permissions->Edit Groups ? (I added editors to their as well, which now I don't think was needed?)
Then go back to Dashboard->Search User->Pick user->View User->Edit User->Add Group etc etc. Then go back to start, do not collect $200, and select Dashboard->Search User->Pick next user->View User->Edit User->Add Group etc and do this for every user. (I know you probably and type a mystic search phrase to get there but I don't know the shortcuts - yet!)
Maybe the user/groups area needs to be simplified for example by having the edits groups section have an option to add numerous users to the group all in one page!
Don't get me wrong I do like C5 and a number of the end-users love the simplicity of the editing etc once its set up, but as an administrator it drives me a little crazy when used to other systems.
And yes I do hate the "Dashboard" and backend layout, with a passion. With its constant vanishing act, why can't it for example "Edit User, click save and it goes back to the user selection screen", not play hide and seek!
Enough of the rant!
Keep up the good work, and thanks again for you help!
thanks for sharing your questions. With concrete5 there typically /is/ at least one or more ways to solve the problem you're looking at so if you feel like something is crazy and can't possibly be as hard as its turning out, its good to ask. ;)
I love Concrete 5 and have just built my first site with it and need to setup an admin for my client.
It probably comes down to the documentation being a bit unclear. A step by step guide would be great.
I have also had trouble with setting up a password protected 'members' area on the website. Perhaps documentation on this could also be clearer. I just wanted one username and one password for a group of people to access to see a page with club information. I'm getting there but it's been confusing.
To make a "members" area on your site we'd generally recommend making a separate user account for each person, then adding each user to a group. Then you can set up permissions to grant access to the entire group. Here's an article that describes how to grant access to a Dashboard page, though the same concepts could be applied to any page in your site:
Granting access to certain pages in the Dashboard would also be a good way to set up access for your client. That way, you could allow them to change certain settings but keep others locked away. If you want to simply grant your client access to almost everything that "admin" can do, simply add your client's user account to the Administrators group that is installed with concrete5.
If you want to grant access only to specific users, not groups, you'll need to enable Advanced Permissions:
Here's a handy permissions screencast that shows how to allow users to access files they've uploaded to the File Manager. This one uses Advanced Permissions a bit:
Hope that helps! Let me know if you run into any roadblocks and I'd be happy to help you find what you're looking for or suggest a good approach to a problem.
I encountered the "painful permissions setting"-thing when setting up users for composer publishing with all the allow/deny-clickery in dashboard pages.
I am not capable of doing this, but wouldn't it be nice to have a Add-On like a "group permissions template" for different user scenarios? I am visualizing some group-permissions-entity-based thing for the most common tasks like "Editor" (can write to certain pages and publish), Writer (can write but not publish) etc ...
I am not sure anybody would pay for this though...
The main difficulty with writing code to do anything with permissions is that the documentation has not caught up with the last couple of years of core updates.
There is a howto by 5fly that developers may find of assistance.