No, this has nothing to do with Packager. The point is that the
templates, paragraphs, etc. must be announced to Magnolia and this will
be done by modules
Paul Worrall schrieb:
So, if I can get the packager working it will make this happen for them
automatically Otherwise I have to deploy a jar defining the module to
kick it off - then they can import changes when they want using the
importer.
On Fri, 2007-10-12 at 11:15 +0200, Ralf Hirning wrote:
Hi Paul,
yes, you have to define a module "mymodule" (module.xml, Module class
extending AbstractAdminModule)
Ralf
Paul Worrall schrieb:
Hi,
If you package up your templates etc. in to a jar file configured as a
module the bootstrap process recognises it and applies it. The
templates then become available (selectable from the website view for a
page).
If you import a configuration into say /modules/mymodule using
Tools->import is there anything extra you have to do to get the
templates/dials/paragraphs etc. recognised ?
Cheers
Paul
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
