Hi Bram,
Op 1-jun-2007, om 15:53 heeft Bram Enning het volgende geschreven:
Basically our problems boil down to this:
Some users may create (and edit, delete etc) certain node-types
while other users may not.
For example:
Group A can create persons and places and may edit and delete nodes
they created;
Group B may not create persons and places, but only streets. The
can however view persons and places created by Group A;
How do you go about and implement this in MMBase?
This is what we did:
For every nodetype a context with group is created, so there is a
persons, places and streets context;
Then comes the, in my view, strange action: With the my-editors we
set in typedef the respective owner at each nodetype. So nodetype
Places gets as his owner a context Places, etc.
Then we create a context and group A and B;
Group A gets create, edit write and delete in the context Persons
and Places Group B for Streets, and view rights for context A;
Is there another way of controlling which nodetypes a group can
create?
I think not. You grant a context to a certain group and when no other
group can access that context the original group is the only group
that can edit (or create) them.
I believe that when you use cloud context security it the only
(other) possible way to disable the creation and editing of certain
nodetypes by a certain group, is when you shield them from that
group. So I think you need to create 'special' editors that display
only those nodetypes that a certain group may access.
---André
thanks,
Bram!
_______________________________________________
Users mailing list
Users@lists.mmbase.org
http://lists.mmbase.org/mailman/listinfo/users
--
André van Toly
MMBase development & Userfriendly webdesign
W: http://www.toly.nl
M: +31(0)627233562
------------------------------------------------------------------
~~<<>>~~
_______________________________________________
Users mailing list
Users@lists.mmbase.org
http://lists.mmbase.org/mailman/listinfo/users
