Re: Re: multi site CMS - run down

yes, this is exactly what I would look for, I don't mind having or not 
having shared themes,
I just don't content editing users to mess with it.

Filip

Ahmed Mohombe wrote:

>> In our scenario, we don't want our customers to control the themes, 
>> they will be put in place by designers and html developers.
>
> IMHO this could be better controlled by user rights/roles:
>
>> The "users" of the CMS only control content, not style or look and 
>> feel, more like a pure Content Management System.
>> I'm fully for the proposed solution, but it will break our 
>> requirements. is there a middle ground?
>
>
>> in the structure below, site1 and site2 has been given permissions to 
>> control their own themes,
>> site3 is restricted to use themes that are predefined in "shared"
>> site1,site2
>
> IMHO one should differentiate what "control" means:
> e.g. is one thing to be able to choose a theme or the other from the 
> "Menu Manager",
> for a site, and it's another right to be allowed to modify it/edit it.
> (Of course, by modifying in most cases will mean only small css or 
> image changes, but that's offtopic.)
>
> A private theme would only mean that it's not shared, so others can't 
> choose it for
> their site pages(so not seeing it in the MenuManager). About editing 
> it or not, IMHO that should be
> another right.
>
> Of course, to edit of shared themes can be done only by Admin.
>
> So there could be the following roles (and of course, more users with 
> different roles for a site):
> 1. basic_user -> just edit content,
>    A. can't edit themes : won't be able to see(/edit) them in File 
> Manager
>    B. can't choose themes : won't be able to use the comboboxes for 
> the themes in the MenuManager (and the FileManager -> however it is 
> confusing from the FM to change themes)
>    C. Will (can) have private themese, but someone else will choose 
> for him (e.g. developers, html writers, etc). This is useful if for a 
> user someone makes a special theme but doesn't want to be
> choosable by others.
>
> Filip, I suppose this is the scenario you would like to use most.
>
> 2. user -> can edit content, and choose themese
>    A. Can't edit themes: wont be able to see(/edit) them in the File 
> Manager
>    B. can choose themes: it will be able from the Menu Manager to 
> choose for it's pages the templates avaiable in his private themes, or 
> in the shared themes directory.
>    C. I suppose this is mostly how it's now with the "user" role.
>
> 3.  editor -> can edit content, can edit it's own private themes
>    A. can edit themes: it's private themese (so will have edit rights 
> in the File Manager)
>    B. can choose themes: it will be able from the Menu Manager to 
> choose for it's pages the themes available in his private or in the 
> shared themes directory
>    C. I suppose it will be also mostly like the actual editor.
> 4. admin -> can do everything.
>
> Of course, the names can be changed, but I just wanted to suggest the 
> different usage scenarios.
> I suppose with the exception of the "basic_user" everything is 
> possible exactly so (less or more :) ) in the actual single site version.
>
> What do you think?
>
> Ahmed.
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> MeshCMS-Discussion mailing list
> MeshCMS-Discussion <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/meshcms-discussion
>
>

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click