I am running Magnolia 3.6.1. There are several websites in the one pair of webapps, with each site having a top-level node which is never displayed (this is ensured by the reverse proxy in front of Tomcat), and the site's pages, including index.html, hanging off that node. The editor for a single site can see the top-level node (in Website and DMS) for that site only, and all the nodes hanging off it, together with the appropriate templates.
One of the sites is only required at certain times, and when the editor doesn't want it, she deactivates the whole site by deactivating the top-level node. However, when she wants the site back, she is unable to activate it again, although she can see it, and I have to do it for her. If she deactivates all the lower-level nodes, she can reactivate them as expected. I guess I have done something wrong in the ACLs, which are as follows (I have merged the "editor" role and the "site" role for this list, and abbreviated shamelessly): Website: RO S&S /tmp/fckeditor Website: RO S&S /$ Website: RW S&S /site-1-top DMS: RO S&S /$ DMS: RW S&S /site-1-top URL: G&P /* Config: RO S&S /modules/adminInterface/config/menu/website Config: RO S&S /modules/adminInterface/config/menu/dms Config: D Sub /modules/adminInterface/config/menu Config: RO S&S /modules/templating/templates/site1 It's as if activation is seeing a "Sub nodes" instead of the "Selected and sub nodes" which de-activation sees at the same position. Can anyone suggest how I might be able to correct this? Paul ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
