Hi Ralf, Thanks for the pointer! I've read through the page, and it sounds straightforward. However, I've bumped into an issue when trying to do something similar for Website content.
1. I set up a "Physical Therapy" structure in the website section using the superuser account. 2. I created a "physical-therapy-editor" role and set the ACL to read/write "/" for Website. (This isn't what I ultimately want, of course, but illustrates the problem I'm having nicely.) 3. I created a PT account, assigned the "physical-therapy-editor" role to it and logged in. I get no content: just the magnolia logo, a panel on the left side of the window with nothing in it, "User: pt | logout", and a big blank space where the content panel usually is. So, obviously I've missed something in setting up this Role or the account, but I don't know what it could be. Any idea what I might be missing? I spent a while trying to sort this out yesterday to no avail. :( Sean On 7/7/06 11:25 AM, "Ralf Hirning" <[email protected]> wrote: > Hi Sean, > > there is an other wiki page which shows how to restrict editors' access to > templates > > http://www.magnolia.info/wiki/Wiki.jsp?page=RestrictTemplateSelection > > This method works for websites as well > > Ralf > > -----Ursprüngliche Nachricht----- > Von: [email protected] [mailto:[EMAIL PROTECTED] > Gesendet: Freitag, 7. Juli 2006 17:48 > An: [email protected] > Betreff: [magnolia-user] Multiple Sites? > > Howdy folks, > > I'm looking at Magnolia as a possible replacement/supplement to our Vignette > CMS. Magnolia seems very nicely done and approachable, and I like the > straightforward approach to editing, templating, administration, etc. > Support for JSR-170 and JSR-168 (in the higher-end version) certainly > sweetens the deal as well. > > The one thing I haven't been able to sort out yet is whether it's possible > to support multiple sites with Magnolia. We have about 250 websites we're > eventually planning to move into a managed architecture. Each of those sites > has different administrators and users. Unfortunately, running 250 discrete > instances of Magnolia doesn't seem pratical. > > I found this page on the wiki which seems to provide some direction: > > http://www.magnolia.info/wiki/Wiki.jsp?page=RunningSeveralSitesWithOneMagnol > iaInstance > > This seems to give a good idea of how to serve several discrete sites from > one Magnolia installation, but doesn't touch at all on Security. I've tried > setting up accounts that use the Roles' Access Control List to only show > certain parts of the content tree, but haven't had much luck with that. > > So, is anybody using Magnolia to serve a bunch of sites, and if so, what > sort of approach do you take? > > Thanks in advance for any information, > > Sean McMains > > > ---------------------------------------------------------------- > for list details see > http://www.magnolia.info/en/magnolia/developer.html > ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
