« Return to Thread: Update to 4.1 moves templatePath DataNode to a new parameters node

Re: Update to 4.1 moves templatePath DataNode to a new parameters node

by gregoryjoseph :: Rate this Message:

Reply to Author | View in Thread


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

 « Return to Thread: Update to 4.1 moves templatePath DataNode to a new parameters node