[Neos] NeosDemo Localisation: remove en_US dependency
Aske Ertmann
aske at moc.net
Wed May 6 16:01:23 CEST 2015
Hi Armin
Did you remember to the node migration mentioned in
http://docs.typo3.org/neos/TYPO3NeosDocumentation/IntegratorsCookbook/TranslatingContent.html#migration-of-existing-content
and run a node:repair?
On Wed, May 6, 2015 at 1:56 PM, armin otto <arminotto at gmail.com> wrote:
> I want to modify the NEOS demo site to support language and country
> localisation.
> Meaning, that I want to e.g. have two english and two german versions of
> the same site, where only sites with the same language inherit from each
> other.
>
> To achive this I edited the Settings.yaml like this:
>
> TYPO3CR:
> contentDimensions:
> 'language':
> default: 'en_US'
> defaultPreset: 'en_US'
> presets:
> 'all': ~
> 'en_US':
> label: 'USA'
> values: ['en_US']
> uriSegment: 'en'
> 'en_UK':
> label: 'UK'
> values: ['en_UK', 'en_US']
> uriSegment: 'uk'
> 'de':
> label: 'Germany'
> values: ['de']
> uriSegment: 'de'
> 'at':
> label: 'Austria'
> values: ['at','de']
> uriSegment: 'at'
>
> After cleaning up the old nodes, this works fine with one exception: The
> footer.
> This is the error message I get:
>
> Exception while rendering
> page<TYPO3.Neos:Page>/
> body<TYPO3.TypoScript:Template>/
> footer/
> __meta/
> override/
> contentCollectionNode:
> No content collection of type TYPO3.Neos:ContentCollection could be found
> in the current node and no node path was provided. You might want to
> configure the nodePath property with a relative path to the content
> collection. (201504300607472797b8)
>
> ----------
>
> This error occurs on all languages where I remove the 'en_US' value.
> Is there a way to make make a language independent from the USA?
> _______________________________________________
> Neos mailing list
> Neos at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/neos
>
--
Venlig hilsen Aske
Webudvikler, team lead
MOC A/S
4692 3435 / 4333 2200
moc.net
More information about the Neos
mailing list