[Neos] FYI: How To Update your own site packages with BREAKING Node Types Change
Aske Ertmann
aske at moc.net
Sun May 26 18:09:20 CEST 2013
FYI: During this weekend I found some issues and improved the changes further, so until these changes are merged there are still some issues. E.g. the menu content element.
List:
https://review.typo3.org/#/q/status:open+topic:typoscript-cleanup,n,z
These will probably be merged monday/tuesday.
Regards,
Aske
On May 25, 2013, at 10:23 PM, Pankaj Lele <pankaj at lelesys.com> wrote:
> Hi Sebastian,
>
> This helped a lot to update one of our experimental Neos projects and we decided to keep sync with Neos master hence forth on daily basis which will help on giving feedback on changes if any.
>
> Thanks,
> Pankaj
>
>> Hey everybody,
>> Karsten and I just merged the whole Node Type refactoring [1] , after
>> testing it in detail again. You see it's a lot of changes, that's why we
>> quickly wanted to get it in.
>> I also updated the Neos Demo package: https://review.typo3.org/#/c/21021/
>> Here are the instructions on how to update own packages:
>> * we assume you have a running installation.
>> * then, update the following packages:
>> o TYPO3.Neos
>> o TYPO3.Neos.NodeTypes
>> o TYPO3.TypoScript
>> o TYPO3.TYPO3CR
>> * Then run the following command to update NodeTypes.yaml of your own
>> site package:
>> o ./flow core:migrate
>> * Then, update the Nodes in the Database by running the following command:
>> o ./flow node:migrate live 20130516212400
>> * Then, if wanted, export the Site again to the package:
>> o ./flow site:export > ....
>> Hope that helps a bit,
>> Sebastian
>> [1] https://review.typo3.org/#/q/status:merged+topic:typoscript-cleanup,n,z
>
>
> --
> Pankaj Lele
> CTO - Lelesys, India
> http://www.lelesys.com
> Twitter: @pankajlele
>
> _______________________________________________
> Neos mailing list
> Neos at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/neos
More information about the Neos
mailing list