Ergebnis 1 bis 4 von 4

Thema: Kann nicht updaten?

  1. #1
    Contao-Nutzer
    Registriert seit
    27.05.2014.
    Beiträge
    121

    Standard Kann nicht updaten?

    Ahoi!

    Wir wollten soeben eine etwas ältere Contao-Installation von 4.6.14 auf 4.9.x updaten, genutzt wird die aktuelle PHP 7.4 Version. Der Fehler:

    Code:
    An error occurred while executing the "contao:install-web-dir" command: 
      PHP Fatal error:  Uncaught Error: Undefined class constant 'VERSIONS' in /v  
      ar/www/vhosts/DOMAIN.COM/httpdocs/contao-2018/vendor/contao/core-bund  
      le/src/DependencyInjection/Compiler/AddPackagesPass.php:32                   
      Stack trace:                                                                 
      #0 /var/www/vhosts/DOMAIN.COM/httpdocs/contao-2018/vendor/symfony/dep  
      endency-injection/Compiler/Compiler.php(140): Contao\CoreBundle\DependencyI  
      njection\Compiler\AddPackagesPass->process()                                 
      #1 /var/www/vhosts/DOMAIN.COM/httpdocs/contao-2018/vendor/symfony/dep  
      endency-injection/ContainerBuilder.php(789): Symfony\Component\DependencyIn  
      jection\Compiler\Compiler->compile()                                         
      #2 /var/www/vhosts/DOMAIN.COM/httpdocs/contao-2018/vendor/symfony/htt  
      p-kernel/Kernel.php(643): Symfony\Component\DependencyInjection\ContainerBu  
      ilder->compile()                                                             
      #3 /var/www/vhosts/DOMAIN.COM/httpdocs/contao-2018/vendor/contao/mana  
      ger-bundle/src/HttpKernel/ContaoKernel.php(234): Symfony\Component\HttpKern  
      el\Kernel->initializeContainer()                                             
      #4 /var/www/vhosts/DOMAIN.COM/httpdocs/contao-2018/vendor/symfony/htt  
      p-kernel/Kern in /var/www/vhosts/DOMAIN.COM/httpdocs/contao-2018/vend  
      or/contao/core-bundle/src/DependencyInjection/Compiler/AddPackagesPass.php   
      on line 32
    Allerdings kann ich nicht viel damit anfangen, etwas zu allgemein für meinen unterdurchschnittlichen Geschmack. Ist das bekannt oder machen wir etwas falsch? Das ähnlichste, das ich finden konnte, war folgendes, da kam aber kein Ende:
    https://community.contao.org/de/show...l=1#post541529

    Composer ist bereits geupdated. Zur Vollständigkeit meine composer.json:
    Code:
    {
        "name": "contao/managed-edition",
        "type": "project",
        "description": "Contao Open Source CMS",
        "license": "LGPL-3.0-or-later",
        "authors": [
            {
                "name": "Leo Feyer",
                "homepage": "https://github.com/leofeyer"
            }
        ],
        "require": {
            "php": "^7.1",
            "contao/calendar-bundle": "^4.6",
            "contao/comments-bundle": "^4.6",
            "contao/conflicts": "*@dev",
            "contao/faq-bundle": "^4.6",
            "contao/listing-bundle": "^4.6",
            "contao/manager-bundle": "4.6.*",
            "contao/news-bundle": "^4.6",
            "contao/newsletter-bundle": "^4.6",
            "dieschittigs/contao-recaptcha": "^1.1",
            "madeyourday/contao-rocksolid-antispam": "^2.0",
            "madeyourday/contao-rocksolid-columns": "^2.0",
            "madeyourday/contao-rocksolid-custom-elements": "^2.2",
            "madeyourday/contao-rocksolid-frontend-helper": "^2.0",
            "madeyourday/contao-rocksolid-icon-picker": "^2.0",
            "madeyourday/contao-rocksolid-mega-menu": "^2.0",
            "madeyourday/contao-rocksolid-slider": "^2.0",
            "madeyourday/contao-rocksolid-theme-assistant": "^2.0"
        },
        "conflict": {
            "contao-components/installer": "<1.3"
        },
        "require-dev": {
            "sensiolabs/security-checker": "^4.1"
        },
        "extra": {
            "branch-alias": {
                "dev-4.6": "4.6.x-dev"
            },
            "contao-component-dir": "assets"
        },
        "autoload": {
            "psr-4": {
                "App\\": "src/"
            }
        },
        "scripts": {
            "post-install-cmd": [
                "@php vendor/bin/contao-setup --ansi"
            ],
            "post-update-cmd": [
                "@php vendor/bin/contao-setup --ansi"
            ]
        }
    }
    Nachtrag:
    Spooky's Anweisung befolgt, die composer.json abgeändert und danach das composer update ausgeführt (https://community.contao.org/de/show...l=1#post541177), führt zu folgender Konsolenausgabe:
    Versuche ich irgendein Paket danach upzudaten, kommt nur folgendes:
    Code:
    Loading composer repositories with package information
    Updating dependencies
    Lock file operations: 3 installs, 35 updates, 3 removals
      - Removing composer/package-versions-deprecated (1.11.99.4)
      - Removing zendframework/zend-code (3.4.1)
      - Removing zendframework/zend-eventmanager (3.2.1)
      - Upgrading beberlei/assert (v3.3.1 => v3.3.2)
      - Upgrading composer/ca-bundle (1.2.11 => 1.3.1)
      - Upgrading contao-components/ace (1.4.13 => 1.4.13.1)
      - Upgrading contao/conflicts (dev-main b52fb0f => dev-main dcbdd8d)
      - Upgrading contao/manager-plugin (2.11.0 => 2.11.1)
      - Upgrading doctrine/dbal (2.13.4 => 2.13.7)
      - Upgrading doctrine/lexer (1.2.1 => 1.2.2)
      - Upgrading friendsofsymfony/http-cache-bundle (2.9.2 => 2.11.2)
      - Upgrading guzzlehttp/promises (1.5.0 => 1.5.1)
      - Locking laminas/laminas-code (4.5.1)
      - Upgrading michelf/php-markdown (1.9.0 => 1.9.1)
      - Locking ocramius/package-versions (1.11.0)
      - Upgrading ocramius/proxy-manager (2.2.3 => 2.13.0)
      - Upgrading psr/container (1.1.1 => 1.1.2)
      - Upgrading simplepie/simplepie (1.5.6 => 1.5.8)
      - Upgrading sonata-project/google-authenticator (2.2.0 => 2.3.1)
      - Upgrading swiftmailer/swiftmailer (v6.2.7 => v6.3.0)
      - Upgrading symfony/cache-contracts (v1.1.10 => v1.1.11)
      - Upgrading symfony/debug (v4.4.31 => v4.4.36)
      - Upgrading symfony/deprecation-contracts (v2.4.0 => v2.5.0)
      - Upgrading symfony/inflector (v5.3.4 => v5.4.0)
      - Upgrading symfony/polyfill-ctype (v1.23.0 => v1.24.0)
      - Upgrading symfony/polyfill-iconv (v1.23.0 => v1.24.0)
      - Upgrading symfony/polyfill-intl-grapheme (v1.23.1 => v1.24.0)
      - Upgrading symfony/polyfill-intl-idn (v1.23.0 => v1.24.0)
      - Upgrading symfony/polyfill-intl-normalizer (v1.23.0 => v1.24.0)
      - Upgrading symfony/polyfill-mbstring (v1.23.1 => v1.24.0)
      - Upgrading symfony/polyfill-php72 (v1.23.0 => v1.24.0)
      - Upgrading symfony/polyfill-php80 (v1.23.1 => v1.24.0)
      - Upgrading symfony/property-access (v4.4.30 => v4.4.36)
      - Upgrading symfony/service-contracts (v1.1.9 => v1.1.11)
      - Upgrading symfony/string (v5.3.7 => v5.4.2)
      - Upgrading symfony/templating (v5.3.7 => v5.4.0)
      - Upgrading symfony/var-dumper (v4.4.31 => v4.4.36)
      - Upgrading symfony/var-exporter (v4.4.31 => v4.4.34)
      - Upgrading tecnickcom/tcpdf (6.4.2 => 6.4.4)
      - Upgrading twig/twig (v2.14.7 => v2.14.10)
      - Locking webimpress/safe-writer (2.2.0)
    Writing lock file
    Installing dependencies from lock file
    Nothing to install, update or remove
    1 package suggestions were added by new dependencies, use `composer suggest` to see details.
    Package contao-components/compass is abandoned, you should avoid using it. No replacement was suggested.
    Package doctrine/doctrine-cache-bundle is abandoned, you should avoid using it. No replacement was suggested.
    Package doctrine/reflection is abandoned, you should avoid using it. Use roave/better-reflection instead.
    Package leafo/scssphp is abandoned, you should avoid using it. Use scssphp/scssphp instead.
    Package league/uri-hostname-parser is abandoned, you should avoid using it. No replacement was suggested.
    Package league/uri-manipulations is abandoned, you should avoid using it. No replacement was suggested.
    Package league/uri-schemes is abandoned, you should avoid using it. No replacement was suggested.
    Package oyejorge/less.php is abandoned, you should avoid using it. No replacement was suggested.
    Package patchwork/utf8 is abandoned, you should avoid using it. Use symfony/polyfill-mbstring or symfony/string instead.
    Package phpunit/php-token-stream is abandoned, you should avoid using it. No replacement was suggested.
    Package scheb/two-factor-bundle is abandoned, you should avoid using it. Use scheb/2fa-bundle instead.
    Package sonata-project/google-authenticator is abandoned, you should avoid using it. No replacement was suggested.
    Package swiftmailer/swiftmailer is abandoned, you should avoid using it. Use symfony/mailer instead.
    Package symfony/inflector is abandoned, you should avoid using it. Use EnglishInflector from the String component instead.
    Package webmozart/path-util is abandoned, you should avoid using it. Use symfony/filesystem instead.
    Generating optimized autoload files
    Class Sensio\Bundle\FrameworkExtraBundle\Tests\DependencyInjection\AddParamConverterPassTest located in ./vendor/sensio/framework-extra-bundle/Tests/DependencyInjection/Compiler/AddParamConverterPassTest.php does not comply with psr-4 autoloading standard. Skipping.
    Class Sensio\Bundle\FrameworkExtraBundle\Tests\DependencyInjection\AddExpressionLanguageProvidersPassTest located in ./vendor/sensio/framework-extra-bundle/Tests/DependencyInjection/Compiler/AddExpressionLanguageProvidersPassTest.php does not comply with psr-4 autoloading standard. Skipping.
    Class Sensio\Bundle\FrameworkExtraBundle\Tests\Request\ParamConverter\ArgumentNameConverterTest located in ./vendor/sensio/framework-extra-bundle/Tests/Request/ArgumentNameConverterTest.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\AbstractUri located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\Data located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\File located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\Ftp located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\Http located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\Uri located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\UriException located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\Ws located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    ocramius/package-versions: Generating version class...
    ocramius/package-versions: ...done generating version class
    contao/manager-plugin: Generating plugin class...
    contao/manager-plugin: ...done generating plugin class
    Could not open input file: vendor/bin/contao-setup
    57 packages you are using are looking for funding.
    Use the `composer fund` command to find out more!
    > @php vendor/bin/contao-setup --ansi
    Script @php vendor/bin/contao-setup --ansi handling the post-update-cmd event returned with error code 1
    Nachtrag 2: Nun lässt sich nichtmal mehr der Cache neu erstellen und die Webseite geht gar nicht mehr
    Geändert von d33eniz (12.01.2022 um 18:14 Uhr)

  2. #2
    Alter Contao-Hase Avatar von bizon
    Registriert seit
    16.06.2010.
    Beiträge
    1.123

    Standard

    Zitat Zitat von d33eniz
    Nachtrag:
    Spooky's Anweisung befolgt, die composer.json abgeändert und danach das composer update ausgeführt https://community.contao.org/de/show...l=1#post541529, führt zu folgender Konsolenausgabe:
    Versuche ich irgendein Paket danach upzudaten, kommt nur folgendes:
    Meines Wissens ist diese Änderung erst ab Contao 4.11 nötig und führt in Contao 4.9 zu Fehlern. Siehe die letzte Zeile der von dir geposteten Konsolenausgabe.

    Wenn du tatsächlich PHP 7.4 einsetzt und auf Contao 4.9 updaten willst, dann ändere die composer.json wie folgt:
    Code:
        "require": {
            "php": "^7.4",
            "contao/calendar-bundle": "^4.9",
            "contao/comments-bundle": "^4.9",
            "contao/conflicts": "*@dev",
            "contao/faq-bundle": "^4.9",
            "contao/listing-bundle": "^4.9",
            "contao/manager-bundle": "4.9.*",
            "contao/news-bundle": "^4.9",
            "contao/newsletter-bundle": "^4.9",
    Dann führe ein vollständiges Update aus.

  3. #3
    Contao-Nutzer
    Registriert seit
    27.05.2014.
    Beiträge
    121

    Standard

    Meines Wissens ist diese Änderung erst ab Contao 4.11 nötig und führt in Contao 4.9 zu Fehlern. Siehe die letzte Zeile der von dir geposteten Konsolenausgabe.
    Ah richtig, wieder rückgängig gemacht, dann ging schon wieder etwas mehr. Die composer.json habe ich wie angegeben abgeändert und danach composer update- tada, Upgrade auf 4.9 hat Problemlos funktioniert. Bin ich blöd oder warum hat das setzen der Versionen im Manager mit anschließendem Update zu Fehlern geführt? War doch prinzipiell das Gleiche oder nicht?

    Und danach ließen sich auch die restlichen Pakete über den Manager mitupdaten. Besten Dank!

  4. #4
    Alter Contao-Hase Avatar von bizon
    Registriert seit
    16.06.2010.
    Beiträge
    1.123

    Standard

    Was den Contao-Manager betrifft, kann ich dir keine Antwort geben, da ich den Contao-Manager nicht benutze.
    Hauptsache das Update hat funktioniert.

Aktive Benutzer

Aktive Benutzer

Aktive Benutzer in diesem Thema: 1 (Registrierte Benutzer: 0, Gäste: 1)

Lesezeichen

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •