I’m using Neos 2.2 and ran into an error while trying to repair some nodes.
Here is my error message:
Run integrity checks related to Neos features
Catchable Fatal Error: Argument 1 passed to TYPO3\Flow\Utility\PositionalArraySorter::__construct() must be of the type array, null given, called in /Applications/mampstack-5.5.35-1/apps/demo/htdocs/Data/Temporary/Development/Cache/Code/Flow_Object_Classes/TYPO3_TYPO3CR_Domain_Service_ConfigurationContentDimensionPresetSource.php on line 38 and defined in /Applications/mampstack-5.5.35-1/apps/demo/htdocs/Packages/Libraries/neos/utility-arrays/Classes/TYPO3/Flow/Utility/PositionalArraySorter.php line 85
Open Data/Logs/Exceptions/20160516225955272efe.txt for a full stack trace.
If needed, I’m going to post the full stack trace.
What can I do?
I have the same error: all I have done is install Neos using composer and then added database and backend user credentials. I used Neos’ setup process to create a blank site.
I log in, add a Text node to a page, and most Ajax actions (save, update, publish) return this error.
Catchable Fatal Error: Argument 1 passed to TYPO3\\Flow\\Utility\\PositionalArraySorter::__construct() must be of the type array, null given, called in [PROJECT ROOT]/Data/Temporary/Development/Cache/Code/Flow_Object_Classes/TYPO3_TYPO3CR_Domain_Service_ConfigurationContentDimensionPresetSource.php on line 38 and defined in [PROJECT ROOT]/Packages/Libraries/neos/utility-arrays/Classes/TYPO3/Flow/Utility/PositionalArraySorter.php line 85
Tracing it through, it seems to indicate that $this->configuration is null in Data/Temporary/Development/Cache/Code/Flow_Object_Classes/TYPO3_TYPO3CR_Domain_Service_ConfigurationContentDimensionPresetSource.php.
Not sure if I should create a new thread but I’m having the same issue.
Running ./flow package:rescan fails with:
Sorry, but he command "typo3.flow:package:rescan" must be specified by its full command
identifier because it is a compile time command which cannot be resolved
from an abbreviated command identifier.
I have stumbled over this multiple times but it cannot be changed. The problem is that those commands are designated as compile time commands and therefore need to be identified very early. If called with the short name Flow starts off a runtime run and then figures out that the command is designated compile time (so it can tell you what to run) and then shuts down.
I have been thinking to try if we couldn’t just run the correct command in a subrequest and just return the output. If the command handling managed to get through to the point to output this message everything in the installation seems alright and it shouldn’t be a problem to do that…