I should clarify, Magnolia should be stopped when you copy the JAR into the lib directories. When you start it up again, it will detect the new JAR.
The way Magnolia works is with "author" instances and "public" instances. The author instance is where you make changes and keep track of versions and preview content changes. When you "activate" a change in the author instance it connects to the public instance and makes the activated changes there. It's very different from other content management systems out there (like Wordpress, Drupal, or Joomla), but Magnolia is far superior. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=bfcfeba5-1092-44bc-a183-3ef4b930a1c1 ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
