All these commands were done without any errors or important hints. Unfortunately I always got an 500 internal server errro. The exception is telling that the package Neos.Demo is missing. This is true. I deleted it before and this was my intention. What was going wrong?
Thanks for your hints.
Here you can find the exception log file:
Exception #1297759968: Exception while property mapping for target type "TYPO3\TYPO3CR\Domain\Model \NodeInterface", at property path "": Invalid resource URI "resource://Neos.Demo/Public/NodeTypes/Thumbnails/Homepage.png": Package "Neos.Demo" is not available.
13 TYPO3\Flow\Property\PropertyMapper_Original::convert("/sites/neosdemo@live;language=en_US", "TYPO3\TYPO3CR\Domain\Model\NodeInterface", TYPO3\Flow\Mvc\Controller\MvcPropertyMappingConfiguration)
12 call_user_func_array(array|2|, array|3|)
11 TYPO3\Flow\Object\DependencyInjection\DependencyProxy::__call("convert", array|3|)
10 TYPO3\Flow\Mvc\Controller\Argument_Original::setValue("/sites/neosdemo@live;language=en_US")
9 TYPO3\Flow\Mvc\Controller\AbstractController_Original::mapRequestArgumentsToControllerArguments()
8 TYPO3\Flow\Mvc\Controller\ActionController_Original::processRequest(TYPO3\Flow\Mvc\ActionRequest, TYPO3\Flow\Http\Response)
7 TYPO3\Flow\Mvc\Dispatcher_Original::initiateDispatchLoop(TYPO3\Flow\Mvc\ActionRequest, TYPO3\Flow \Http\Response)
6 TYPO3\Flow\Mvc\Dispatcher_Original::dispatch(TYPO3\Flow\Mvc\ActionRequest, TYPO3\Flow\Http \Response)
5 TYPO3\Flow\Mvc\DispatchComponent_Original::handle(TYPO3\Flow\Http\Component\ComponentContext)
4 TYPO3\Flow\Http\Component\ComponentChain_Original::handle(TYPO3\Flow\Http\Component \ComponentContext)
3 TYPO3\Flow\Http\Component\ComponentChain_Original::handle(TYPO3\Flow\Http\Component \ComponentContext)
2 TYPO3\Flow\Http\RequestHandler::handleRequest()
1 TYPO3\Flow\Core\Bootstrap::run()
Thanks for your quick reply.
I removed this file. But unfortunately it doesn’t help. I got the same exception and the file was generated again. In this file Configuration/PackageStates.php I haven’t found an entry like ‘Neos.Demo’.
Do you use resource://Neos.Demo/Public/NodeTypes/Thumbnails/Homepage.png as templatePath in one of your fusion files? Or does one of your NodeTypes in the NodeTypes.yaml files start with Neos.Demo:...? If so, please change them to the current package name as Neos will try to search for a template in a Neos.Demo Package (which doesn’t exist any more).
I have still the same problem. I am not able to create a (empty) site using Neos CMS LTS Version 2.3.8 at Domain-Factory. Can someone help?
Meanwhile I tried another way to get a working Neos. I drop all tables from the database and afterwards I executed the following command:
$ ./flow doctrine:migrate
I got an exception:
Exception #1355480641 in line 137 of /kunden/xxxxx_xxxxx/Neos/neoscms/Data/Temporary/Production/Cache/Code/Flow_Object_Classes/TYPO3_Setup_Step_DatabaseStep.php
: Failed loading /usr/local/php5/ZendOptimizer.so: /usr/local/php5/ZendOptimizer.so: undefined symbol: zend_opcode_handlers
Fatal error: Cannot use $this as parameter in /kunden/xxxxx_xxxxx/Neos/neoscms/Packages/Libraries/ocramius/proxy-manager/src/ProxyManager/GeneratorStrategy/Eval
uatingGeneratorStrategy.php(68) : eval()'d code on line 340
The same exception was thrown when I tried to call the setup using webinterface. Only the table “flow_doctrine_migrationstatus” was created after executing the setup or the migration command.
Any help would be appreciated.
It seems nobody can help me.
I have asked the support of the provider DomainFactory regarding the failed loading of ZendOptimizer. They told me I should create a special php.ini for the domain and drop the entry for the Zendoptimizer.
I did it and now I got the same exception but without an additional exception log file. Again: I deleted all tables from the database and on the next step I executed the following command which was canceled with a fatal error :
$ ./flow doctrine:migrate
Fatal error: Cannot use $this as parameter in /kunden/xxxxx_xxxxx/Neos/neoscms/Packages/Libraries/ocramius/proxy-manager/src/ProxyManager/GeneratorStrategy/EvaluatingGeneratorStrategy.php(68) : eval()'d code on line 340
Is anybody here who has an idea how I can solve this problem?
Hi Christian, maybe you are right. Actually I did not know it. The provider DomainFactory has offered a pre-installed version Neos CMS LTS Version 2.3.8 which I have selected.
After the installation the Neos.Demo package was available and working. Up to now I was not able to create a new package or site.
I am pretty sure it’s something about the PHP version. What does php -v say and can you find out what version of the ocramius/proxy-manager is installed?
The changelog Packages/Libraries/ocramius/proxy-manager/CHANGELOG.md is telling me that the version 2.0.1 has been installed.
Using the mydomain.de/setup I am able to perform the first steps before I get still the same exception:
Exception #1355480641 in line 137 of /kunden/xxxxx_xxxxx/Neos/neoscms/Data/Temporary/Production/Cache/Code/Flow_Object_Classes/TYPO3_Setup_Step_DatabaseStep.php:
Fatal error: Cannot use $this as parameter in /kunden/xxxxx_xxxxx/Neos/neoscms/Packages/Libraries/ocramius/proxy-manager/src/ProxyManager/GeneratorStrategy/EvaluatingGeneratorStrategy.php(68) : eval()'d code on line 340
Neither of the mentioned PHP versions is an actual CLI binary, which you should have for Flow and Neos. So you should figure out where your hoster has an actual PHP CLI binary (eg. PHP 7.0.24 (cli) (built: Oct 17 2017 00:34:37) ( NTS )) from my local system.
avoid the %PHP_BINDIR% at this place, since this is used to locate the CLI binary from the SAPI binary. Use the full path in the setting. Afterwards, you might at most need to flush the cache.
I used a new browser instance, but I’ve got still the same exception. Only one empty DB table was created (flow_doctrine_migrationstatus). I wondered a little bit: the (old) settings for the DB were still available in the setup form. (it was not removed by flushing).
has the same effect. I can find several settings with the right reference to the php-binary:
Even in the first line of the flow script: #!/usr/local/bin/php7-70STABLE-CLI
The DB configuration is stored inside the Settings.yaml, which is not flushed for good reasons
Anyway, I just out of curiousity installed the Neos 2.3 LTS on our DF account and the installation went really smoothly, it also already added the phpBinaryPathAndFilename to settings automatically so even the command line tool worked
So somewhere down your path a few things must have gone off road and now cause a lot of pain unfortunately Let’s try to get that solved!
I then further followed your steps from the first post, and after importing the new site (without the resource clean&publish, node repair) I also ended up with the exception about the Neos.Demo package.
What I then did however, was just flush the cache, rebuild it and then I could correctly log into the Neos backend again start working on that site. export FLOW_CONTEXT=Production ./flow flow:cache:flush --force ./flow flow:core:compile && ./flow doctrine:compileproxies && ./flow flow:cache:warmup
I always do the warmup with the below three commands because I occasionally had the proxy compilation fail and then things would not work. With this line things always work out correctly.
So maybe it’s better to just restart all over instead of trying to fix the broken setup?