Kickstarter How-To?

[mad (Martin Huber)]

Hey David,
your are right. Thanks: The Kickstarter-Package is now running. I took the resulting Sites.xml and reduced them for my own base with de_DE and functioning setting.

There are only the jingling words from @christianm in my mind.

@christianm

but I suggest doing that only in the inital setup. What the demo site does and what I recommend is using the Sites.xml

This is related to a slightly different initial situation. But at the end, it is probably comparable and would have to be very efficient.

Conclusion/Question

***So maybe there is an more easier way with sites.xml*** [(maybe with Neos-Tools or by hand) for a hole bunch of sites, sub-sites, language-dimensions and so on ...] ***for a base-filled site-tree and an base-skeleton.***

Does anyone know such a way?

• Would not be the first time, as I’m looking for wrong terms and therefore doesn’t find the solution.

---

For solution seekers

I had some language-Dimensions data from the Sites.xml with (en_US), which made the work somewhat complicated than necessary: My base-reason to search a more comprehensive solution.

Perhaps this is a totally twisted approach. But should someone have the same error messages with the base language DE, because of en_US in Sites.xml , here are my working files:

Path: Vendor.BasePackage/Resources/Private/Content/Sites.xml
(Vendor.Site have to change to the base-package name.)

<?xml version="1.0" encoding="UTF-8"?>
<root>
    <site name="SiteName" state="1" siteResourcesPackageKey="Vendor.Site" siteNodeName="sitename">
        <nodes formatVersion="2.0">
            <node nodeName="sitename">
                <variant workspace="live" nodeType="TYPO3.Neos.NodeTypes:Page" sortingIndex="100" version="1" removed="" hidden="" hiddenInIndex="">
                    <dimensions>

                        <language>de_DE</language>

                    </dimensions>
                    <accessRoles __type="array"/>
                    <properties>
                        <title __type="string">Home</title>
                        <uriPathSegment __type="string">home</uriPathSegment>
                    </properties>
                </variant>
            </node>
        </nodes>
    </site>
</root>

Path: root/Configuration/Settings.yaml

TYPO3:
  TYPO3CR:
    contentDimensions:
      language:
        # The default dimension that is applied when creating nodes without specifying a dimension
        default: 'de_DE'
        # The default preset to use if no URI segment was given when resolving languages in the router
        defaultPreset: 'de_DE'
        label: 'Language'
        icon: 'icon-language'
        presets:
          'de_DE':
            label: 'Deutsch (Deutschland)'
            values: ['de_DE']
            uriSegment: ''

With this Settings and Sites.xml I have no errors left, easy to login in backend, and new nodes have the de_DE dimensionvalue in Database.

Helping Flow-command:

./flow configuration:show --type Settings --path TYPO3.TYPO3CR.contentDimensions

Helping Migrate Files path-to:
Packages/Application/TYPO3.TYPO3CR/Migrations/TYPO3CR
use with:

# NO node dimension to DEFAULT dimension
./flow node:migrate --version 20140326143834
# SOME node dimension to DEFAULT dimension (with or without --version)
/flow node:migrate 20150716212459