[opencms-dev] Fwd: Restrict a user group to a content editor

[Christoph Fröhlich]

Just for the records:

After some thoughts we decided not to go with the script based solution. The main counter argument is that when adding new users the editor has to be configured explicitly for the new user.  
Since adding new users is done by varying staff at the client, it is too difficult to control that this happens reliably.

When we found the following interface

org.opencms.xml.content.CmsDefaultXmlContentHandler#isAcaciaEditorDisabled()

we decided to prevent the usage of Acacia-Editor for distinct content types as a whole.

This is not a generic solution for my initial question but it solves our particular problem.

Regards
C

Anfang der weitergeleiteten Nachricht:

> Von: Christoph Fröhlich <cfauto at folge2.de>
> Betreff: Aw: [opencms-dev] Restrict a user group to a content editor
> Datum: 27. Juni 2014 10:57:27 MESZ
> An: The OpenCms mailing list <opencms-dev at opencms.org>
> Antwort an: The OpenCms mailing list <opencms-dev at opencms.org>
> 
> Hi Tobias,
> 
> thanks for your quick reply and the recommendation how to solve it.
> Sounds good. I will try this.
> 
> Regards
> c
> 
> Am 27.06.2014 um 10:00 schrieb Tobias Karrer <kartobi at gmail.com>:
> 
>> Hi Christoph,
>> 
>> users can choose their editor in "Preferences > Tab Editors > Preferred editors > XML Content > Default page editor"
>> 
>> The setting is stored in users additional info map:
>> USERPREFERENCES_editors-preferrededitorsxmlcontent=/system/workplace/editors/xmlcontent/editor.jsp
>> 
>> So I guess you may change/set it with a script quite easily.
>> 
>> Best,
>> Tobias
>> 
>> Am 27.06.2014 06:01, schrieb Christoph Fröhlich:
>> 
>>> Dear all,
>>> 
>>> we are currently migrating a 8.0.4 installation to 9.0.1
>>> 
>>> In this installation there is one user group with 300+ users which edit content infrequently (they add, edit and delete xml-based content types).
>>> 
>>> For some of these people it is really difficult to work with the Cms and we don't want to confuse them even more. Therefor it would be best if they could stick to the old standard editor and don't have to use the new acacia editor.
>>> 
>>> So here's my question:
>>> Can we specify that the users of a distinct group are bound to a distinct editor? While leaving the freedom of choice to all other users?
>>> 
>>> Thanks and regards
>>> Christoph
>>> 
>>> _______________________________________________
>>> This mail is sent to you from the opencms-dev mailing list
>>> To change your list options, or to unsubscribe from the list, please visit
>>> http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev
>>> 
>>> 
>>> 
>> 
>> _______________________________________________
>> This mail is sent to you from the opencms-dev mailing list
>> To change your list options, or to unsubscribe from the list, please visit
>> http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev
>> 
>> 
>> 
> 
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20140703/60c2a3ab/attachment.htm>