[opencms-dev] Give write access to a group of people but forbid mutual editing

[Yves Glodt]

Ok that sounds perfect.

But, how can I be sure a v8news item from person A ends automatically up in
/.content/news/department-of-a/, and from person B in
/.content/news/department-of-b/
?

By default all ends up in /.content/news/



On 15 June 2013 07:18, Antoine PINEAU <a.pineau at eurelis.com> wrote:

>  If you use Solr search to retrieve your news, you will be able to get
> ALL the news in ALL subfolders from ALL people J****
>
> Solr will also allow you to manage efficiently facets relying on the
> categories.****
>
> ** **
>
> *De :* opencms-dev-bounces at opencms.org [mailto:
> opencms-dev-bounces at opencms.org] *De la part de* Yves Glodt
> *Envoyé :* vendredi 14 juin 2013 09:10
>
> *À :* The OpenCms mailing list
> *Objet :* Re: [opencms-dev] Give write access to a group of people but
> forbid mutual editing****
>
> ** **
>
> And... will the collector still find ALL the news from ALL people even
> they are in subfolders of /.content/news/ ?****
>
> ** **
>
> Because we want to list them all in one place, and based on categories on
> a different place.****
>
> ** **
>
> On 14 June 2013 09:07, Yves Glodt <yg at mind.lu> wrote:****
>
> The /.content/news/from-a/ solution looks interesting.****
>
> ** **
>
> How can I be sure a v8news item from person A ends up in that folder (and
> person B in /.content/news/from-b/) ?****
>
> ** **
>
> By default all ends up in /.content/news/****
>
> ** **
>
> Best regards,****
>
> Yves****
>
> ** **
>
> On 13 June 2013 17:51, Antoine PINEAU <a.pineau at eurelis.com> wrote:****
>
>   Hi,****
>
>  ****
>
> I suggest you to isolate contents from user A to contents from user B in
> separate folders and set permissions on each folder.****
>
> /.content/news nothing can be added by users****
>
> /.content/news/from-a/ can only be edited by user A****
>
> /.content/news/from-b/ can only be edited by user B****
>
> …****
>
>  ****
>
> Antoine****
>
>  ****
>
> *De :* opencms-dev-bounces at opencms.org [mailto:
> opencms-dev-bounces at opencms.org] *De la part de* Siegfried Ehret
> *Envoyé :* jeudi 13 juin 2013 17:14****
>
>
> *À :* The OpenCms mailing list
> *Objet :* Re: [opencms-dev] Give write access to a group of people but
> forbid mutual editing****
>
>  ****
>
> You can set permissions by files but it’s going to be boring…****
>
>  ****
>
> *De :* opencms-dev-bounces at opencms.org [
> mailto:opencms-dev-bounces at opencms.org <opencms-dev-bounces at opencms.org>]
> *De la part de* Yves Glodt
> *Envoyé :* jeudi 13 juin 2013 15:37
> *À :* The OpenCms mailing list
> *Objet :* Re: [opencms-dev] Give write access to a group of people but
> forbid mutual editing****
>
>  ****
>
> Bump... and let me reformulate the question:****
>
>  ****
>
> Many people can add content to /.content/news/. This works well.****
>
>  ****
>
> But I do not want that user A can edit the items created by user B.****
>
>  ****
>
> How is that doable ?****
>
>  ****
>
>  ****
>
>  ****
>
> On 21 May 2013 08:39, Yves Glodt <yg at mind.lu> wrote:****
>
> Hi,****
>
>  ****
>
> I would like some users to be able to add files to /.content/news/.****
>
>  ****
>
> Is there a way to let them add stuff, but in the same time be sure on can
> not edit the others files ?****
>
>  ****
>
> Best regards,****
>
> Yves****
>
>  ****
>
> ** **
>
> _______________________________________________
> 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/20130617/c5b2b368/attachment.htm>