[SOLVED] Problem with upgrade to Neos 3.0 (Node type "" does not exist)

Hi,
I have upgrade a first project but there was a lot of find/replace stuff for own Fusion/Fluid Code and so on.

This time I tried it very accurate, step by step. (System os x 10.11.6, mamp pro with php 7.0.8)

Unfortunately the ./flow check within step 9 within upgrade instructions. doesn’t echo anything > blank line in Terminal!!

###Situation Start:
initial-position: oldProject
target-position: updatedProject

CHECK: At this moment, the ./flow execution is run totally normal > Output:

Neos 2.3.8 (“Development” context)
usage: ./flow

See “./flow help” for a list of all available commands.

Also php -v:

PHP 7.0.8 (cli) (built: Jul 11 2016 11:30:15) ( NTS )
Copyright (c) 1997-2016 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2016 Zend Technologies

###THEN:

  1. Duplicate oldProject in htdocs and named it updatedProject
  2. Duplicate MySql Database oldProjectData to updatedProjectData
  3. Changed Configuration/Settings.yaml dbname: updatedProjectData
  4. Check Frontend and Backend all is fine.
  5. Did a ```./flow node:repair > all is fine
  6. Change some data to check if Frontend/Backend and Database is correct related. > All is fine
  7. (2.) Downloaded the DistributionUpgrader.phar && chmod
  8. Check again ./flow > All normal with Output like above
  9. (3.) Run ./DistributionUpgrader.phar Output:

No installation path given! Please give the absolute path of the installation you want to upgrade.
Usage: ./DistributionUpgrader.phar <INSTALLATION_PATH>

10 . Run again with path: ./DistributionUpgrader.phar absolute/path/to/Folder/Where/DistributionUpgrader.phar/is/in > Output:

Adapting composer.json…
Replaced installer scripts namespace.
Finished composer.json

Adapting Configuration…
Done adapting configuration.
Adapting front controllers…
Done adapting front controllers.
Removing leftover “IncludeCachedConfiguration” files…
Done removing leftover “IncludeCachedConfiguration” files

The upgrading script finished.
The following files have been changed by it and depending on
your version control and deployment strategy you have to make sure
that the files are also changed on any other systems you have:


/composer.json
/Configuration/Routes.yaml
/Configuration/Settings.yaml
/Configuration/Testing/Settings.yaml
/flow
/flow.bat
/Web/index.php

11 . Did all steps from 4. to 8. in upgrade instructions Also Check the files > all path are now with «Neos»

###Problem:
12 . (9.) Check if the Flow command line comes up without any errors:
./flow > Output: Empty jump to next Terminal line > no error, but also no Neos 3.0.0 output!

Tried again and again; also tried directly after the run of DistributionUpgrader.phar, same result again and again. The execution ./flow does output:
#“”
(nothing!)

php -v output is still OK:

PHP 7.0.8 (cli) (built: Jul 11 2016 11:30:15) ( NTS )
Copyright (c) 1997-2016 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2016 Zend Technologies

Also New Terminal-Window, Reboot OS X. No change…
###Question

  • What could I do different, so the Update-Prozess (10.-12.) with ./flow will run correctly?

Do you have a fatal error? So try to run flow this way:

php -d display_errors=1 ./flow

Thank you @pamegli,
have found maybe a problem and solved it.
Now, I can do the update-process 1-11 without problems till the end on point 12.
And I only have two pieces of search/replace for TYPO3. Great!

But in step 12 (Test your website), there Is an error throwing at the end:
node type “” does not exist:

I flushed the cache and repaired nodes. But alltime the same throwing:

./flow node:repair
Run checks for basic node integrity in the content repository

Checking for nodes with abstract or undefined node types …
Node type “” does not exist

Type: Neos\ContentRepository\Exception
Code: 1316451800
File: Data/Temporary/Development/Cache/Code/Flow_Object_Classes/Neos_ContentRepos
itory_Domain_Service_NodeTypeManager.php
Line: 243

Open Data/Logs/Exceptions/2017021611474454786a.txt for a full stack trace.

2017021611474454786a.txt value:

Exception #1361467839 in line 121 of /Users/mh/Sites/MAMP-htdocs/sd-3test.neos/Data/Temporary/Development/Cache/Code/Flow_Object_Classes/Neos_Flow_ResourceManagement_ResourceManager.php: The configuration for the resource target "localWebDirectoryStaticResourcesTarget" defined in your settings has not defined a valid "target" option. Please check the configuration syntax and make sure that the specified class "Neos\Flow\Resource\Target\FileSystemSymlinkTarget" really exists.

26 Neos\Flow\ResourceManagement\ResourceManager_Original::initializeTargets()
25 Neos\Flow\ResourceManagement\ResourceManager_Original::initialize()
24 Neos\Flow\ResourceManagement\ResourceManager_Original::getCollection("static")
23 Neos\Flow\Package::Neos\Flow\{closure}("Flow_PublicResourcesFiles", array|1890|, "Neos\Flow\Monitor\FileMonitor::filesHaveChanged")
22 Closure::__invoke("Flow_PublicResourcesFiles", array|1890|, "Neos\Flow\Monitor\FileMonitor::filesHaveChanged")
21 call_user_func_array(array|2|, array|3|)
20 Neos\Flow\SignalSlot\Dispatcher::dispatch("Neos\Flow\Monitor\FileMonitor", "filesHaveChanged", array|3|)
19 Neos\Flow\Monitor\FileMonitor_Original::emitFilesHaveChanged("Flow_PublicResourcesFiles", array|1890|)
18 Neos\Flow\Monitor\FileMonitor_Original::detectChanges()
17 Neos\Flow\Package::Neos\Flow\{closure}(Neos\Flow\Core\Booting\Step, "runtime", "Neos\Flow\Core\Booting\Sequence::afterInvokeStep")
16 Closure::__invoke(Neos\Flow\Core\Booting\Step, "runtime", "Neos\Flow\Core\Booting\Sequence::afterInvokeStep")
15 call_user_func_array(array|2|, array|3|)
14 Neos\Flow\SignalSlot\Dispatcher::dispatch("Neos\Flow\Core\Booting\Sequence", "afterInvokeStep", array|3|)
13 Neos\Flow\Core\Booting\Sequence::invokeStep(Neos\Flow\Core\Booting\Step, Neos\Flow\Core\Bootstrap)
12 Neos\Flow\Core\Booting\Sequence::invokeStep(Neos\Flow\Core\Booting\Step, Neos\Flow\Core\Bootstrap)
11 Neos\Flow\Core\Booting\Sequence::invokeStep(Neos\Flow\Core\Booting\Step, Neos\Flow\Core\Bootstrap)
10 Neos\Flow\Core\Booting\Sequence::invokeStep(Neos\Flow\Core\Booting\Step, Neos\Flow\Core\Bootstrap)
9 Neos\Flow\Core\Booting\Sequence::invokeStep(Neos\Flow\Core\Booting\Step, Neos\Flow\Core\Bootstrap)
8 Neos\Flow\Core\Booting\Sequence::invokeStep(Neos\Flow\Core\Booting\Step, Neos\Flow\Core\Bootstrap)
7 Neos\Flow\Core\Booting\Sequence::invokeStep(Neos\Flow\Core\Booting\Step, Neos\Flow\Core\Bootstrap)
6 Neos\Flow\Core\Booting\Sequence::invokeStep(Neos\Flow\Core\Booting\Step, Neos\Flow\Core\Bootstrap)
5 Neos\Flow\Core\Booting\Sequence::invoke(Neos\Flow\Core\Bootstrap)
4 Neos\Flow\Cli\CommandRequestHandler::boot("Runtime")
3 Neos\Flow\Cli\CommandRequestHandler::handleRequest()
2 Neos\Flow\Core\Bootstrap::run()
1 require("/Users/mh/Sites/MAMP-htdocs/sd-3test.neos/Packages/Framework/Neos.Flow/Scripts/flow.php")```
```

Crazy about this: the 3 records with unstructured nodetypes are the same in the old installation 2.3.9 without any problems/error throwing!
OLD:
<img src="//assets-discuss-neos-io.s3-eu-central-1.amazonaws.com/original/2X/0/05604203adaf3b218726dba1028bc03a27b2f98e.png" width="690" height="46">
NEW:
<img src="//assets-discuss-neos-io.s3-eu-central-1.amazonaws.com/original/2X/d/dd728a6cb602cb440565d643da1837dafc907167.png" width="690" height="25">

The records are not deletable on shorthand: 
<img src="//assets-discuss-neos-io.s3-eu-central-1.amazonaws.com/original/2X/3/356e0e05ca8cf9e778e9999e9fce14900a3a00b5.png" width="330" height="141">

Can't find help in Documentation/Google...
- ***Does anyone have a solution?***

At the end I don’t know, which particular change (try and error) have solve the problem.
But yet, the project ist working on Neos 3.0 and the Images don’t have mess in lastchange date also all other is working without problems/errors.