5.6.x "con4gis\CoreBundle\Command\ImportCommand" cannot have an empty name.

"con4gis\CoreBundle\Command\ImportCommand" cannot have an empty name.

Was will mir diese Felermeldung sagen?

Code:

$ /bin/php83 -q -dmax_execution_time=0 -dmemory_limit=-1 -ddisplay_errors=0 -ddisplay_startup_errors=0 -derror_reporting=0 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /www/htdocs/w7itrd56/webpage/public/contao-manager.phar.php composer update bugbuster/contao-dlstats-bundle christianbarkowsky/contao-tiny-compress-images con4gis/maps contao/manager-bundle madeyourday/contao-rocksolid-columns madeyourday/contao-rocksolid-custom-elements madeyourday/contao-rocksolid-icon-picker madeyourday/contao-rocksolid-mega-menu madeyourday/contao-rocksolid-slider madeyourday/contao-rocksolid-theme-assistant trilobit-gmbh/contao-headerfootercode-bundle contao/news-bundle contao/listing-bundle contao/conflicts contao/core-bundle --with-dependencies --no-install --no-scripts --no-dev --no-progress --no-ansi --no-interaction --optimize-autoloader Loading composer repositories with package information contao/manager-plugin: Dumping generated plugins file... contao/manager-plugin: ...done dumping generated plugins file Updating dependencies Lock file operations: 0 installs, 61 updates, 0 removals - Upgrading contao-components/ace (1.43.3 => 1.43.4) - Upgrading contao-components/simplemodal (3.0.3 => 3.0.4) - Upgrading dasprid/enum (1.0.6 => 1.0.7) - Upgrading doctrine/collections (2.3.0 => 2.4.0) - Upgrading doctrine/dbal (3.10.2 => 3.10.3) - Upgrading doctrine/doctrine-bundle (2.16.1 => 2.18.0) - Upgrading doctrine/orm (2.20.6 => 2.20.7) - Upgrading doctrine/persistence (3.4.0 => 3.4.3) - Upgrading doctrine/sql-formatter (1.5.2 => 1.5.3) - Upgrading jaybizzle/crawler-detect (v1.3.5 => v1.3.6) - Upgrading lcobucci/clock (3.3.1 => 3.5.0) - Upgrading lcobucci/jwt (5.5.0 => 5.6.0) - Upgrading league/flysystem (3.30.0 => 3.30.1) - Upgrading league/flysystem-bundle (3.5.0 => 3.6.0) - Upgrading nelmio/cors-bundle (2.5.0 => 2.6.0) - Upgrading nelmio/security-bundle (v3.5.1 => v3.6.0) - Upgrading nette/schema (v1.3.2 => v1.3.3) - Upgrading nikic/php-parser (v5.6.1 => v5.6.2) - Upgrading paragonie/constant_time_encoding (v2.7.0 => v2.8.2) - Upgrading php-feed-io/feed-io (v6.1.1 => v6.1.2) - Upgrading simplepie/simplepie (1.8.1 => 1.9.0) - Upgrading spomky-labs/pki-framework (1.3.0 => 1.4.0) - Upgrading symfony/cache (v7.3.2 => v7.3.5) - Upgrading symfony/config (v7.3.2 => v7.3.4) - Upgrading symfony/console (v7.3.3 => v7.3.5) - Upgrading symfony/debug-bundle (v7.3.0 => v7.3.5) - Upgrading symfony/dependency-injection (v7.3.3 => v7.3.4) - Upgrading symfony/doctrine-bridge (v7.3.3 => v7.3.5) - Upgrading symfony/doctrine-messenger (v7.3.3 => v7.3.4) - Upgrading symfony/error-handler (v7.3.2 => v7.3.4) - Upgrading symfony/finder (v7.3.2 => v7.3.5) - Upgrading symfony/framework-bundle (v7.3.3 => v7.3.5) - Upgrading symfony/http-client (v6.4.25 => v6.4.26) - Upgrading symfony/http-foundation (v7.3.3 => v7.3.5) - Upgrading symfony/http-kernel (v7.3.3 => v7.3.5) - Upgrading symfony/intl (v7.3.3 => v7.3.5) - Upgrading symfony/lock (v7.3.2 => v7.3.4) - Upgrading symfony/mailer (v7.3.3 => v7.3.5) - Upgrading symfony/mime (v7.3.2 => v7.3.4) - Upgrading symfony/monolog-bridge (v7.3.3 => v7.3.5) - Upgrading symfony/process (v7.3.3 => v7.3.4) - Upgrading symfony/property-info (v7.3.1 => v7.3.5) - Upgrading symfony/routing (v7.3.2 => v7.3.4) - Upgrading symfony/security-bundle (v7.3.3 => v7.3.4) - Upgrading symfony/security-core (v7.3.3 => v7.3.5) - Upgrading symfony/security-http (v7.3.3 => v7.3.5) - Upgrading symfony/serializer (v7.3.3 => v7.3.5) - Upgrading symfony/string (v7.3.3 => v7.3.4) - Upgrading symfony/translation (v7.3.3 => v7.3.4) - Upgrading symfony/twig-bundle (v7.3.2 => v7.3.4) - Upgrading symfony/type-info (v7.3.3 => v7.3.5) - Upgrading symfony/validator (v7.3.3 => v7.3.5) - Upgrading symfony/var-dumper (v7.3.3 => v7.3.5) - Upgrading symfony/var-exporter (v7.3.3 => v7.3.4) - Upgrading symfony/web-profiler-bundle (v7.3.3 => v7.3.5) - Upgrading symfony/yaml (v7.3.3 => v7.3.5) - Upgrading terminal42/escargot (1.6.2 => 1.6.3) - Upgrading twig/extra-bundle (v3.21.0 => v3.22.0) - Upgrading twig/string-extra (v3.21.0 => v3.22.0) - Upgrading twig/twig (v3.21.1 => v3.22.0) - Upgrading webmozart/assert (1.11.0 => 1.12.1) Writing lock file Package doctrine/annotations is abandoned, you should avoid using it. No replacement was suggested. Package doctrine/cache is abandoned, you should avoid using it. No replacement was suggested. 129 packages you are using are looking for funding. Use the `composer fund` command to find out more! Found 4 security vulnerability advisories affecting 1 package. Run "composer audit" for a full list of advisories. # Process terminated with exit code 0 # Result: OK $ /bin/php83 -q -dmax_execution_time=0 -dmemory_limit=-1 -ddisplay_errors=0 -ddisplay_startup_errors=0 -derror_reporting=0 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /www/htdocs/w7itrd56/webpage/public/contao-manager.phar.php composer install --no-dev --no-progress --no-ansi --no-interaction --optimize-autoloader Installing dependencies from lock file Verifying lock file contents can be installed on current platform. Nothing to install, update or remove Package doctrine/annotations is abandoned, you should avoid using it. No replacement was suggested. Package doctrine/cache is abandoned, you should avoid using it. No replacement was suggested. Generating optimized autoload files contao/manager-plugin: Dumping generated plugins file... contao/manager-plugin: ...done dumping generated plugins file 134 packages you are using are looking for funding. Use the `composer fund` command to find out more! > @php vendor/bin/contao-setup In CheckExceptionOnInvalidReferenceBehaviorPass.php line 116: The service "doctrine.orm.default_annotation_metadata_driver" has a depende ncy on a non-existent service "annotation_reader". Script @php vendor/bin/contao-setup handling the post-install-cmd event returned with error code 1 # Process terminated with exit code 1 # Result: General error

Contao 5.5 hat das Lebensende erreicht, aktualisiere auf Contao 5.6.4.

Das willl ich, aber es geht nicht.
Die Aktualisierung hat mit dieser Fehlmeldung abgebrochen:

Code:

$ /bin/php83 -q -dmax_execution_time=0 -dmemory_limit=-1 -ddisplay_errors=0 -ddisplay_startup_errors=0 -derror_reporting=0 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /www/htdocs/w7itrd56/webpage/public/contao-manager.phar.php composer require contao/manager-bundle=5.6.* contao/news-bundle=5.6.* contao/listing-bundle=5.6.* --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction /www/htdocs/w7itrd56/webpage/composer.json has been updated # Process terminated with exit code 0 # Result: OK > Resolving dependencies using Composer Cloud v3.8.2 [7.7MiB/0.26s] Loading composer repositories with package information [90.4MiB/16.64s] Updating dependencies [31.2MiB/18.60s] Lock file operations: 2 installs, 75 updates, 6 removals [31.2MiB/18.60s] - Removing doctrine/cache (2.2.0) [31.2MiB/18.60s] - Removing doctrine/common (3.5.0) [31.2MiB/18.60s] - Removing symfony/polyfill-iconv (v1.33.0) [31.2MiB/18.60s] - Removing symfony/polyfill-php72 (v1.31.0) [31.2MiB/18.61s] - Removing voku/portable-ascii (2.0.3) [31.2MiB/18.61s] - Removing voku/portable-utf8 (6.0.13) [31.2MiB/18.61s] - Upgrading cmsig/seal (0.6.1 => 0.12.3) [31.2MiB/18.61s] - Upgrading cmsig/seal-loupe-adapter (0.6.1 => 0.12.2) [31.2MiB/18.61s] - Upgrading cmsig/seal-symfony-bundle (0.6.1 => 0.12.2) [31.2MiB/18.61s] - Upgrading contao-components/ace (1.43.3 => 1.43.4) [31.2MiB/18.61s] - Upgrading contao-components/altcha (1.5.1 => 2.2.4) [31.2MiB/18.61s] - Upgrading contao-components/simplemodal (3.0.3 => 3.0.4) [31.2MiB/18.61s] - Upgrading contao-components/swiper (11.2.10 => 12.0.3) [31.2MiB/18.61s] - Upgrading contao-components/tinymce4 (7.9.1 => 8.2.0) [31.2MiB/18.61s] - Upgrading contao/core-bundle (5.5.16 => 5.6.4) [31.2MiB/18.62s] - Upgrading contao/listing-bundle (5.5.16 => 5.6.4) [31.2MiB/18.62s] - Upgrading contao/manager-bundle (5.5.16 => 5.6.4) [31.2MiB/18.62s] - Upgrading contao/news-bundle (5.5.16 => 5.6.4) [31.2MiB/18.62s] - Upgrading dasprid/enum (1.0.6 => 1.0.7) [31.2MiB/18.62s] - Upgrading doctrine/collections (2.3.0 => 2.4.0) [31.2MiB/18.62s] - Upgrading doctrine/dbal (3.10.2 => 4.3.4) [31.2MiB/18.62s] - Upgrading doctrine/doctrine-bundle (2.16.1 => 2.18.0) [31.2MiB/18.62s] - Upgrading doctrine/orm (2.20.6 => 3.5.3) [31.2MiB/18.62s] - Upgrading doctrine/persistence (3.4.0 => 3.4.3) [31.2MiB/18.62s] - Upgrading doctrine/sql-formatter (1.5.2 => 1.5.3) [31.2MiB/18.62s] - Upgrading jaybizzle/crawler-detect (v1.3.5 => v1.3.6) [31.2MiB/18.62s] - Locking joomla/string (4.0.0) [31.2MiB/18.62s] - Upgrading lcobucci/clock (3.3.1 => 3.5.0) [31.2MiB/18.63s] - Upgrading lcobucci/jwt (5.5.0 => 5.6.0) [31.2MiB/18.63s] - Upgrading league/flysystem (3.30.0 => 3.30.1) [31.2MiB/18.63s] - Upgrading league/flysystem-bundle (3.5.0 => 3.6.0) [31.2MiB/18.63s] - Upgrading loupe/loupe (0.9.5 => 0.12.16) [31.2MiB/18.63s] - Locking loupe/matcher (0.2.0) [31.2MiB/18.63s] - Upgrading mjaschen/phpgeo (4.2.1 => 6.0.0) [31.2MiB/18.63s] - Upgrading nelmio/cors-bundle (2.5.0 => 2.6.0) [31.2MiB/18.63s] - Upgrading nelmio/security-bundle (v3.5.1 => v3.6.0) [31.2MiB/18.63s] - Upgrading nette/schema (v1.3.2 => v1.3.3) [31.2MiB/18.64s] - Upgrading nikic/php-parser (v5.6.1 => v5.6.2) [31.2MiB/18.64s] - Upgrading nitotm/efficient-language-detector (v2.1.2 => v3.0.0) [31.2MiB/18.64s] - Upgrading paragonie/constant_time_encoding (v2.7.0 => v3.1.3) [31.2MiB/18.64s] - Upgrading php-feed-io/feed-io (v6.1.1 => v6.1.2) [31.2MiB/18.64s] - Upgrading simplepie/simplepie (1.8.1 => 1.9.0) [31.2MiB/18.64s] - Upgrading spomky-labs/pki-framework (1.3.0 => 1.4.0) [31.2MiB/18.64s] - Upgrading symfony/cache (v7.3.2 => v7.3.5) [31.2MiB/18.64s] - Upgrading symfony/config (v7.3.2 => v7.3.4) [31.2MiB/18.65s] - Upgrading symfony/console (v7.3.3 => v7.3.5) [31.2MiB/18.65s] - Upgrading symfony/debug-bundle (v7.3.0 => v7.3.5) [31.2MiB/18.65s] - Upgrading symfony/dependency-injection (v7.3.3 => v7.3.4) [31.2MiB/18.65s] - Upgrading symfony/doctrine-bridge (v7.3.3 => v7.3.5) [31.2MiB/18.65s] - Upgrading symfony/doctrine-messenger (v7.3.3 => v7.3.4) [31.2MiB/18.65s] - Upgrading symfony/error-handler (v7.3.2 => v7.3.4) [31.2MiB/18.65s] - Upgrading symfony/finder (v7.3.2 => v7.3.5) [31.2MiB/18.65s] - Upgrading symfony/framework-bundle (v7.3.3 => v7.3.5) [31.2MiB/18.65s] - Upgrading symfony/http-client (v6.4.25 => v6.4.26) [31.2MiB/18.65s] - Upgrading symfony/http-foundation (v7.3.3 => v7.3.5) [31.2MiB/18.66s] - Upgrading symfony/http-kernel (v7.3.3 => v7.3.5) [31.2MiB/18.66s] - Upgrading symfony/intl (v7.3.3 => v7.3.5) [31.2MiB/18.66s] - Upgrading symfony/lock (v7.3.2 => v7.3.4) [31.2MiB/18.66s] - Upgrading symfony/mailer (v7.3.3 => v7.3.5) [31.2MiB/18.66s] - Upgrading symfony/mime (v7.3.2 => v7.3.4) [31.2MiB/18.66s] - Upgrading symfony/monolog-bridge (v7.3.3 => v7.3.5) [31.2MiB/18.66s] - Upgrading symfony/process (v7.3.3 => v7.3.4) [31.2MiB/18.66s] - Upgrading symfony/property-info (v7.3.1 => v7.3.5) [31.2MiB/18.66s] - Upgrading symfony/routing (v7.3.2 => v7.3.4) [31.2MiB/18.66s] - Upgrading symfony/security-bundle (v7.3.3 => v7.3.4) [31.2MiB/18.66s] - Upgrading symfony/security-core (v7.3.3 => v7.3.5) [31.2MiB/18.66s] - Upgrading symfony/security-http (v7.3.3 => v7.3.5) [31.2MiB/18.66s] - Upgrading symfony/serializer (v7.3.3 => v7.3.5) [31.2MiB/18.66s] - Upgrading symfony/string (v7.3.3 => v7.3.4) [31.2MiB/18.66s] - Upgrading symfony/translation (v7.3.3 => v7.3.4) [31.2MiB/18.67s] - Upgrading symfony/twig-bundle (v7.3.2 => v7.3.4) [31.2MiB/18.67s] - Upgrading symfony/type-info (v7.3.3 => v7.3.5) [31.2MiB/18.67s] - Upgrading symfony/validator (v7.3.3 => v7.3.5) [31.2MiB/18.67s] - Upgrading symfony/var-dumper (v7.3.3 => v7.3.5) [31.2MiB/18.67s] - Upgrading symfony/var-exporter (v7.3.3 => v7.3.4) [31.2MiB/18.67s] - Upgrading symfony/web-profiler-bundle (v7.3.3 => v7.3.5) [31.2MiB/18.67s] - Upgrading symfony/yaml (v7.3.3 => v7.3.5) [31.2MiB/18.67s] - Upgrading terminal42/escargot (1.6.2 => 1.6.3) [31.2MiB/18.67s] - Upgrading twig/extra-bundle (v3.21.0 => v3.22.0) [31.2MiB/18.67s] - Upgrading twig/string-extra (v3.21.0 => v3.22.0) [31.2MiB/18.67s] - Upgrading twig/twig (v3.21.1 => v3.22.0) [31.2MiB/18.67s] - Upgrading wamania/php-stemmer (v3.0.1 => v4.0.0) [31.2MiB/18.67s] - Upgrading webmozart/assert (1.11.0 => 1.12.1) [30.3MiB/18.68s] Writing lock file [17.7MiB/18.72s] <warning>Package doctrine/annotations is abandoned, you should avoid using it. No replacement was suggested.</warning> [17.9MiB/19.00s] No security vulnerability advisories found. [18.5MiB/19.00s] Memory usage: 18.46MB (peak: 208.88MB), time: 19.01s. [18.5MiB/19.00s] Finished Composer Cloud resolving. # Job ID AevSarO5JaxUQyyUA3jh2BPrcuZLqHBRUB6OTyOzTZ7LoIRPTjGMcHk8IoQ0PGrsA3EQtr7kQdgucdZjpeB9DonLQLeik0cV37x9nitDXZrjIlNsb5GMLb completed in 24 seconds # Memory usage: 18.46MB (peak: 208.88MB), time: 19.01s. $ /bin/php83 -q -dmax_execution_time=0 -dmemory_limit=-1 -ddisplay_errors=0 -ddisplay_startup_errors=0 -derror_reporting=0 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /www/htdocs/w7itrd56/webpage/public/contao-manager.phar.php composer install --no-dev --no-progress --no-ansi --no-interaction --optimize-autoloader Installing dependencies from lock file Verifying lock file contents can be installed on current platform. Nothing to install, update or remove Package doctrine/annotations is abandoned, you should avoid using it. No replacement was suggested. Generating optimized autoload files contao/manager-plugin: Dumping generated plugins file... contao/manager-plugin: ...done dumping generated plugins file 129 packages you are using are looking for funding. Use the `composer fund` command to find out more! > @php vendor/bin/contao-setup In DoctrineExtension.php line 1634: The annotation driver is only available in doctrine/orm v2. Script @php vendor/bin/contao-setup handling the post-install-cmd event returned with error code 1 # Process terminated with exit code 1 # Result: General error ##################### In DoctrineExtension.php line 1634: The annotation driver is only available in doctrine/orm v2.

Du hast vermutliche eine Extension oder eigene Anpassung, die mit Symfony 7 inkompatibel ist.

Ich habe eine Extension gefunden, die wohl nicht mit Symfony 7 inkompatibel ist, und habe sie gelöscht. Jetzt komme ich wenigstens wieder ins Backend.

Ein Update ist aber nicht möglich. Ich habe versucht, nur ein Composer-Update durchzuführen, da erscheint wieder die Fehlermeldung.

Was das wohl sagen mag?

Code:

In CheckExceptionOnInvalidReferenceBehaviorPass.php line 116: The service "doctrine.orm.default_annotation_metadata_driver" has a depende ncy on a non-existent service "annotation_reader".

Wo ist jetzt mein Beitrag wegen der tl_log? Ich habe ihn wohl nicht abgeschickt.

Zitat:

Zitat von Birden

Ich habe eine Extension gefunden, die wohl nicht mit Symfony 7 inkompatibel ist, und habe sie gelöscht. Jetzt komme ich wenigstens wieder ins Backend.

Ein Update ist aber nicht möglich. Ich habe versucht, nur ein Composer-Update durchzuführen, da erscheint wieder die Fehlermeldung.

Was das wohl sagen mag?

Code:

In CheckExceptionOnInvalidReferenceBehaviorPass.php line 116: The service "doctrine.orm.default_annotation_metadata_driver" has a depende ncy on a non-existent service "annotation_reader".

Das ist die selbe Fehlermeldung wie vorhin. Du wirst also immer noch eine Erweiterung haben, die nicht mit Symfony 7 kompatibel ist.
Es wäre hilfreich die composer.json zu posten

Zitat:

Zitat von Birden

Wo ist jetzt mein Beitrag wegen der tl_log? Ich habe ihn wohl nicht abgeschickt.

Der wäre hier:
https://community.contao.org/de/show...-gro%C3%9F-ist

Die sieht so aus:

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": { "con4gis/maps": "^10.0", "contao/conflicts": "*@dev", "contao/listing-bundle": "5.5.*", "contao/manager-bundle": "5.5.*", "contao/news-bundle": "5.5.*", "madeyourday/contao-rocksolid-columns": "^2.1", "madeyourday/contao-rocksolid-custom-elements": "^2.4", "madeyourday/contao-rocksolid-icon-picker": "^2.1", "madeyourday/contao-rocksolid-mega-menu": "^2.2", "madeyourday/contao-rocksolid-slider": "^2.2", "madeyourday/contao-rocksolid-theme-assistant": "^2.1" }, "config": { "allow-plugins": { "composer/package-versions-deprecated": true, "contao-community-alliance/composer-plugin": true, "contao-components/installer": true, "contao/manager-plugin": true, "php-http/discovery": false } }, "extra": { "contao-component-dir": "assets", "public-dir": "public" }, "scripts": { "post-install-cmd": [ "@php vendor/bin/contao-setup" ], "post-update-cmd": [ "@php vendor/bin/contao-setup" ] } }

Siehe oben - aktualisiere auf Contao 5.6.

Da bekomme ich dann wieder diese Fehlermeldung:

Code:

$ /bin/php83 -q -dmax_execution_time=0 -dmemory_limit=-1 -ddisplay_errors=0 -ddisplay_startup_errors=0 -derror_reporting=0 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /www/htdocs/w7itrd56/webpage/public/contao-manager.phar.php composer require contao/manager-bundle=5.6.* contao/news-bundle=5.6.* contao/listing-bundle=5.6.* --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction /www/htdocs/w7itrd56/webpage/composer.json has been updated # Process terminated with exit code 0 # Result: OK > Resolving dependencies using Composer Cloud v3.8.2 [7.5MiB/0.22s] Loading composer repositories with package information [82.9MiB/13.52s] Updating dependencies [29.1MiB/14.87s] Lock file operations: 2 installs, 74 updates, 6 removals [29.1MiB/14.88s] - Removing doctrine/cache (2.2.0) [29.1MiB/14.88s] - Removing doctrine/common (3.5.0) [29.1MiB/14.88s] - Removing symfony/polyfill-iconv (v1.33.0) [29.1MiB/14.88s] - Removing symfony/polyfill-php72 (v1.31.0) [29.1MiB/14.88s] - Removing voku/portable-ascii (2.0.3) [29.1MiB/14.88s] - Removing voku/portable-utf8 (6.0.13) [29.1MiB/14.89s] - Upgrading cmsig/seal (0.6.1 => 0.12.3) [29.1MiB/14.89s] - Upgrading cmsig/seal-loupe-adapter (0.6.1 => 0.12.2) [29.1MiB/14.89s] - Upgrading cmsig/seal-symfony-bundle (0.6.1 => 0.12.2) [29.1MiB/14.89s] - Upgrading contao-components/ace (1.43.3 => 1.43.4) [29.1MiB/14.89s] - Upgrading contao-components/altcha (1.5.1 => 2.2.4) [29.1MiB/14.89s] - Upgrading contao-components/simplemodal (3.0.3 => 3.0.4) [29.1MiB/14.89s] - Upgrading contao-components/swiper (11.2.10 => 12.0.3) [29.1MiB/14.89s] - Upgrading contao-components/tinymce4 (7.9.1 => 8.2.0) [29.1MiB/14.89s] - Upgrading contao/core-bundle (5.5.16 => 5.6.4) [29.1MiB/14.89s] - Upgrading contao/listing-bundle (5.5.16 => 5.6.4) [29.1MiB/14.89s] - Upgrading contao/manager-bundle (5.5.16 => 5.6.4) [29.1MiB/14.89s] - Upgrading contao/news-bundle (5.5.16 => 5.6.4) [29.1MiB/14.89s] - Upgrading dasprid/enum (1.0.6 => 1.0.7) [29.1MiB/14.89s] - Upgrading doctrine/collections (2.3.0 => 2.4.0) [29.1MiB/14.89s] - Upgrading doctrine/dbal (3.10.2 => 4.3.4) [29.1MiB/14.89s] - Upgrading doctrine/doctrine-bundle (2.16.1 => 2.18.0) [29.1MiB/14.89s] - Upgrading doctrine/orm (2.20.6 => 3.5.3) [29.1MiB/14.90s] - Upgrading doctrine/persistence (3.4.0 => 3.4.3) [29.1MiB/14.90s] - Upgrading doctrine/sql-formatter (1.5.2 => 1.5.3) [29.1MiB/14.90s] - Locking joomla/string (4.0.0) [29.1MiB/14.90s] - Upgrading lcobucci/clock (3.3.1 => 3.5.0) [29.1MiB/14.90s] - Upgrading lcobucci/jwt (5.5.0 => 5.6.0) [29.1MiB/14.90s] - Upgrading league/flysystem (3.30.0 => 3.30.1) [29.1MiB/14.90s] - Upgrading league/flysystem-bundle (3.5.0 => 3.6.0) [29.1MiB/14.90s] - Upgrading loupe/loupe (0.9.5 => 0.12.16) [29.1MiB/14.90s] - Locking loupe/matcher (0.2.0) [29.1MiB/14.90s] - Upgrading mjaschen/phpgeo (4.2.1 => 6.0.0) [29.1MiB/14.90s] - Upgrading nelmio/cors-bundle (2.5.0 => 2.6.0) [29.1MiB/14.90s] - Upgrading nelmio/security-bundle (v3.5.1 => v3.6.0) [29.1MiB/14.90s] - Upgrading nette/schema (v1.3.2 => v1.3.3) [29.1MiB/14.90s] - Upgrading nikic/php-parser (v5.6.1 => v5.6.2) [29.1MiB/14.90s] - Upgrading nitotm/efficient-language-detector (v2.1.2 => v3.0.0) [29.1MiB/14.90s] - Upgrading paragonie/constant_time_encoding (v2.7.0 => v3.1.3) [29.1MiB/14.90s] - Upgrading php-feed-io/feed-io (v6.1.1 => v6.1.2) [29.1MiB/14.90s] - Upgrading simplepie/simplepie (1.8.1 => 1.9.0) [29.1MiB/14.91s] - Upgrading spomky-labs/pki-framework (1.3.0 => 1.4.0) [29.1MiB/14.91s] - Upgrading symfony/cache (v7.3.2 => v7.3.5) [29.1MiB/14.91s] - Upgrading symfony/config (v7.3.2 => v7.3.4) [29.1MiB/14.91s] - Upgrading symfony/console (v7.3.3 => v7.3.5) [29.1MiB/14.91s] - Upgrading symfony/debug-bundle (v7.3.0 => v7.3.5) [29.1MiB/14.91s] - Upgrading symfony/dependency-injection (v7.3.3 => v7.3.4) [29.1MiB/14.91s] - Upgrading symfony/doctrine-bridge (v7.3.3 => v7.3.5) [29.1MiB/14.91s] - Upgrading symfony/doctrine-messenger (v7.3.3 => v7.3.4) [29.1MiB/14.91s] - Upgrading symfony/error-handler (v7.3.2 => v7.3.4) [29.1MiB/14.91s] - Upgrading symfony/finder (v7.3.2 => v7.3.5) [29.1MiB/14.91s] - Upgrading symfony/framework-bundle (v7.3.3 => v7.3.5) [29.1MiB/14.92s] - Upgrading symfony/http-client (v6.4.25 => v7.3.4) [29.1MiB/14.92s] - Upgrading symfony/http-foundation (v7.3.3 => v7.3.5) [29.1MiB/14.92s] - Upgrading symfony/http-kernel (v7.3.3 => v7.3.5) [29.1MiB/14.92s] - Upgrading symfony/intl (v7.3.3 => v7.3.5) [29.1MiB/14.92s] - Upgrading symfony/lock (v7.3.2 => v7.3.4) [29.1MiB/14.92s] - Upgrading symfony/mailer (v7.3.3 => v7.3.5) [29.1MiB/14.92s] - Upgrading symfony/mime (v7.3.2 => v7.3.4) [29.1MiB/14.92s] - Upgrading symfony/monolog-bridge (v7.3.3 => v7.3.5) [29.1MiB/14.93s] - Upgrading symfony/process (v7.3.3 => v7.3.4) [29.1MiB/14.93s] - Upgrading symfony/property-info (v7.3.1 => v7.3.5) [29.1MiB/14.93s] - Upgrading symfony/routing (v7.3.2 => v7.3.4) [29.1MiB/14.93s] - Upgrading symfony/security-bundle (v7.3.3 => v7.3.4) [29.1MiB/14.93s] - Upgrading symfony/security-core (v7.3.3 => v7.3.5) [29.1MiB/14.93s] - Upgrading symfony/security-http (v7.3.3 => v7.3.5) [29.1MiB/14.93s] - Upgrading symfony/serializer (v7.3.3 => v7.3.5) [29.1MiB/14.93s] - Upgrading symfony/string (v7.3.3 => v7.3.4) [29.1MiB/14.93s] - Upgrading symfony/translation (v7.3.3 => v7.3.4) [29.1MiB/14.93s] - Upgrading symfony/twig-bundle (v7.3.2 => v7.3.4) [29.1MiB/14.93s] - Upgrading symfony/type-info (v7.3.3 => v7.3.5) [29.1MiB/14.93s] - Upgrading symfony/validator (v7.3.3 => v7.3.5) [29.1MiB/14.93s] - Upgrading symfony/var-dumper (v7.3.3 => v7.3.5) [29.1MiB/14.93s] - Upgrading symfony/var-exporter (v7.3.3 => v7.3.4) [29.1MiB/14.93s] - Upgrading symfony/web-profiler-bundle (v7.3.3 => v7.3.5) [29.1MiB/14.93s] - Upgrading symfony/yaml (v7.3.3 => v7.3.5) [29.1MiB/14.94s] - Upgrading terminal42/escargot (1.6.2 => 1.6.3) [29.1MiB/14.94s] - Upgrading twig/extra-bundle (v3.21.0 => v3.22.0) [29.1MiB/14.94s] - Upgrading twig/string-extra (v3.21.0 => v3.22.0) [29.1MiB/14.94s] - Upgrading twig/twig (v3.21.1 => v3.22.0) [29.1MiB/14.94s] - Upgrading wamania/php-stemmer (v3.0.1 => v4.0.0) [29.1MiB/14.94s] - Upgrading webmozart/assert (1.11.0 => 1.12.1) [28.2MiB/14.95s] Writing lock file [17.0MiB/15.00s] <warning>Package doctrine/annotations is abandoned, you should avoid using it. No replacement was suggested.</warning> [17.2MiB/15.26s] No security vulnerability advisories found. [17.7MiB/15.27s] Memory usage: 17.74MB (peak: 195.28MB), time: 15.27s. [17.7MiB/15.27s] Finished Composer Cloud resolving. # Job ID FBBgNr3Vj5akgAzzRj14asKffQdjFyk5BuPopBCetFTWkWhMONPy3hDCD6LRH6HFOSZozdXrvpU3fMma6pIdcK5JeMF8YNMo6nPXZ completed in 12 seconds # Memory usage: 17.74MB (peak: 195.28MB), time: 15.27s. $ /bin/php83 -q -dmax_execution_time=0 -dmemory_limit=-1 -ddisplay_errors=0 -ddisplay_startup_errors=0 -derror_reporting=0 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /www/htdocs/w7itrd56/webpage/public/contao-manager.phar.php composer install --no-dev --no-progress --no-ansi --no-interaction --optimize-autoloader Installing dependencies from lock file Verifying lock file contents can be installed on current platform. Nothing to install, update or remove Package doctrine/annotations is abandoned, you should avoid using it. No replacement was suggested. Generating optimized autoload files contao/manager-plugin: Dumping generated plugins file... contao/manager-plugin: ...done dumping generated plugins file 126 packages you are using are looking for funding. Use the `composer fund` command to find out more! > @php vendor/bin/contao-setup In DoctrineExtension.php line 1634: The annotation driver is only available in doctrine/orm v2. Script @php vendor/bin/contao-setup handling the post-install-cmd event returned with error code 1 # Process terminated with exit code 1 # Result: General error

Für eine schnelle Fehlerbehebung könntest du einen Conflict auf Symfony 7 setzen, ansonsten würde ein verbose composer update helfen um den Fehler besser eingrenzen zu können.

Zitat:

Zitat von Birden

Da bekomme ich dann wieder diese Fehlermeldung:

Dann gilt wieder diese Aussage von vorhin:

Zitat:

Zitat von Spooky

Du hast vermutliche eine Extension oder eigene Anpassung, die mit Symfony 7 inkompatibel ist.

Mit der oben angegebenen composer.json und entsprechender Aktualisierung auf Contao 5.6 kann ich Contao über den Manager unter XAMPP ohne Fehler installieren.
Es existieren nur einige gleichlautende Warnings

Code:

[WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot have an empty name.

Liste der Anhänge anzeigen (Anzahl: 1)

Jetzt war es plötzlich wieder möglich, die Version 5.5 zu aktualisieren.

Als ich dann auf Version 5.6 updaten wollte, erschien eine veränderte Fehlermeldung. Aufgrund dessen setzte ich ein dbal conflict. Jetzt bin ich auf Version 5.6, aber vier DB-Aktualisierung werden nicht übernommen.

Anhang 28139

Klicke ich da auf weiter, werden sie wieder als nicht aktualisiert angezeigt.

Wenn ich den dbal conflict raus nehme und das Coposer Update ausführe bekomm ich folgende Fehlermeldung:

Code:

> Resolving dependencies using Composer Cloud v3.8.2 [7.4MiB/0.20s] Loading composer repositories with package information [82.8MiB/12.70s] Updating dependencies [29.0MiB/14.05s] Lock file operations: 0 installs, 1 update, 0 removals [29.0MiB/14.06s] - Upgrading doctrine/dbal (3.10.3 => 4.3.4) [28.2MiB/14.07s] Writing lock file [16.9MiB/14.11s] Package doctrine/annotations is abandoned, you should avoid using it. No replacement was suggested. [17.1MiB/14.42s] No security vulnerability advisories found. [17.7MiB/14.42s] Memory usage: 17.67MB (peak: 196.08MB), time: 14.44s. [17.7MiB/14.43s] Finished Composer Cloud resolving. # Job ID jcQHGNBiYXBNrKe7S0UFFiHK2OADx8G7UYqEW6Npe69Zfw84gtaevDu2WyDhg0ws0bYDPr3S5uyQCv1E completed in 12 seconds # Memory usage: 17.67MB (peak: 196.08MB), time: 14.44s. $ /bin/php83 -q -dmax_execution_time=0 -dmemory_limit=-1 -ddisplay_errors=0 -ddisplay_startup_errors=0 -derror_reporting=0 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /www/htdocs/w7itrd56/webpage/public/contao-manager.phar.php composer install --no-dev --no-progress --no-ansi --no-interaction --optimize-autoloader Installing dependencies from lock file Verifying lock file contents can be installed on current platform. Nothing to install, update or remove Package doctrine/annotations is abandoned, you should avoid using it. No replacement was suggested. Generating optimized autoload files contao/manager-plugin: Dumping generated plugins file... contao/manager-plugin: ...done dumping generated plugins file 126 packages you are using are looking for funding. Use the `composer fund` command to find out more! > @php vendor/bin/contao-setup [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. Added the bin/console file. Added the public/index.php file. Added the public/preview.php file. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. Trying to install assets as relative symbolic links. --- ------------------------------- ------------------ Bundle Method / Error --- ------------------------------- ------------------ ? ContaoCoreBundle relative symlink ? RockSolidCustomElementsBundle relative symlink ? MultiColumnWizardBundle relative symlink ? RockSolidColumnsBundle relative symlink ? ContaoNewsBundle relative symlink ? RockSolidMegaMenuBundle relative symlink ? RockSolidThemeAssistantBundle relative symlink ? con4gisCoreBundle relative symlink ? RockSolidIconPickerBundle relative symlink ? con4gisMapsBundle relative symlink ? RockSolidSliderBundle relative symlink --- ------------------------------- ------------------ [OK] All assets were successfully installed. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. --- ------------------------------------------- -------------------------------------------------- Symlink Target / Error --- ------------------------------------------- -------------------------------------------------- ? public/files/tao files/tao ? public/files/buchloze files/buchloze ? system/themes/flexible vendor/contao/core-bundle/contao/themes/flexible ? public/assets assets ? public/system/themes system/themes ? system/logs var/logs ? public/vendor/scrivo/highlight_php/styles vendor/scrivo/highlight.php/styles --- ------------------------------------------- -------------------------------------------------- [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. // Clearing the cache for the prod environment with debug false [OK] Cache for the "prod" environment (debug=false) was successfully cleared. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. // Clearing the cache for the dev environment with debug true [OK] Cache for the "dev" environment (debug=true) was successfully cleared. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. // Warming up the cache for the prod environment with debug false try 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}] 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}] 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}] 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}] 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}] 01:28:28 CRITICAL [console] Error thrown while running command "cache:warmup --env=prod --no-ansi". Message: "Unknown column type "array" requested. Any Doctrine type that you use has to be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a list of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If this error occurs during database introspection then you might have forgotten to register all database types for a Doctrine Type. Use AbstractPlatform#registerDoctrineTypeMapping() or have your custom types implement Type#getMappedDatabaseTypes(). If the type name is empty you might have a problem with the cache or forgot some mapping information." ["exception" => Doctrine\DBAL\Types\Exception\UnknownColumnType { …},"command" => "cache:warmup --env=prod --no-ansi","message" => "Unknown column type "array" requested. Any Doctrine type that you use has to be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a list of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If this error occurs during database introspection then you might have forgotten to register all database types for a Doctrine Type. Use AbstractPlatform#registerDoctrineTypeMapping() or have your custom types implement Type#getMappedDatabaseTypes(). If the type name is empty you might have a problem with the cache or forgot some mapping information."] In UnknownColumnType.php line 15: Unknown column type "array" requested. Any Doctrine type that you use has t o be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a li st of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If this error occurs during database introspection then you might have forgot ten to register all database types for a Doctrine Type. Use AbstractPlatfor m#registerDoctrineTypeMapping() or have your custom types implement Type#ge tMappedDatabaseTypes(). If the type name is empty you might have a problem with the cache or forgot some mapping information. cache:warmup [--no-optional-warmers] 01:28:28 CRITICAL [console] An error occurred while using the console. Message: "An error occurred while executing the "/usr/bin/php83 -dmemory_limit=-1 /www/htdocs/w7itrd56/webpage/vendor/contao/manager-bundle/bin/contao-console cache:warmup --env=prod --no-ansi" command: [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. try 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}] 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}] 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}] 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}] 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}] 01:28:28 CRITICAL [console] Error thrown while running command "cache:warmup --env=prod --no-ansi". Message: "Unknown column type "array" requested. Any Doctrine type that you use has to be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a list of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If this error occurs during database introspection then you might have forgotten to register all database types for a Doctrine Type. Use AbstractPlatform#registerDoctrineTypeMapping() or have your custom types implement Type#getMappedDatabaseTypes(). If the type name is empty you might have a problem with the cache or forgot some mapping information." ["exception" => Doctrine\DBAL\Types\Exception\UnknownColumnType { …},"command" => "cache:warmup --env=prod --no-ansi","message" => "Unknown column type "array" requested. Any Doctrine type that you use has to be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a list of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If this error occurs during database introspection then you might have forgotten to register all database types for a Doctrine Type. Use AbstractPlatform#registerDoctrineTypeMapping() or have your custom types implement Type#getMappedDatabaseTypes(). If the type name is empty you might have a problem with the cache or forgot some mapping information."] In UnknownColumnType.php line 15: Unknown column type "array" requested. Any Doctrine type that you use has t o be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a li st of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If this error occurs during database introspection then you might have forgot ten to register all database types for a Doctrine Type. Use AbstractPlatfor m#registerDoctrineTypeMapping() or have your custom types implement Type#ge tMappedDatabaseTypes(). If the type name is empty you might have a problem with the cache or forgot some mapping information. cache:warmup [--no-optional-warmers] " ["exception" => RuntimeException { …},"message" => """ An error occurred while executing the "/usr/bin/php83 -dmemory_limit=-1 /www/htdocs/w7itrd56/webpage/vendor/contao/manager-bundle/bin/contao-console cache:warmup --env=prod --no-ansi" command: \n [WARNING] Some commands could not be registered: \n \n \n The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha \n ve an empty name. \n \n \n \n [WARNING] Some commands could not be registered: \n \n \n The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha \n ve an empty name. \n \n \n try\n 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}]\n 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}]\n 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}]\n 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}]\n 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}]\n 01:28:28 CRITICAL [console] Error thrown while running command "cache:warmup --env=prod --no-ansi". Message: "Unknown column type "array" requested. Any Doctrine type that you use has to be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a list of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If this error occurs during database introspection then you might have forgotten to register all database types for a Doctrine Type. Use AbstractPlatform#registerDoctrineTypeMapping() or have your custom types implement Type#getMappedDatabaseTypes(). If the type name is empty you might have a problem with the cache or forgot some mapping information." ["exception" => Doctrine\DBAL\Types\Exception\UnknownColumnType { …},"command" => "cache:warmup --env=prod --no-ansi","message" => "Unknown column type "array" requested. Any Doctrine type that you use has to be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a list of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If this error occurs during database introspection then you might have forgotten to register all database types for a Doctrine Type. Use AbstractPlatform#registerDoctrineTypeMapping() or have your custom types implement Type#getMappedDatabaseTypes(). If the type name is empty you might have a problem with the cache or forgot some mapping information."]\n \n In UnknownColumnType.php line 15:\n \n Unknown column type "array" requested. Any Doctrine type that you use has t \n o be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a li \n st of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If \n this error occurs during database introspection then you might have forgot \n ten to register all database types for a Doctrine Type. Use AbstractPlatfor \n m#registerDoctrineTypeMapping() or have your custom types implement Type#ge \n tMappedDatabaseTypes(). If the type name is empty you might have a problem \n with the cache or forgot some mapping information. \n \n \n cache:warmup [--no-optional-warmers]\n \n """] In ContaoSetupCommand.php line 143: An error occurred while executing the "/usr/bin/php83 -dmemory_limit=-1 /ww w/htdocs/w7itrd56/webpage/vendor/contao/manager-bundle/bin/contao-conso le cache:warmup --env=prod --no-ansi" command: [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. [WARNING] Some commands could not be registered: The command defined in "con4gis\CoreBundle\Command\ImportCommand" cannot ha ve an empty name. try 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}] 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}] 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}] 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}] 01:28:28 ERROR [php] Warning: Undefined array key "admin" ["exception" => ErrorException { …}] 01:28:28 CRITICAL [console] Error thrown while running command "cache:warm up --env=prod --no-ansi". Message: "Unknown column type "array" requested. Any Doctrine type that you use has to be registered with \Doctrine\DBAL\Typ es\Type::addType(). You can get a list of all the known types with \Doctrin e\DBAL\Types\Type::getTypesMap(). If this error occurs during database intr ospection then you might have forgotten to register all database types for a Doctrine Type. Use AbstractPlatform#registerDoctrineTypeMapping() or have your custom types implement Type#getMappedDatabaseTypes(). If the type nam e is empty you might have a problem with the cache or forgot some mapping i nformation." ["exception" => Doctrine\DBAL\Types\Exception\UnknownColumnTyp e { …},"command" => "cache:warmup --env=prod --no-ansi","message" => "Unkno wn column type "array" requested. Any Doctrine type that you use has to be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a list of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If this error occurs during database introspection then you might have forgotten t o register all database types for a Doctrine Type. Use AbstractPlatform#reg isterDoctrineTypeMapping() or have your custom types implement Type#getMapp edDatabaseTypes(). If the type name is empty you might have a problem with the cache or forgot some mapping information."] In UnknownColumnType.php line 15: Unknown column type "array" requested. Any Doctrine type that you use has t o be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a li st of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If this error occurs during database introspection then you might have forg ot ten to register all database types for a Doctrine Type. Use AbstractPlatf or m#registerDoctrineTypeMapping() or have your custom types implement Type# ge tMappedDatabaseTypes(). If the type name is empty you might have a proble m with the cache or forgot some mapping information. cache:warmup [--no-optional-warmers] contao:setup Script @php vendor/bin/contao-setup handling the post-install-cmd event returned with error code 1 # Process terminated with exit code 1 # Result: General error

Die Warnings hatte ich ja auch schon beschrieben.
Genau Deine Fehlermeldung bekomme ich erst, wenn ich con4gis/import dazu installiere.

Also diese von oben

Code:

The annotation driver is only available in doctrine/orm v2.

Mal ganz etwas anderes: Es wäre wirklich schön, wenn Du für Deinen Thread einen passenden Titel vergeben würdest (vielleicht die Fehlermeldung). Dann wird es für andere mit gleichen Fehlern leichter, den Thread zu finden.

Downgrade doch einfach auf eine LTS Version wie z.B. Contao 5.3? Oder geht das auch nicht?

Ich werde nie verstehen warum Leute auf diese Zwischenversionen gehen, die nur 6 Monaten supportet werden. Das ist total sinnfrei, da es eben total viele Probleme und Konflikte geben kann wie man ja aktuell hier wieder sieht.
Damit will ich nicht die komplette Versionierungslogik von Contao in Frage stellen. Diese Versionen ergeben schon Sinn für die Entwickler und andere Profis, aber ich glaube nicht, dass man das produktiv einsetzen sollte. Ich glaube Contao 3.4 war die letzte nicht-LTS, die ich produktiv installiert habe. Ich nutze Contao seit 2008 und hab schon so gut wie alles gesehen und erlebt.
Aber naja, muss ja jeder selbst wissen ;)

Wenn du neue Features willst, nimmst du natürlich die neueste Contao Version.

Ist die Frage, ob man als Hobbyanwender tatsächlich die neuesten Features benötigt oder mit einer LTS besser dran ist. Muss man abwägen.
Ich gehöre ja auch eher zur Version LTS für produktive Seiten, aber für neue Features setze ich eben die neueste Version ein,

Unabhängig davon: Downgrades (der Datenbank) werden grundsätzlich nicht unterstützt und könnten daher zu Problemen führen.

Zitat:

Zitat von Spooky

Unabhängig davon: Downgrades (der Datenbank) werden grundsätzlich nicht unterstützt und könnten daher zu Problemen führen.

Okay, danke für die Info. War mir gar nicht so bewusst bisher. Ich hatte nie Probleme gehabt bis dato, allerdings waren die Downgrade-Sprünge nie sehr groß.
Ist denn so ein krasser Unterschied zwischen 5.3 und 5.6 hinsichtlich der DB und wenn ja bei welchen Feldern bzw. Feldtypen?
Ist das im Endeffekt für ihn nicht trotzdem der schnellere Weg als jetzt zwanghaft 5.6 weiter zu erzwingen?

Zitat:

Zitat von mlweb

Ist die Frage, ob man als Hobbyanwender tatsächlich die neuesten Features benötigt oder mit einer LTS besser dran ist. Muss man abwägen.
Ich gehöre ja auch eher zur Version LTS für produktive Seiten, aber für neue Features setze ich eben die neueste Version ein,

Stimmt. Bei wieviel Prozent deiner Projekte setzt du denn dann die Nicht-LTS ein?
Für mich persönlich waren die Features der Zwischenversionen seit Contao 4.0 nie wirklich so krass überzeugend, dass ich jetzt unbedingt darauf setzen muss, bevor die nächste LTS da ist.
Aber das liegt sicher auch daran, dass ich erstens gar keine Zeit habe mich überhaupt im Detail damit zu beschäftigen, was z.B. an Version 5.0 bis 5.6 so viel besser ist als bei 4.13.
Und zweitens kann ich mir zur Not auch anderweitig behelfen, wenn es irgendwas in irgendeiner Version nicht gibt :)

OffTopic:
@Stranger
Da ich mir immer die Zeit nehme mich mit den neuen Versionen und ihren Featuren zur beschäftigen - setze ich immer dann auf die neueste Version, wenn ich/der Kunde ein solches Feature benötigt. Außerdem sehr konsequent bei Neuprojekten ca. 3 - 4 Monate bevor die nächste LTS rauskommt (vorausgesetzt es gibt kein Problem mit irgendeiner Erweiterung). Dann ist im Projekt das Update auf die folgende LTS schon eingepreist.