[Neos] Exception after composer update: An invalid node path...

[Simon Schaufelberger (Schaufi)]

Hi,
> As said, please read the release notes and watch out for commits marked
> wiht !!!. These are breaking, but have an explanation on how to upgrade
> in the commit message.

I did but i didnt find anything about template change (from footer). i 
did all code migrations but still it's not working.

how can i find out where 
"page<TYPO3.Neos:Page>/body<TYPO3.TypoScript:Template>/footer"
comes from? in the exception i dont see anyting about a template path 
that is rendered. that would help a lot!

Regards, Schaufi

Am 25.10.2013 20:11, schrieb Sebastian Kurfürst:
> Hey Simon,
>
>> i would expect from neos that at least the core itself is stable
>> without using any additional packages. i'm using the typoscript
>> template from TYPO3.NeosDemoTypo3Org. clean master. the template is
>> loaded from files, not from db cache or? i just did a composer update
>> again today and still no solution. do i need any manual changes on the
>> database side?
> As said, please read the release notes and watch out for commits marked
> wiht !!!. These are breaking, but have an explanation on how to upgrade
> in the commit message.
>
> The templates are in the file system, that's correct.
>
> Neos is still an alpha version, so we rather break things now than when
> 1.0 final is out; and we try to keep the pain to an minimum by providing
> migrations etc.
>
> Greets,
> Sebastian
>