Currently the weblcms is using 2 right-systems
1) the global right system to set righs on tools and categories etc
2) a second right-system to set rights on publications
this prevents us from doing certain things we want to do there. (see
redmine for some of the issues)
it is also not a good idea to mix 2 different rights-systems in one
application I think.
I think we should use the chamilo rights system for everything in the
weblcms.
This should be discussed asap, before everybody starts to try to work
around this problem, complicating things even further.
to me it seems the best solution that you have one location tree
- course
- tool
- category
- publication
and allow the inheritance of the rights. It would also be best if we
could enforce that you can only narrow the rights when you go down the
tree: If someone does not have view-rights on the course, tool or
category, it should not be possible to give him/here view-rights on the
publication.
we particularly need this to "mimic" some of the tools in 1.8.x like
group-documents, studentpublications, teacher publications, ... with
categories in the documents and forum-tools that have certain pre-set
rights.
Kind regards,
Nathalie
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
