Will, Perhaps I just don't know the proper ACL settings for this. Suppose I have the following pages:
/page + /page/active + /page/addSubpage Those last two are using Blossom Templates for processing. I need editors to be able to POST data to those pages, which I thought meant I had to grant read-only access to /page and its subpages. This is what I have done and it is working great but what would be even better would be to have a way to prevent that entire tree of pages from showing up in Admin Central unless you are the superuser or something. Make sense? Is there a way to make this happen using ACLs? Tom On Feb 18, 2011, at 2:19 PM, Will Scheidegger wrote: > I guess I'm missing a point here. ACL does not work for you? > > -will > > On 18.02.2011, at 20:55, Thomas Duffey wrote: > >> I'm wondering if these is a way to hide pages in Admin Central, either on a >> page-by-page basis or based on some rule like not showing any pages that are >> read-only. We're using Blossom a lot these days and have pages tied to >> Spring controllers that we'd like to keep out of sight from our content >> editors. They do need read-only access to these pages to be able to use >> their functionality (A lot of them provide handlers for Ajax requests used >> on the author side) but I haven't found a way to keep them out of the tree. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
