[Neos] Put Text node as direct child on page

Aske Ertmann aske at moc.net
Tue Jan 27 09:00:15 CET 2015

Hi Reinis

It’s a little tricky due to some technical reasons/limitations, but I’ve shared two ways of achieving it here https://gist.github.com/aertmann/f9c8a33e8720f7cb21be <https://gist.github.com/aertmann/f9c8a33e8720f7cb21be>

I’ve created a ticket to make it easier, but still needs to be implemented.. https://jira.typo3.org/browse/NEOS-228 <https://jira.typo3.org/browse/NEOS-228>

Hope it helps.


> On 26 Jan 2015, at 12:30, Reinis Zumbergs <reinis.zumbergs at gmail.com> wrote:
> Hello, all, my first post here!
> We all know how to put ContentCollection on the page:
> - add new childnode in NodeTypes.yaml
> - add ContentCollection sub-path to body parts in Root.ts2
> But I would like to put TYPO3.Neos.NodeTypes:Text directly on page. I tried various approaches including:
> NodeTypes.yaml
> 'TYPO3.Neos.NodeTypes:Page':
> childNodes:
>   headerLink1:
>     type: 'TYPO3.Neos.NodeTypes:Text'
> Root.ts2
> page.body {
> 	// Frontpage header links
> 	headerLink1 = TYPO3.Neos.NodeTypes:Text {
> 		node = ${q(site).children('headerLink1')}
> 	}
> }
> But no success. The editable area in BE is created and the Text node is present in page structure, but when it tries to save changes, an error occurs saying:
> Node type "TYPO3.Neos.NodeTypes:Page" does not have a property "text" according to the schema.
> Another approach to somewhat achieve what I need would be to be able to limit ContentCollection to have only one child - no possibility to add more content nodes to the collection.
> _______________________________________________
> Neos mailing list
> Neos at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/neos

More information about the Neos mailing list