Site Package not working after upgrade to neos 4.0


(Andre Beherzig) #1

I Upgraded to latest version of Neos 4.0. Most things seems to run correct on my test system but my first ever added site package is gone. The demo site package is still working but my own created site package is only displaying the content not the template/theme I have created. Any idea why this happen? Should I also “migrate” this site package? How?

Here is my configuration:

{
“name”: “neos/neos-base-distribution”,
“description”: “Neos Base Distribution”,
“license”: “GPL-3.0+”,
“support”: {
“email”: "hello@neos.io",
“slack”: “http://slack.neos.io/”,
“forum”: “https://discuss.neos.io/”,
“wiki”: “https://discuss.neos.io/c/the-neos-project/project-documentation”,
“issues”: “https://github.com/neos/neos-development-collection/issues”,
“docs”: “http://neos.readthedocs.org/”,
“source”: “https://github.com/neos/neos-base-distribution
},
“config”: {
“vendor-dir”: “Packages/Libraries”,
“bin-dir”: “bin”
},
“require”: {
“neos/neos”: “~4.0.0”,
“neos/nodetypes”: “~4.0.0”,
“neos/demo”: “~4.0.0”,
“neos/site-kickstarter”: “~4.0.0”,

    "neos/neos-ui": "~1.0",
    "neos/neos-ui-compiled": "~1.0",

    "neos/seo": "~2.0",
    "flowpack/neos-matomo": "^3.0",
    "neos/setup": "~4.0",
    "flowpack/neos-frontendlogin": "~3.0",
    "neos/redirecthandler-neosadapter": "~2.0",
    "neos/redirecthandler-databasestorage": "~2.0",
    "neos/form": "^4.1",
    "neos/form-builder": "^1.0",
    "neos/form-fusionrenderer": "^1.0",
    "neos/redirecthandler": "^2.0"

},
"require-dev": {
    "neos/buildessentials": "~4.1.0",
    "mikey179/vfsstream": "~1.6",
    "phpunit/phpunit": "~6.0.0",
    "symfony/css-selector": "~2.0",
    "neos/behat": "dev-master"
},
"replace": {
    "typo3/neos-base-distribution": "3.3.9"
},
"suggest": {
    "ext-pdo_sqlite": "For running functional tests out-of-the-box this is required"
},
"scripts": {
    "post-update-cmd": "Neos\\Flow\\Composer\\InstallerScripts::postUpdateAndInstall",
    "post-install-cmd": "Neos\\Flow\\Composer\\InstallerScripts::postUpdateAndInstall",
    "post-package-update": "Neos\\Flow\\Composer\\InstallerScripts::postPackageUpdateAndInstall",
    "post-package-install": "Neos\\Flow\\Composer\\InstallerScripts::postPackageUpdateAndInstall"
}

}

I am running into this error while trying to migrate the site package:

./flow flow:core:migrate <lw.castioni>

-su: syntax error near unexpected token `newline’


(Rene Rehme) #2

I don’t know if that fixes your main problem but if you want to execute flow:core:migrate the right way you have to remove the “<” and “>” character like this (based on your example):

./flow flow:core:migrate lw.castioni

(Andre Beherzig) #3

Thanks Rene for your fast reply but I also tested without <> an getting this:

./flow flow:core:migrate lw.castioni

====================================================================================
Migrating package “lw.castioni”

fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git

Migration TYPO3.FLOW3-201201261636 (2012-01-26 16:36)

Adjust to the major changes in FLOW3 1.1 when coming from 1.0.

Skipping: Not a Git working copy, use --force to apply changes anyways


(Christian Müller) #4

First of all why would you install or have installed the demo site in an actual installation? I would strongly suggest removing it. Second you apparently don’t version your project which is not a good idea. core:migrate works by creating git commits in your project so you can review them and make sure nothing went wrong. As you don’t have a git repository there it fails.


(Andre Beherzig) #5

@christianm thanks for your reply.

  1. I was testing Neos to find out the best setup (which packages are helpful which aren’t…) for my needs. Testing different packages, the demo sites and was creating my first template (site package).

  2. Yes I understand. I will use Git and Versions in production system. But is there any chance “easy way” to manually migrate the “old” template site package into new Neos 4.0?

thanks