I was thinking about writing a custom filter too. This would work fine to actually prevent a page from being served to the user, but I don't see how I could hide the page from the user as restricting access to the website repository in the ACL will do...
Ops... I misunderstood "user" as the site end user, you intended the editor (if I understand correctly now) that should not see a some pages of the webiste. Or I'm getting it wrong again and you mean that the end user has a few pages that are composed from such "reserved" sparse pages and the query should get only the pages the user would be able to access?
That's why I guess that some save handler magic which updates the ACL will maybe have to be applied. Then again: A the save handler for the page properties dialog is configurable. But what about when the editor renames the page in the tree? Maybe observation would be the way to go...
Depending on how critical is this feature for the editor, maybe it's possibile to keep the same idea and use a customized treehandler that excludes not only the pages from ACLs but also pages/paths that have some characteristics. Never tried this way, but you may let us know if it's feasible... :-) This way the user simply won't see the restricted pages, but if he deletes something that contains a restricted page, the page will be gone. (I haven't tried what happens with acls if I have permissions to delete the parent but I have no permissions on the child.)
Regards, Danilo. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
