[SOLVED] Changed overwrite possibilities?

Crazy, but Yepp, works at the end:

So for other stumblers:
I did:
root.manifest (root/composer.json excerpt: only require part):

"require": {
        "neos/neos": "~3.0.0",
        "neos/nodetypes": "~3.0.0",
        "neos/seo": "~2.0.0",
        "neos/redirecthandler-neosadapter": "^2.0",
        "neos/redirecthandler-databasestorage": "^2.0",
        "neos/swiftmailer": "~6.0.0",
        "flowpack/simplesearch-contentrepositoryadaptor": "^2.0",
        "flowpack/simplesearch": "^2.0",
        "jonnitto/googlemaps": "^2.3",
        "vendorname/mysitepackage": "3.0.6"
    },

Own package have to be at the end.

Package composer.manifest (VendorName.SiteName/composer.json excerpt: only require part):

"require": {
        "neos/neos": "*",
        "neos/nodetypes": "*",
        "neos/seo": "*"
    },

And all the other packages where you like to overwrite parts.

Then I did:
1. execute: composer update
2. execute: rm Configuration/PackageStates.php
3. execute: ./flow neos.flow:package:rescan
short ./flow package:rescan throws an error:
Unrecognized Command
Sorry, but he command “neos.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.

So use the long «noes.flow:package…» from step 3.
##4. DONE – Overwrite is operative!

Tank you @aertmann!

###Last short question:

  • Is it ok, when I delete all the migrations.stuff in extra. Looks not simplifying: Or would the deleting be a cause for next stumbling?
1 Like