Update to 4.1 moves templatePath DataNode to a new parameters node

[tobltobs]

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@...>
----------------------------------------------------------------

[gregoryjoseph]

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-2809

With 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.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

[tobltobs]

> In the meantime, apologies for the mix-up. I hope you don't have too many
> template definitions to fix ;)

No problem, that Resource is deprecated now bothers me more.

I have two other problems updating 3.6.x Installations to 4.1:
1.)  An "can't resolve class for node
/modules/adminInterface/commands/default/sendMail" error in the
logfile. Changing the class from info.magnolia.module.mail.MailCommand
 moved to info.magnolia.module.mail.commands.MailCommand makes the
error go away...

2.) WARN: Dialog definitions should be of type contentNode but
[/modules/templating/dialogs/paragraphs/xyz is of type content. This
one comes even for the magnolia own dialogs like dms and user edit
dialogs. And it comes if you install a clean 4.1, not only with
updated installations.

Regards

Tobias

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

[Françoise Gérard]

Hi Grégory,

I installed Magnolia 4.0 a few weeks ago and there was the "templatePath" in the template definition of the STK.
Now with Magnolia 4.1 I do not see that definition anymore (for example in the stkHome definition).
I guess this is because of the bug you describe, right?

Okay but then, how does Magnolia find the way to the template path, as it is not more defined? Is it hardcoded somewhere?

I am also searching for the "comment" definition in an Article (to integrate it somewhere else). I guess it is only a paragraph to add, but I can not find the Arcticle template definion having that comment paragraph. Can you tell?

Regards,

Françoise




--------------------------------------------------------

Françoise Gérard (Francoise.Gerard@... )
Project Manager

 
BSB Luxembourg (www.bsb.com)
7A, rue des MérovingiensZ.A.I. Bourmicht - L-8070 Bertrange
T:[phone] - F:[phone]
--------------------------------------------------------



BUSINESS SOLUTIONS BUILDERS DISCLAIMER
This e-mail message and any attachments are intended exclusively for the addressee(s) and may contain information which is confidential and/or protected by intellectual property rights. If you receive this e-mail by mistake, please notify immediately the sender, or Business Solutions Builders (by e-mail at disclaimer@...), and delete the message and any attachments without printing, copying or opening it. Any disclosure, reproduction, distribution or use of this message or any attachments, by persons other than the designed addressee(s), is strictly prohibited. E-mail transmission and Internet use cannot be guaranteed to be secure. Business Solutions Builders and its subsidiaries cannot be held responsible for any loss, delay or damage arising from their use.
--------------------------------------------------------

-----Original Message-----


From: user-list-owner@... [mailto:user-list-owner@...] On Behalf Of Grégory Joseph
Sent: vendredi 3 juillet 2009 18:55
To: Magnolia User-List
Subject: Re: [magnolia-user] Update to 4.1 moves templatePath DataNode to a new parameters node


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-2809

With 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.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

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

[gregoryjoseph]

Hi,

On Jul 3, 2009, at 11:11 PM, Tobias Reinhardt wrote:
>> In the meantime, apologies for the mix-up. I hope you don't have  
>> too many
>> template definitions to fix ;)
>
> No problem, that Resource is deprecated now bothers me more.

Any specific problem or difficulty with that ?
http://documentation.magnolia-cms.com/releases/4-0-1/api-cleanup.html#Aggregationandtemplating

> I have two other problems updating 3.6.x Installations to 4.1:
> 1.)  An "can't resolve class for node
> /modules/adminInterface/commands/default/sendMail" error in the
> logfile. Changing the class from info.magnolia.module.mail.MailCommand
> moved to info.magnolia.module.mail.commands.MailCommand makes the
> error go away...

info.magnolia.module.mail.commands.MailCommand is indeed the correct  
class; can't see where the wrong class name comes from.

>
> 2.) WARN: Dialog definitions should be of type contentNode but
> [/modules/templating/dialogs/paragraphs/xyz is of type content. This
> one comes even for the magnolia own dialogs like dms and user edit
> dialogs. And it comes if you install a clean 4.1, not only with
> updated installations.

Hmm, I thought we'd have fixed that for 4.1; it should really just be  
a debug message, and can be ignored. I'll report this on our Jira if  
it's not already there.

Cheers,

-g


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