Hi Tobias,
Dang, this just looks like a bug. Thanks for reporting ! I added it in
our bugtracker:
http://jira.magnolia-cms.com/browse/MAGNOLIA-2809With 4.0, the path properties have been renamed to templatePath (for
consistency w/ paragraphs). Non-standard properties are also moved to
this parameters node (so one can still use them in their templates,
but they're not part of the template definition bean per se).
Unfortunately, it looks like we got mixed up, and instead of keep the
'templatePath' properties (which had just been renamed from 'path') we
attempt to keep the 'path' ones (which, well, have just been renamed
to 'templatePath')
It's unfortunate we notice this just after releasing 4.0.2. Hopefully
we'll come up with a fix soon, and it'll definitely be included in
4.1.1 which is due to release in the coming weeks/month.
In the meantime, apologies for the mix-up. I hope you don't have too
many template definitions to fix ;)
Cheers,
-g
On Jul 3, 2009, at 1:00 PM, Tobias Reinhardt wrote:
>
> Hello
>
> I updated two projects from 3.6.x to 4.1. With both projects there was
> a newly created ContentNode under every Template Node
> (templating>templates) after the update and the templatePath DataNode
> was moved to this new folder.
> The result was a "Unable to render
> info.magnolia.module.templating.Template internal in page /intranet:
> templatePath not set."
> After recreating the datanode templatePath direct under
> templating>templates>templatename it worked again.
> Templates are of type jsp.
>
> What is the purpose of this parameters node?
>
> Regards
>
> Tobias
>
> ----------------------------------------------------------------
> For list details see
>
http://www.magnolia-cms.com/home/community/mailing-lists.html> To unsubscribe, E-mail to: <
user-list-unsubscribe@...>
> ----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.htmlTo unsubscribe, E-mail to: <
user-list-unsubscribe@...>
----------------------------------------------------------------