Thanks Ralf & James, It was just such a remarkably long and hard weekend and since I assumed no one paid any attention to the email I didn't have the energy to write a response to myself. I was able to get the sites up and running without the Apache install (I did see several references to the Apache deployment mentioned but not that particular one so I couldn't figure out how to set it up).
There were several things blocking me, the first was the redirect from the root folder that kept breaking my filter code. Also installing a custom filter wouldn't work, so I eventually just derived from the Magnolia filter and implemented my own filter on top that does the redirection based on the HTTP host header. I can post the code although its hardcoded to my site and relatively trivial. If there is interest I can try and write something. About the user permissions, the whole set of different roles for all the repositories was just something I had a very hard time understanding when reading the documentation. I eventually figured it out from the documentation but I don't really like that aspect of Magnolia. It seems roles such as "editor" are hardcoded in the system because when you view their ACL's they don't seem to be what an editor really needs. On my machine an editor only has a website permission to "/" where in fact there are quite a few different elements to set up in order to get the proper permissions. Thanks. -- Shai Almog vPrise http://www.vprise.com/ ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
