I guess adding a redundant "each" to that sentence wouldn't be luxury, for the 
sake of clarity.
Cheers!

-g

On Jan 8, 2010, at 10:26 PM, Laird Nelson wrote:

> ...aaand one more Google hit later I found the answer.  From 
> http://documentation.magnolia-cms.com/modules/standard-templating-kit.html I 
> missed the apostrophe after the word "instances":
> 
> "The bundle is provided as a zip file; the archive contains a number of .jar 
> files, which you'll need to copy to your Magnolia instances' WEB-INF/lib 
> folder"
> 
> Thanks folks; sorry to bother.
> 
> L
> 
> On Fri, Jan 8, 2010 at 4:23 PM, Laird Nelson <[email protected]> wrote:
> I am a newbie to Magnolia.
> 
> I successfully installed and deployed an author instance and a public 
> instance of version 4.2.3 on Glassfish 2.1.
> 
> The Website tab tells me that my next step is to install the standard 
> templating kit.  But of course it doesn't say how to do that.
> 
> From banging around on Google and injuring myself bashing around in the dark 
> on the chaotic community wiki site and the official documentation site, I see 
> that to install a module, which I gather the standard templating kit is, you 
> need to dump the module in the WEB-INF/lib folder.  As a Java developer this 
> makes sense to me.  However: do I install it into both instances, or is this 
> a case where I install these .jar files into my author instance and then 
> somehow magically activate them (even though I think they've got to be part 
> of the running webapp, not part of the JCR)?
> 
> I hope to write up my great laborious deployment journey so that others may 
> find installing this product easier.
> 
> Thanks,
> Laird
> 


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to