Wrong node order in the CR

Using Neos & Flow
1

Hi

I’m rebuilding my site on version 2.3.2. (had same errors on ealier versions)

The Pages have 3 ContentCollection top, main and footer (in this order).

In both, the NodeType configuration and in the TS they are declared in that order.
Further more they have position statements.

./flow node:repair --dry-run

shows, that the order is not correct. (I also looked at the exported XML) Also tried to change the PrimaryContent of ‘main’ to a normal ContentCollection.
Nothing helps (so far).
In the Neos stucture tree they appear in the correct order.
I had some strange effects in my last installation, so I’m keen to make every thing clean now.

  Child node "footer" in "/sites/website" does not have a stable identifier
    1 identifiers of child nodes need to be updated
    Child node "footer" in "/sites/website" does not have a stable identifier
    1 identifiers of child nodes need to be updated
    Checking for child nodes that need reordering ...
    Should move node named "main" after node named "top" in "/sites/website"
    Should move node named "footer" after node named "main" in "/sites/website"
    Should move node named "main" after node named "top" in "/sites/website/node-57c5a7ea2058e"
    Should move node named "main" after node named "top" in "/sites/website/node-57c5a930bbbc5"
    Should move node named "main" after node named "top" in "/sites/website"
    Should move node named "footer" after node named "main" in "/sites/website"

TypoScript

		top = ContentCollection {
			nodePath = 'top'
			@position = 'before main'
		}

		main = ContentCollection {
		#main = PrimaryContent {
			nodePath = 'main'
		}

		// Shared footer wird in der homePage gespeichert
		footer = ContentCollection {
			nodePath = ${q(site).children('footer').property('_path')}
			collection = ${q(site).children('footer').children()}
		}

NodeTypes

'Eg.Website:Page':
  ui:
    label: 'Standard-Seite'
    icon: 'icon-file'
    help:
      message: 'Seite für den allgemeinen Gebrauch.'
  superTypes:
    'TYPO3.Neos:Document': TRUE
  childNodes:
    top:
      position: 'before main'
      type: 'TYPO3.Neos:ContentCollection'
      constraints:
        nodeTypes:
#          '*': FALSE
          'Eg.Website:Teaser': TRUE
          'Eg.Website:TeaserReference': TRUE
          'Eg.Website:RandomTeaser': TRUE
    main:
      type: 'TYPO3.Neos:ContentCollection'
  constraints:
    nodeTypes:
      'TYPO3.Neos.NodeTypes:Page': FALSE
      'Eg.Website:HomePage': FALSE

And

'Eg.Website:HomePage':
  ui:
    label: 'Start-Seite'
    icon: 'icon-globe'
    help:
     message: 'Die Homepage. (Es kann nur Eine geben)'
  superTypes:
    'Eg.Website:Page': TRUE
  childNodes:
    footer:
      position: 'after main'
      type: 'TYPO3.Neos:ContentCollection'
      constraints:
        nodeTypes:
          '*': FALSE
          'TYPO3.Neos.NodeTypes:Headline': TRUE
          'TYPO3.Neos.NodeTypes:Text': TRUE
  constraints:
    nodeTypes:
      'TYPO3.Neos.NodeTypes:Page': FALSE
      'Eg.Website:HomePage': FALSE

What is going wrong here? Any ideas?
By the way: what is the purpose (advantage) of PrimaryContent.

Thanx in advance
Klaus

Update:
The same thing happend always with the multiColumn NodeTypes. The columns 0,1 and 2 (3Colunms) appear in the reversed order.

2

The position is defined in the NodeTypes.yaml, so you can drop it from Fusion (TypoScript). On top of that, what ``` node:repair` wants to do is the expected course of action, no? It would move so everything is in the correct order.

So, what is the actual error you see?

3

Hi Karsten,

I had some strange things in my “old” Neos installation: So I want to make everything perfect in this installation.
I just worried about the output of node:repair --dry-run. “You should move Node …” . I’m insecure.
node:repair (without --dry-run) gives no errors and does not correct the node order.

The node order in sites.xml doesn’t follows the order in the NodeType definition (it’s reversed).

Question:
What could be the reason for that behaviour? Is there anything I have to do?

Klaus

4

Hey Klaus,

really weird that the node ordering is reversed – I don’t get this really; and I’ve never seen this happening before.

Is it also reversed if you e.g. run the Neos Demo Site, and create a threeColumn container? If yes, we should continue looking at your setup (PHP version, Mysql, …), if not, we should again look at your NodeTypes, TypoScript etc.

Thanks,
Sebastian

5

Hi Sebastian,

I will install it to a server managed by Punkt.de.
I will check the behaviour there. Than we know if it is my local installation (I’m working with phpStorm on Ubuntu 16.04), or Neos, or my faulty configuration.-

I will not erease my old installation,becaus it makes really crazy things:

  • Newly created Nodes can’t be deleted any more.
  • A DataSource SelectBox doesn’t work reliable.
  • ‘*’: FALSE don’t work at all on contraints for documentNodes
  • Sometimes the CSS is missing in the backend.

Some of these Issues I wrote in earlier posts.

To get rid of this problems I cleaned up everything and moved it over to a brand new system (2.3.2).
Everthing is solved, exept the noder order.

Now I don’t have the time. It’s the last hour before my holydays.
I’ll be back on Sept. 22. Than we can continue.

Thanks, so far
Klaus

1 Like
6

Hi Sebastian,

I’m back from Holidays (Nice, but way to short).
The site is now also hosted by Punkt.de. Running on free BSD.
Newly created documentNodes show the wrong order of the ContentCollections within them (like before).
The ordering of Multicolumn-Elements are reversed.
So the Mistake(es) seem(s) to be in my configuration.

Any ideas?

Klaus