Description
ACL of older revisions is ignored. For example, if revision 1 was a private revision with #acl All:, and revision 2 is public #acl All:read, you can view both revisions using Get Info, or see diffs between revisions.
Example
http://nirs.dyndns.org/main/AclHistoryTest?action=info
Details
Release 1.3.3
Workaround
Discussion
It is not clear if this is a bug - It depends how page acl are treated. Either page acl set acl for all previous revisions of the page, or page acl set the acl only for a specific revision. Both ways make sense, the question is which is the one the typical user will expect, and which will be more safe. We want to prevent a situation when you reveal stuff that you did not want to reveal, but we also want to prevent a situation when you can't use the wiki because of too strict acl. -- NirSoffer 2005-02-11 20:53:53
I would like to re-open the discussion on this behavior. It was clear that the other behavior (setting the ACL based on the one that is written in the page) was natural since I use MoinMoin as a CMS. My work-flow is to collaborate to write a page, with lots of rude words and cryptic signs to mark things to do and so on. Once we set the #acl All:read to go live, it would highly desirable that they do not have access to the previous draft information. -- LaurentPerrinet 2010-04-29 10:47:46
Plan
- Priority:
Assigned to: ThomasWaldmann
- Status: for 1.3, this is intended behaviour. We just use the latest ACLs known.
If we have good reasons, we might change that to a strict revision's acl based behaviour (this would be easier for us).