> I create a JSP template and put it in the relevant directory on the > author instance. > - Do I then bounce the author instance before I can test the template ? > Do I need to delete the magnolia cache directory ?
If I remember correctly, you shouldn't need to bounce the instance to introduce a new template. You will, however, have to add a template definition to point to the JSP at the appropriate place in your AdminCentral config. > Lets say I have now tested the template and want to publish it. > - What is the process of getting it to the public instance ? Do I > physically have to copy the JSP file into the relevant webapp directory > for the public instance or does activating it in the GUI propagate it to > the configured subscribers (and take care of all that for me) ? Yep, you'll need to copy the template's JSP over. > - Also what do I need to do to the public instance to get it to register > the update ? Once the JSP is copied to public, just activate the template's config definition like you would other content. The Enterprise Edition also has a packaging tool that's designed to wrap up the JSP and the config into one nice, versionable package. I haven't fooled with it much yet, though. Sean ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
