Access Restriction should be more flexible

Reported by Bas R. Leeflang on 2003-01-18
12
Affects Status Importance Assigned to Milestone
Silva
Wishlist
Unassigned

Bug Description

I have been testin the access restriction option. Thusfar it
seems to rigid for many purposes. I understood that that it
would be difficult to reduce access restrictions for objects
deeper in an URL tree. OK I can live with that...

Currently, it is also not possible to increase the access
restrictions when going deeper. This means that the
restrictions apply basically from the site root. This would
reduce the options to:

/root/(free)
/root/folder1/(Authenticated)
/root/folder2/(Viewer)

For many sites it would be a nice feature when you could
increase the restriction upon going further in the tree.

Furthermore it would be great when the restriction options
would be expanded with Editor and ChiefEditor levels.
Bas

Kit Blake (kitblake) wrote :

Adding JW to the nosy list.

Martijn Faassen (faassen) wrote :

Increasing restrictions is not possible for roles the
way Zope works. There is a product that monkeypatches
Zope to retract roles but supporting this would involve
rather large reengineering of Silva.

It is possible to increase access restriction by withdrawing
permissions, such as the view permission. This is used
by Silva so that pieces of a site can be restricted.
It is not easy to generalize this to other abilities,
however, such as authoring (you'd really want to
retract roles there, which as mentioned above is
very difficult).

Martijn Faassen (faassen) wrote :

Now possible at least for public content with Viewer+(+) roles, which work on
permission retraction basis.

Changed in silva:
milestone: none → 2.3.6
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers