Hello all, I've just dived in into Magnolia 4.5.x and am very excited about it. From the view point of the technical architecture, the publish/subscriber pattern reminds me of the approach that CoreMedia is using - brilliant!
My test setup that I derived from "magnolia-tomcat-bundle-4.5.7-tomcat-bundle.zip" looks as follows: 1) authoring instance on localhost:8080, single Tomcat 2) public system on localhost:8180, single Tomcat 3) public system on localhost:8280, single Tomcat In instance (1), the Tomcat's only webapp is "magnoliaAuthor". On the other Tomcats, it's only "magnoliaPublic". That way, all instances are strictly separated. My first question is: After I've downloaded and setup the example Magnolia authoring instance, all nodes had the red icon meaning the are not published. But the public instance already had all the content, templates etc. it needs. How can this be explained? Second question: On the public instances, I can open an authoring system although this webapp is not part of this Tomcat instance: http://localhost:8180/magnoliaPublic/.magnolia/pages/adminCentral.html shows the authoring system. How can this be and does it make sense? Last question: In the authoring system I managed to publish all nodes, so that they are all are green now (as I'd have expected from the beginning). I've now changed something in the FTL templates and published this change. However, the change cannot be seen in the public instances, although I've cleared the cache everywhere. How is this supposed to work? Thanks and best regards, Georg -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=58d53b0b-eab8-49a6-a636-fee0ce682e46 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
