Grégory Joseph wroet:
On Nov 19, 2009, at 5:11 PM, Nils Breunese wrote:
I cleaned out my repository and restarted Magnolia. The
TemplatesInstallTask succeeds (I see them in the repository), but
the UpdateAllSiteDefinitions task fails with the following error
message:
----
ERROR info.magnolia.module.InstallContextImpl : > Could
not install or update vpro-sitestat module. Task 'Prototype template
path update' failed. (PathNotFoundException: config)
info.magnolia.module.delta.TaskExecutionException: Could not execute
task: config
at
info
.magnolia
.module
.delta.AbstractRepositoryTask.execute(AbstractRepositoryTask.java:60)
(...)
----
I don't really understand this PathNotFoundException and why it's
referring to 'config'. Any ideas?
Hmm, by looking at the source of UpdateAllSiteDefinitions, it's
failing at either line 76 or 82, ie:
Content stkSiteDefinition = modulesNode.getContent("standard-
templating-kit").getContent("config").getContent("site");
or
Content sitesNode = modulesNode.getContent("extended-
templating-kit").getContent("config").getContent("sites");
This would mean that either of /modules/standard-templating-kit/config
or /modules/extended-templating-kit/config is not present on your
instance ... ?
If I started Magnolia with a clean repository, I would get this error
and the site definitions would not be updated. If I then restarted
Magnolia the site definitions did get updated.
I guessed this was because of module dependencies. I changed my module
to depend on the extended-templating-kit instead of the
standard-templating-kit and then the problem went away. We are using EE,
so it's no problem, but there is nothing in my module that's specific to
EE, so I thought I might as well have just a dependency on the
standard-templating-kit. But if you are using ETK the module apparently
also needs to depende on ETK or dependencies are not handled in the
desired order.
Or is there another, maybe even better, way of accomplishing this
include?
Better, I don't know, but certainly a different approach: have you
considered using SiteMesh ?
I know SiteMesh from my recent experiments with Grails, since
SiteMesh is integrated in Grails. Introducing SiteMesh into our
Magnolia stack just for this feature sounds like overkill, but yes,
I guess it could work. Do you have any experience with/examples of
using SiteMesh with Magnolia?
No, but I've had the itch for a while ;)
We also have a much simpler "instream-modification" module/filter
which could be used for that sort of thing too (it's in enterprise at
the moment, and unreleased)
Let us know when there's more info on SiteMesh or this
'instream-modification' module/filter. For now, my module is working.
Thanks for your help.
Nils Breunese.
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
