Is it possible to migrate from Neos 2.0.0-beta5 to Neos 2.0 released?

it’s certainly a silly question, but perhaps ? :slight_smile:

Yes it’s possible, update your composer.json in your distribution, run composer update and the doctrine and node migration and everything should work.

The upgrade instruction from 1.2 to 2.0 can help:
https://www.neos.io/develop/download/upgrade-instructions-2-0.html

1 Like

Ok thank you very much Dominique …
I will do it soon and I will confirm you the result !
Best regards
jean-claude

sorry Dominique but I did not succeed …
I have this error … I tried to understand where I am wrong,
but I do not understand in which file is the problem… please, can you help me ?..

I read this http://neos.readthedocs.org/en/2.0/Appendixes/ChangeLogs/200-RC1.html#bugfix-node-repair-should-consider-dimensions

in my settings.yaml I inserted
Neos:
userInterface:
scrambleTranslatedLabels: FALSE

because, I don’t want to use translation, I just want one language …
and I don’t want now to modify all my “yaml” files …

Uncaught exception #1265213849 in line 435 of /var/www/vhosts/art-et-sol.com/httpdocs/Neos2-0/Packages/Framework/TYPO3.Flow/Classes/TYPO3/Flow/Object/DependencyInjection/ProxyClassBuilder.php: The object “TYPO3\TYPO3CR\Domain\Service\ContentDimensionCombinator” which was specified as a property in the object configuration of object “TYPO3\Neos\Command\NodeCommandControllerPlugin” (automatically registered class) does not exist. Check for spelling mistakes and if that dependency is correctly configured.

This class exist in your project ? If yes, sounds like a cache issue, remove everything from Data/Temporary should help, if not, you are not on 2.0, so something wrong with your composer configuration.

1 Like

No, I have not this class in my project … but when I do “./flow node:repair” … I have this error.
I read that node:repair should consider dimensions . …
Additionally TYPO3\TYPO3CR\Domain\Service\ContentDimensionCombinator was introduced to deal with generating possible dimension configuarations for Context generation

as I have already deleted Temporary … I think as you said that something is wrong with the composer configuration … Is there a built composer.json ?..

Can you post your composer.json here ?

1 Like

Hi Jean

Make sure you flush the caches. If it still doesn’t work, use the --force flag or rm the temporary folder manually.

Also make sure you have the updated versions of all the packages, use composer show -i to see the versions.

Regarding the scrambleTranslatedLabels, that’s a core development feature you shouldn’t use unless you’re translating the Neos user interface.

I’m not sure what you mean with only one language, but you don’t really have to do anything to do that. It’s more about not using dimensions. Or maybe you’re talking about setting the default language in the user interface?

Cheers,
Aske

1 Like

thank’s Aske and Dominique

Yes Aske, it’s more about not using dimensions. Here is my "composer show -i "

$ php composer.phar show -i
behat/transliterator v1.0.1 String transliterator
composer/installers v1.0.21 A multi-framework Composer library installer
doctrine/annotations v1.2.6 Docblock Annotations Parser
doctrine/cache v1.4.1 Caching library offering an object-oriented API for many cache backends
doctrine/collections v1.3.0 Collections Abstraction library
doctrine/common v2.5.0 Common Library for Doctrine projects
doctrine/dbal v2.5.1 Database Abstraction Layer
doctrine/inflector v1.0.1 Common String Manipulations with regard to casing and singular/plural rules.
doctrine/instantiator 1.0.5 A small, lightweight utility to instantiate objects in PHP without invoking their constructors
doctrine/lexer v1.0.1 Base library for a lexer that can be used in Top-Down, Recursive Descent Parsers.
doctrine/migrations v1.0.0 Database Schema migrations using Doctrine DBAL
doctrine/orm v2.4.7 Object-Relational-Mapper for PHP
flowpack/behat dev-master 42ba311 Behat support package for TYPO3 Flow
flowpack/neos-frontendlogin 2.0.0 TYPO3 Neos plugin implementing a simple frontend login
gedmo/doctrine-extensions v2.3.12 Doctrine2 behavioral extensions
google/apiclient 1.1.4 Client library for Google APIs
imagine/imagine 0.6.2 Image processing for PHP 5.3
mikey179/vfsStream v1.5.0 Virtual file system to mock the real file system in unit tests.
phpdocumentor/reflection-docblock 2.0.4
phpspec/prophecy v1.5.0 Highly opinionated mocking framework for PHP 5.3+
phpunit/php-code-coverage 2.2.2 Library that provides collection, processing, and rendering functionality for PHP code coverage information.
phpunit/php-file-iterator 1.4.1 FilterIterator implementation that filters files based on a list of suffixes.
phpunit/php-text-template 1.2.1 Simple template engine.
phpunit/php-timer 1.0.7 Utility class for timing
phpunit/php-token-stream 1.4.6 Wrapper around PHP’s tokenizer extension.
phpunit/phpunit 4.8.4 The PHP Unit Testing framework.
phpunit/phpunit-mock-objects 2.3.6 Mock Object library for PHPUnit
sebastian/comparator 1.2.0 Provides the functionality to compare PHP values for equality
sebastian/diff 1.3.0 Diff implementation
sebastian/environment 1.3.2 Provides functionality to handle HHVM/PHP environments
sebastian/exporter 1.2.1 Provides the functionality to export PHP variables for visualization
sebastian/global-state 1.0.0 Snapshotting of global state
sebastian/recursion-context 1.0.1 Provides functionality to recursively process PHP variables
sebastian/version 1.0.6 Library that helps with managing the version number of Git-hosted PHP projects
symfony/console v2.7.3 Symfony Console Component
symfony/dom-crawler v2.5.12 Symfony DomCrawler Component
symfony/yaml v2.5.12 Symfony Yaml Component
typo3/buildessentials 3.0.0 TYPO3 Flow Build Toolchain Essentials
typo3/eel 3.0.0 The Embedded Expression Language (Eel) is a building block for creating Domain Specific Languages
typo3/flow 3.0.0 TYPO3 Flow Application Framework
typo3/fluid 3.0.0 Next-Generation Templating Framework for TYPO3 Flow and TYPO3 Neos, also backported to TYPO3 CMS
typo3/form 2.0.0 Extensible and flexible API for building web forms
typo3/imagine 2.0.0 Provides a Flow factory for the imagine library
typo3/kickstart 3.0.0 A simple generator for controller and views.
typo3/media 2.0.0-beta5 The Media package
typo3/neos 2.0.0 The next generation of the popular open-source CMS.
typo3/neos-googleanalytics 1.0.1 Google Analytics integration for TYPO3 Neos
typo3/neos-kickstarter 2.0.0 A simple generator for Neos assets, like sites and plugins.
typo3/neos-nodetypes 2.0.0 Node type configuration for TYPO3 Neos
typo3/neos-seo 1.0.5 SEO configuration and tools for TYPO3 Neos
typo3/neosdemotypo3org 2.0.0 Site package for the Neos Demo Site
typo3/party 3.0.1 A PHP implementation of the OASIS Customer Information Quality (CIQ) XML Standard.
typo3/setup 2.0.1 An extensible setup tool for TYPO3 Flow based applications
typo3/twitter-bootstrap 2.2.0 Simple and flexible HTML, CSS, and Javascript for popular user interface components and interactions. Packaged for use with TYPO3 Flow
typo3/typo3cr 2.0.0-beta5 Content repository based on TYPO3 Flow, specifically made for TYPO3 Neos.
typo3/typoscript 2.0.0-beta5 TypoScript is a hierarchical, prototype based processing language

Here is my composer.json

{
“name”: “typo3/neos-base-distribution”,
“description” : “TYPO3 Neos Base Distribution”,
“license”: “GPL-3.0+”,
“support”: {
“email”: "neos@typo3.org",
“irc”: “irc://irc.freenode.org/typo3-neos”,
“forum”: “http://forum.typo3.org/index.php/f/121/”,
“issues”: “https://jira.typo3.org/”,
“source”: “https://git.typo3.org/
},
“config”: {
“vendor-dir”: “Packages/Libraries”,
“bin-dir”: “bin”
},
“require”: {
“typo3/neos”: “~2.0”,
“typo3/neos-nodetypes”: “~2.0”,
“typo3/neosdemotypo3org”: “~2.0”,
“typo3/neos-kickstarter”: “~2.0”,

    "doctrine/migrations": "~1.0",

    "typo3/neos-seo": "~1.0",
    "typo3/imagine": "~2.0",
    "typo3/twitter-bootstrap": "~2.0",
    "typo3/form": "~2.0",
    "typo3/setup": "~2.0",

    "typo3/typo3cr": "2.0.0-beta5",
    "typo3/typoscript": "2.0.0-beta5",
    "typo3/media": "2.0.0-beta5",
    "typo3/fluid": "3.0.*@beta",
    "typo3/eel": "3.0.*@beta",
    "typo3/party": "3.0.*@beta",
    "typo3/kickstart": "3.0.*@beta",
    "typo3/neos-googleanalytics": "~1.0"
},
"require-dev": {
    "typo3/buildessentials": "~3.0",
    "mikey179/vfsstream": "~1.5",
    "phpunit/phpunit": "~4.6",
    "flowpack/behat": "dev-master"
},
"suggest": {
    "ext-pdo_sqlite": "For running functional tests out-of-the-box this is required"
},
"scripts": {
    "post-update-cmd": "TYPO3\\Flow\\Composer\\InstallerScripts::postUpdateAndInstall",
    "post-install-cmd": "TYPO3\\Flow\\Composer\\InstallerScripts::postUpdateAndInstall",
    "post-package-update":"TYPO3\\Flow\\Composer\\InstallerScripts::postPackageUpdateAndInstall",
    "post-package-install":"TYPO3\\Flow\\Composer\\InstallerScripts::postPackageUpdateAndInstall"
}

}

As you see you use some beta package in your composer json, for Neos all package should be ~2.0 and Flow ~3.0 and composer update, flush the cache and should work :wink:

1 Like

Ok !
I replace all the 2.0.0-beta5 with 2.0 and 3.0.*@beta with 3.0

correct ?..

Use ~2.0 or ~3.0 instead of the beta versions and it should be fine.

1 Like

Ok thank you Karsten …

I modified composer.json and now …
almost everything is correct and the site works,
but now I install a 2.0 Neos clean to be reassured …

here is my composer.json file modified :

{
“name”: “typo3/neos-base-distribution”,
“description” : “TYPO3 Neos Base Distribution”,
“license”: “GPL-3.0+”,
“support”: {
“email”: "neos@typo3.org",
“irc”: “irc://irc.freenode.org/typo3-neos”,
“forum”: “http://forum.typo3.org/index.php/f/121/”,
“issues”: “https://jira.typo3.org/”,
“source”: “https://git.typo3.org/
},
“config”: {
“vendor-dir”: “Packages/Libraries”,
“bin-dir”: “bin”
},
“require”: {
“typo3/neos”: “~2.0”,
“typo3/neos-nodetypes”: “~2.0”,
“typo3/neosdemotypo3org”: “~2.0”,
“typo3/neos-kickstarter”: “~2.0”,

    "doctrine/migrations": "~1.0",

    "typo3/neos-seo": "~1.0",
    "typo3/imagine": "~2.0",
    "typo3/twitter-bootstrap": "~2.0",
    "typo3/form": "~2.0",
    "typo3/setup": "~2.0",

    "typo3/typo3cr": "~2.0",
    "typo3/typoscript": "~2.0",
    "typo3/media": "~2.0",
    "typo3/fluid": "3.0.*",
    "typo3/eel": "3.0.*",
    "typo3/party": "3.0.*",
    "typo3/kickstart": "3.0.*",
    "typo3/neos-googleanalytics": "~1.0"
},
"require-dev": {
    "typo3/buildessentials": "~3.0",
    "mikey179/vfsstream": "~1.5",
    "phpunit/phpunit": "~4.6",
    "flowpack/behat": "dev-master"
},
"suggest": {
    "ext-pdo_sqlite": "For running functional tests out-of-the-box this is required"
},
"scripts": {
    "post-update-cmd": "TYPO3\\Flow\\Composer\\InstallerScripts::postUpdateAndInstall",
    "post-install-cmd": "TYPO3\\Flow\\Composer\\InstallerScripts::postUpdateAndInstall",
    "post-package-update":"TYPO3\\Flow\\Composer\\InstallerScripts::postPackageUpdateAndInstall",
    "post-package-install":"TYPO3\\Flow\\Composer\\InstallerScripts::postPackageUpdateAndInstall"
}

}

There is still a lot in your composer.json that it not needed. If you require typo3/neos that in turn will require typo3/flow (which will require e.g. typo3/fluid in turn), typo3/typoscript, …

To get a feeling for that, try removing dependencies one by one and run composer update --dry-run after every edit. It will show you what it would remove - and if it would, you need to undo the last step :wink:

1 Like

Should look more or less like https://git.typo3.org/Neos/Distributions/Base.git/blob/f9607fffb0aa1c5828fd40296a83d36c4705eba2:/composer.json

1 Like

Hello Karsten and Hello Aske …
hello … you are too nice for me :smile:
I started with Neos early this year and I realize that I should have started with Flow …
that’s why I do not understand everything !! …
I also realize all the work you do for Neos will be “Magical” !
I will do immediately what you advise me and I will confirm the results …
Best regards and Cheers
jean-claude

Hello Aske and Hello Karsten,

I just do what you advised me and now everything is perfect. I thank you once again …

for those who have the same problem as me, here’s a composer.json amended to update from Neos beta 5 to Neos 2.0. Note that I’ve worked on my file that I saved with my method … backup Neos on server linux
after “php composer.phar update” and “./flow doctrine: migrate” and then “./flow node: repair” …
I found my site and everything works perfectly.

here is my composer.json to do the update :

{
“name”: “typo3/neos-base-distribution”,
“description” : “TYPO3 Neos Base Distribution”,
“license”: “GPL-3.0+”,
“support”: {
“email”: "hello@neos.io",
“slack”: “http://slack.neos.io/”,
“irc”: “irc://irc.freenode.org/typo3-neos”,
“forum”: “https://discuss.neos.io/”,
“issues”: “https://jira.neos.io/”,
“source”: “https://git.typo3.org/
},
“config”: {
“vendor-dir”: “Packages/Libraries”,
“bin-dir”: “bin”
},
“require”: {
“typo3/neos”: “2.0.",
“typo3/neos-nodetypes”: "2.0.
”,
“typo3/neosdemotypo3org”: “2.0.",
“typo3/neos-kickstarter”: "2.0.
”,

    "doctrine/migrations": "@dev",

    "typo3/neos-seo": "~1.0",
    "typo3/imagine": "~2.0",
    "typo3/twitter-bootstrap": "~2.0",
    "typo3/form": "~2.0",
    "typo3/setup": "~2.0"
},
"require-dev": {
    "typo3/buildessentials": "3.0.*@rc",
    "mikey179/vfsstream": "1.5.*",
    "phpunit/phpunit": "4.6.*",
    "flowpack/behat": "dev-master"
},
"suggest": {
    "ext-pdo_sqlite": "For running functional tests out-of-the-box this is required"
},
"scripts": {
    "post-update-cmd": "TYPO3\\Flow\\Composer\\InstallerScripts::postUpdateAndInstall",
    "post-install-cmd": "TYPO3\\Flow\\Composer\\InstallerScripts::postUpdateAndInstall",
    "post-package-update":"TYPO3\\Flow\\Composer\\InstallerScripts::postPackageUpdateAndInstall",
    "post-package-install":"TYPO3\\Flow\\Composer\\InstallerScripts::postPackageUpdateAndInstall"
}

}

Here is a minimal composer manifest for Neos 2.0: https://gist.github.com/kdambekalns/46e0e33b73af2b2db4a0