Contao-Community - Installation / Update

Installation von Theme Canvas+ misslingt: Ungültiges Token

mainmeyer — Fri, 31 Jul 2026 11:16:36 GMT

Nach 12 Jahren Stillstand aktualisiere ich meine Webseite und habe lokal auf meinem Rechner eine WAMP64-Installation aufgesetzt, die einwandfrei funktiioniert: php8.3.28, mysql8.4.7. Meine Contao-Version ist 8.7.9, Contao-Manager 1.10.16.

Beim Installieren des Themes "Canvas+" taucht die Fehlermeldung "Ungültiges Token" auf. Die Installation versuche ich über die Importieren-Funktion.

Ich bin kein Fachmann. Wer kann helfen?

Marcel

Java Script Blocker

hendele — Thu, 30 Jul 2026 09:32:36 GMT

Hallo gemeinde.
ich bekomme seit einigen Tagen folgede Meldung (siehe Screenshot).
ich habe Version 5.3.48 installiert und arbeite mit dem Firefox (neuste Version).

Ich kann die Einstellungen nicht finden, wo ich eben diesen Javascript Blocker abstellen kann.

Danke
Erwin Hendel
Bildschirmfoto 2026-07-30 um 11.31.35.png

Angehängte Grafiken

Bildschirmfoto 2026-07-30 um 11.31.35.png (96,8 KB)

Störung im CONTAO Manager 1.10.16

mv-soft — Wed, 29 Jul 2026 11:44:32 GMT

Hallo,

gibt es eine Störung bei Nutzung des CONTAO- Managers ? Heute Viormittag konnte ich noch damit fehlerfrei arbeiten. Diese Fehlermeldung kommt nach der Systemprüfung:

Code:

Konnte keine Ergebnisse laden.



Prüfe deine Internet-Verbindung und deaktiviere alle JavaScript-Blocker.

Vielen Dank für Hinweise.

5.3.x Update CM: Datei korrupt?

scroll — Thu, 23 Jul 2026 07:08:05 GMT

Hallo,
in einer Installation kann ich das Update für den CM von 1.10.14 auf 1.10.16 nicht durchführen.

Fehlermeldung:
update-cm.png

Was ist das für ein Problem und wie kann ich das lösen?

Leider habe ich keinen Konsolenzugriff.

Gruß Michael

Angehängte Grafiken

update-cm.png (10,5 KB)

Problem mit contao Manager 1.10.16

JamesBolivar — Tue, 21 Jul 2026 09:32:08 GMT

Hallo,
nach dem sich der Contao Manager 1.10.16 installiert hat, verlieren die Contao 5.3.x Webseiten ihre Datenbank zuordnungen.
Diese lässt sich auch nicht wieder herstellen, da die Datei: .env.local keine Inhalte ausser dem APP_SECRET enthält.

Das ist jetzt ein echtes Problem, den jede Seite die ich anfasse geht sozusagen den Bach runter. Irgendeine Idee, was da schief geht?

Danke!

Gruß Chris

5.7.x Drei Fehler nach dem Upgrade von Version 5.3 auf 5.7.9

Achim H. — Sun, 19 Jul 2026 16:53:44 GMT

Der Sommer macht heute ein wenig Pause und ich mache ein wenig Updates.

Bei meinen Websites ergeben sich nach dem Upgrade von 5.3.48 auf 5.7.9. folgende Fragen:

1.
Die Schriftarten werden nicht (immer) geladen, obwohl die externen Stylesheets eingebunden und alle Dateien vorhanden sind.

2.
Bei Downloads (PDF) werden keine Vorschaubilder mehr angezeigt, sondern der PDF-Platzhalter.

3.
Beim Klick auf Bilder, die beim Klicken als Popup größer eingeblendet werden sollen, passiert nichts. (Über Kontextmenü > in neuenm Tag öffnen klappt's, ist aber nicht gewollt, und an den Browser-Einstellungen habe ich nichts geändert).

Ein Beispiel:

Version 5.3:
https://a-klarinette.de/daskli
Version_5-3.png

Version 5.7:
https://contao5.a-klarinette.de/daskli
Version_5-7.png

Angehängte Grafiken

Version_5-3.png (250,3 KB)
Version_5-7.png (618,3 KB)

5.3.x Vorschaumodus Fehlermeldung

captain fruit — Wed, 15 Jul 2026 07:35:29 GMT

Hallo,

bei einer Installation funktioniert der Vorschaumodus nicht. Die Seite direkt aufrufen geht aber.
Fehlermeldung:

Zitat:

Diese Website kann keine sichere Verbindung bereitstellen
website.wpw.tax verwendet ein nicht unterstütztes Protokoll.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH

Beim Hoster (Strato) ist ein SSL Zertifikat vergeben, beim Startpunkt der Website ist https eingestellt, Cache geleert...

Hat jemand eine Idee?

Backup-Lösung (Dateien und DB) für Contao-Installationen auf Shared Hosting

Balduin — Fri, 10 Jul 2026 09:54:13 GMT

Ich habe ein kleines Backup-Script veröffentlicht, das Contao-Dateien und Datenbank sichert. Es ist auch ohne SSH-Zugang nutzbar und lässt sich per PHP-Trigger mit URL-Cronjob automatisieren:

https://github.com/elektrischerwalfi...p-shell-script

Das Script läuft serverseitig, unabhängig von Contao-Extensions und Backend.

Kurzüberblick:

• Contao 4.x und 5.x (Credentials aus parameters.yml bzw. .env.local)
• Datei-Backup per tar mit konfigurierbaren Excludes
• DB-Backup per mysqldump
• automatische Aufbewahrung älterer Backups (MAX_BACKUPS)
• Logging und optionale E-Mail bei Fehlern
• für Hoster ohne SSH: Ausführung per PHP-Trigger und URL-Cronjob möglich

Getestet auf all-inkl und IONOS.

Feedback und Issues sind willkommen — besonders von anderen Shared-Hosting-Setups.

5.7.x Bei News Autor deaktivieren

hpt — Tue, 07 Jul 2026 19:42:24 GMT

Hallo,

ich habe gerade eine komplette Neuinstallation mit 5.7. durchgeführt. D.h. nur die eigenen Files dazukopiert, der Rest ist komplett neu vom Manager!
http://chor-eintracht-hugstetten.de.....kasserver.com

Bei den News siehe Aktuelles wollte ich den Autor deaktivieren.
Wie bei 5.7. jetzt möglich im Backend, Template Studio, für die news_.... eigene twig Files erstellt, den betreffenden Bereich eingefügt und Autor herausgelöscht.

Code:

    {% block info %}

        {{ date }}


    {% endblock %}

Original:

Code:

{% block info %}

        {{ date }} {{ author }}


    {% endblock %}

Warum greift die Anpassung nicht? Cache, Prod.Cache, Composer Cache usw. gelöscht / neu aufgebaut
Muss ich irgendwo noch was aktivieren?

Update von Contao 5.3 auf 5,7

ok99 — Mon, 06 Jul 2026 16:08:16 GMT

Hallo,

ich habe schon so einige 5.3er auf 5.7 gebracht - eigentlich ohne Probleme, aber jetzt hakt es irgendwie:

PHP 8.3
Server: Hetzner

Contao Manager bricht ab mit folgender Fehlermeldung:

Code:

> Resolving dependencies using Composer Cloud v3.10.1 [7.2MiB/0.34s] Loading composer repositories with package information [89.6MiB/20.33s] Updating dependencies [174.3MiB/21.47s] Your requirements could not be resolved to an installable set of packages. [174.3MiB/21.47s] Problem 1 - ext-redis is present at version 6.0.2.0 and cannot be modified by Composer - Root composer.json requires contao/manager-bundle 5.7.* -> satisfiable by contao/manager-bundle[5.7.0, ..., 5.7.8]. - contao/manager-bundle[5.7.0, ..., 5.7.8] require symfony/cache ^7.4 -> satisfiable by symfony/cache[v7.4.0, ..., v7.4.14]. - symfony/cache[v7.4.0, ..., v7.4.14] conflict with ext-redis <6.1. To enable extensions, verify that they are enabled in your .ini files: - /etc/php/8.4/cli/php.ini - /etc/php/8.4/cli/conf.d/10-mysqlnd.ini - /etc/php/8.4/cli/conf.d/10-opcache.ini - /etc/php/8.4/cli/conf.d/10-pdo.ini - /etc/php/8.4/cli/conf.d/15-xml.ini - /etc/php/8.4/cli/conf.d/20-bcmath.ini - /etc/php/8.4/cli/conf.d/20-bz2.ini - /etc/php/8.4/cli/conf.d/20-calendar.ini - /etc/php/8.4/cli/conf.d/20-ctype.ini - /etc/php/8.4/cli/conf.d/20-curl.ini - /etc/php/8.4/cli/conf.d/20-dba.ini - /etc/php/8.4/cli/conf.d/20-dom.ini - /etc/php/8.4/cli/conf.d/20-exif.ini - /etc/php/8.4/cli/conf.d/20-ffi.ini - /etc/php/8.4/cli/conf.d/20-fileinfo.ini - /etc/php/8.4/cli/conf.d/20-ftp.ini - /etc/php/8.4/cli/conf.d/20-gd.ini - /etc/php/8.4/cli/conf.d/20-gettext.ini - /etc/php/8.4/cli/conf.d/20-gmp.ini - /etc/php/8.4/cli/conf.d/20-iconv.ini - /etc/php/8.4/cli/conf.d/20-igbinary.ini - /etc/php/8.4/cli/conf.d/20-imagick.ini - /etc/php/8.4/cli/conf.d/20-intl.ini - /etc/php/8.4/cli/conf.d/20-ldap.ini - /etc/php/8.4/cli/conf.d/20-mbstring.ini - /etc/php/8.4/cli/conf.d/20-mysqli.ini - /etc/php/8.4/cli/conf.d/20-pdo_mysql.ini - /etc/php/8.4/cli/conf.d/20-pdo_sqlite.ini - /etc/php/8.4/cli/conf.d/20-phar.ini - /etc/php/8.4/cli/conf.d/20-posix.ini - /etc/php/8.4/cli/conf.d/20-readline.ini - /etc/php/8.4/cli/conf.d/20-shmop.ini - /etc/php/8.4/cli/conf.d/20-simplexml.ini - /etc/php/8.4/cli/conf.d/20-soap.ini - /etc/php/8.4/cli/conf.d/20-sockets.ini - /etc/php/8.4/cli/conf.d/20-sqlite3.ini - /etc/php/8.4/cli/conf.d/20-sysvmsg.ini - /etc/php/8.4/cli/conf.d/20-sysvsem.ini - /etc/php/8.4/cli/conf.d/20-sysvshm.ini - /etc/php/8.4/cli/conf.d/20-tokenizer.ini - /etc/php/8.4/cli/conf.d/20-xmlreader.ini - /etc/php/8.4/cli/conf.d/20-xmlwriter.ini - /etc/php/8.4/cli/conf.d/20-xsl.ini - /etc/php/8.4/cli/conf.d/20-zip.ini - /etc/php/8.4/cli/conf.d/25-redis.ini - /etc/php/8.4/cli/conf.d/50-serverctl.ini You can also run php --ini in a terminal to see which files are used by PHP in CLI mode. Alternatively, you can run Composer with --ignore-platform-req=ext-redis to temporarily ignore these required extensions. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions. [174.3MiB/21.48s] Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems. [60.3MiB/21.58s] Memory usage: 60.26MB (peak: 178.05MB), time: 21.59s. [60.3MiB/21.58s] Finished Composer Cloud resolving.

Ich denke das Entscheidende ist: symfony/cache 7.4.x conflict with ext-redis < 6.1
Aber ich dachte Contao braucht kein Redis?

Meine composer.json sieht so aus:

Code:

{

  "type": "project",

  "require": {

    "contao/calendar-bundle": "5.7.*",

    "contao/comments-bundle": "5.7.*",

    "contao/conflicts": "*@dev",

    "contao/faq-bundle": "5.7.*",

    "contao/listing-bundle": "5.7.*",

    "contao/manager-bundle": "5.7.*",

    "contao/news-bundle": "5.7.*",

    "contao/newsletter-bundle": "5.7.*",

    "dklemmt/contao_dk_mmenu": "^4.1",

    "madeyourday/contao-rocksolid-slider": "^2.2",

    "oveleon/contao-cookiebar": "^2.2"

  },

  "extra": {

    "public-dir": "public",

    "contao-component-dir": "assets"

  },

  "scripts": {

    "post-install-cmd": [

      "@php vendor/bin/contao-setup"

    ],

    "post-update-cmd": [

      "@php vendor/bin/contao-setup"

    ]

  }

}

Hat da jemand eine Idde?

5.3.x Will Leads 3.1 aktualisieren - lange Liste an Updates - Schlägt fehl

µaTh — Sat, 04 Jul 2026 19:55:52 GMT

Hallo liebe Contao Community,

ich nutze Contao 5.3.40 und u.a. die Leads Extension Version 3.1.3

Nun wollte ich Leads von 3.1.3 auf 3.1.7 updaten und habe im Contao Manager bei Leads ^3.1 eingetragen und mit "Aktualisieren" daneben die Extension für das Update vorgemerkt und dann
"Änderung anwenden". Aus meiner Sicht ist hier nichts spektakuläres dabei.

Nun läuft der Cloud Composer los und verfängt sich in einem Fehler, der dazu führt dass der Reparationsmodus vom Contao Manager startet (und zum glück reparieren kann, so dass Contao wieder funktioniert).

Das ist das Logfile dazu:

Code:

> Resolving dependencies using Composer Cloud v3.10.1



[7.3MiB/0.23s] Loading composer repositories with package information

[98.0MiB/23.37s] Updating dependencies

[30.5MiB/23.81s] Lock file operations: 0 installs, 119 updates, 0 removals

[30.5MiB/23.81s]   - Upgrading codefog/contao-haste (5.2.14 => 5.4.2)

[30.5MiB/23.81s]   - Upgrading composer/ca-bundle (1.5.8 => 1.5.12)

[30.5MiB/23.81s]   - Upgrading composer/pcre (3.3.2 => 3.4.0)

[30.5MiB/23.81s]   - Upgrading contao-components/ace (1.43.3 => 1.44.0)

[30.5MiB/23.81s]   - Upgrading contao-components/contao (9.4.1 => 9.4.2)

[30.5MiB/23.82s]   - Upgrading contao-components/datepicker (3.0.1 => 3.0.3)

[30.5MiB/23.82s]   - Upgrading contao-components/simplemodal (3.0.3 => 3.1.2)

[30.5MiB/23.82s]   - Upgrading contao-components/tristen-tablesort (5.6.0 => 5.7.1)

[30.5MiB/23.82s]   - Upgrading contao/conflicts (dev-main 00029ff => dev-main 12e7b75)

[30.5MiB/23.82s]   - Upgrading contao/image (1.2.3 => 1.2.4)

[30.5MiB/23.82s]   - Upgrading doctrine/annotations (2.0.2 => 2.0.2)

[30.5MiB/23.82s]   - Upgrading doctrine/cache (2.2.0 => 2.2.0)

[30.5MiB/23.82s]   - Upgrading doctrine/collections (2.3.0 => 2.6.0)

[30.5MiB/23.82s]   - Upgrading doctrine/dbal (3.10.2 => 3.10.5)

[30.5MiB/23.82s]   - Upgrading doctrine/deprecations (1.1.5 => 1.1.6)

[30.5MiB/23.82s]   - Upgrading doctrine/doctrine-bundle (2.16.2 => 2.18.3)

[30.5MiB/23.82s]   - Upgrading doctrine/event-manager (2.0.1 => 2.1.1)

[30.5MiB/23.82s]   - Upgrading doctrine/orm (2.20.6 => 2.20.13)

[30.5MiB/23.82s]   - Upgrading doctrine/persistence (3.4.1 => 3.4.5)

[30.5MiB/23.82s]   - Upgrading doctrine/sql-formatter (1.5.2 => 1.5.4)

[30.5MiB/23.82s]   - Upgrading guzzlehttp/promises (2.3.0 => 2.5.0)

[30.5MiB/23.82s]   - Upgrading imagine/imagine (1.5.0 => 1.5.4)

[30.5MiB/23.82s]   - Upgrading knplabs/knp-menu-bundle (v3.6.0 => v3.7.0)

[30.5MiB/23.82s]   - Upgrading knplabs/knp-time-bundle (v2.4.0 => 2.5.0)

[30.5MiB/23.83s]   - Upgrading lcobucci/clock (3.3.1 => 3.5.0)

[30.5MiB/23.83s]   - Upgrading lcobucci/jwt (5.5.0 => 5.6.0)

[30.5MiB/23.83s]   - Upgrading league/commonmark (2.7.1 => 2.8.2)

[30.5MiB/23.83s]   - Upgrading league/flysystem (3.30.0 => 3.35.1)

[30.5MiB/23.83s]   - Upgrading league/flysystem-bundle (3.5.0 => 3.7.0)

[30.5MiB/23.83s]   - Upgrading league/flysystem-local (3.30.0 => 3.31.0)

[30.5MiB/23.83s]   - Upgrading league/uri (7.5.1 => 7.8.1)

[30.5MiB/23.83s]   - Upgrading league/uri-interfaces (7.5.0 => 7.8.1)

[30.5MiB/23.83s]   - Upgrading maennchen/zipstream-php (3.1.2 => 3.2.2)

[30.5MiB/23.83s]   - Upgrading masterminds/html5 (2.10.0 => 2.10.1)

[30.5MiB/23.83s]   - Upgrading menatwork/contao-multicolumnwizard-bundle (3.6.10 => 3.6.16)

[30.5MiB/23.83s]   - Upgrading monolog/monolog (2.10.0 => 2.11.0)

[30.5MiB/23.83s]   - Upgrading nelmio/cors-bundle (2.5.0 => 2.6.1)

[30.5MiB/23.83s]   - Upgrading nelmio/security-bundle (v3.6.0 => v3.9.0)

[30.5MiB/23.83s]   - Upgrading nette/schema (v1.3.2 => v1.3.5)

[30.5MiB/23.83s]   - Upgrading nette/utils (v4.0.8 => v4.1.4)

[30.5MiB/23.83s]   - Upgrading nikic/php-parser (v4.19.4 => v4.19.5)

[30.5MiB/23.83s]   - Upgrading php-feed-io/feed-io (v6.1.2 => V6.4.0)

[30.5MiB/23.83s]   - Upgrading php-http/client-common (2.7.2 => 2.7.3)

[30.5MiB/23.84s]   - Upgrading phpoffice/phpspreadsheet (4.3.1 => 5.8.0)

[30.5MiB/23.84s]   - Upgrading scheb/2fa-backup-code (v7.11.0 => v7.13.1)

[30.5MiB/23.84s]   - Upgrading scheb/2fa-bundle (v7.11.0 => v7.13.1)

[30.5MiB/23.84s]   - Upgrading scheb/2fa-trusted-device (v7.11.0 => v7.13.1)

[30.5MiB/23.84s]   - Upgrading spatie/schema-org (3.23.1 => 3.23.2)

[30.5MiB/23.84s]   - Upgrading spomky-labs/otphp (11.3.0 => 11.5.0)

[30.5MiB/23.84s]   - Upgrading symfony-cmf/routing (3.0.4 => 3.0.5)

[30.5MiB/23.84s]   - Upgrading symfony-cmf/routing-bundle (3.1.1 => 3.2.0)

[30.5MiB/23.84s]   - Upgrading symfony/asset (v6.4.24 => v6.4.34)

[30.5MiB/23.84s]   - Upgrading symfony/cache (v6.4.26 => v6.4.42)

[30.5MiB/23.84s]   - Upgrading symfony/cache-contracts (v3.6.0 => v3.7.1)

[30.5MiB/23.84s]   - Upgrading symfony/clock (v6.4.24 => v6.4.30)

[30.5MiB/23.84s]   - Upgrading symfony/config (v6.4.26 => v6.4.42)

[30.5MiB/23.84s]   - Upgrading symfony/console (v6.4.26 => v6.4.42)

[30.5MiB/23.84s]   - Upgrading symfony/dependency-injection (v6.4.26 => v6.4.42)

[30.5MiB/23.84s]   - Upgrading symfony/deprecation-contracts (v3.6.0 => v3.7.1)

[30.5MiB/23.84s]   - Upgrading symfony/doctrine-bridge (v6.4.26 => v6.4.42)

[30.5MiB/23.85s]   - Upgrading symfony/doctrine-messenger (v6.4.26 => v6.4.42)

[30.5MiB/23.85s]   - Upgrading symfony/dom-crawler (v6.4.25 => v6.4.40)

[30.5MiB/23.85s]   - Upgrading symfony/error-handler (v6.4.26 => v6.4.36)

[30.5MiB/23.85s]   - Upgrading symfony/event-dispatcher (v6.4.25 => v6.4.37)

[30.5MiB/23.85s]   - Upgrading symfony/event-dispatcher-contracts (v3.6.0 => v3.7.1)

[30.5MiB/23.85s]   - Upgrading symfony/expression-language (v6.4.24 => v6.4.42)

[30.5MiB/23.85s]   - Upgrading symfony/filesystem (v6.4.24 => v6.4.39)

[30.5MiB/23.85s]   - Upgrading symfony/finder (v6.4.24 => v6.4.42)

[30.5MiB/23.85s]   - Upgrading symfony/framework-bundle (v6.4.26 => v6.4.42)

[30.5MiB/23.85s]   - Upgrading symfony/html-sanitizer (v6.4.25 => v6.4.41)

[30.5MiB/23.85s]   - Upgrading symfony/http-client (v6.4.26 => v6.4.42)

[30.5MiB/23.85s]   - Upgrading symfony/http-client-contracts (v3.6.0 => v3.7.1)

[30.5MiB/23.85s]   - Upgrading symfony/http-foundation (v6.4.26 => v6.4.42)

[30.5MiB/23.85s]   - Upgrading symfony/http-kernel (v6.4.26 => v6.4.42)

[30.5MiB/23.85s]   - Upgrading symfony/intl (v6.4.26 => v6.4.42)

[30.5MiB/23.85s]   - Upgrading symfony/lock (v7.3.4 => v7.4.14)

[30.5MiB/23.85s]   - Upgrading symfony/mailer (v6.4.26 => v6.4.40)

[30.5MiB/23.85s]   - Upgrading symfony/messenger (v6.4.25 => v6.4.42)

[30.5MiB/23.85s]   - Upgrading symfony/mime (v6.4.26 => v6.4.41)

[30.5MiB/23.86s]   - Upgrading symfony/monolog-bridge (v6.4.26 => v6.4.40)

[30.5MiB/23.86s]   - Upgrading symfony/options-resolver (v6.4.25 => v6.4.30)

[30.5MiB/23.86s]   - Upgrading symfony/password-hasher (v6.4.24 => v6.4.32)

[30.5MiB/23.86s]   - Upgrading symfony/polyfill-ctype (v1.33.0 => v1.37.0)

[30.5MiB/23.86s]   - Upgrading symfony/polyfill-intl-grapheme (v1.33.0 => v1.38.1)

[30.5MiB/23.86s]   - Upgrading symfony/polyfill-intl-idn (v1.33.0 => v1.38.1)

[30.5MiB/23.86s]   - Upgrading symfony/polyfill-intl-normalizer (v1.33.0 => v1.38.0)

[30.5MiB/23.86s]   - Upgrading symfony/polyfill-mbstring (v1.33.0 => v1.38.2)

[30.5MiB/23.86s]   - Upgrading symfony/polyfill-php73 (v1.33.0 => v1.37.0)

[30.5MiB/23.86s]   - Upgrading symfony/polyfill-php80 (v1.33.0 => v1.37.0)

[30.5MiB/23.86s]   - Upgrading symfony/polyfill-php81 (v1.33.0 => v1.38.1)

[30.5MiB/23.86s]   - Upgrading symfony/polyfill-php83 (v1.33.0 => v1.38.2)

[30.5MiB/23.86s]   - Upgrading symfony/polyfill-php84 (v1.33.0 => v1.38.1)

[30.5MiB/23.86s]   - Upgrading symfony/polyfill-uuid (v1.33.0 => v1.37.0)

[30.5MiB/23.86s]   - Upgrading symfony/process (v6.4.26 => v6.4.41)

[30.5MiB/23.87s]   - Upgrading symfony/property-access (v6.4.25 => v6.4.32)

[30.5MiB/23.87s]   - Upgrading symfony/property-info (v7.3.4 => v7.4.8)

[30.5MiB/23.87s]   - Upgrading symfony/rate-limiter (v6.4.24 => v6.4.42)

[30.5MiB/23.87s]   - Upgrading symfony/routing (v6.4.26 => v6.4.41)

[30.5MiB/23.87s]   - Upgrading symfony/security-bundle (v6.4.26 => v6.4.42)

[30.5MiB/23.87s]   - Upgrading symfony/security-core (v6.4.26 => v6.4.42)

[30.5MiB/23.87s]   - Upgrading symfony/security-csrf (v6.4.24 => v6.4.31)

[30.5MiB/23.87s]   - Upgrading symfony/security-http (v6.4.26 => v6.4.42)

[30.5MiB/23.87s]   - Upgrading symfony/service-contracts (v3.6.0 => v3.7.1)

[30.5MiB/23.88s]   - Upgrading symfony/string (v6.4.26 => v6.4.39)

[30.5MiB/23.88s]   - Upgrading symfony/translation (v6.4.26 => v6.4.42)

[30.5MiB/23.88s]   - Upgrading symfony/translation-contracts (v3.6.0 => v3.7.1)

[30.5MiB/23.88s]   - Upgrading symfony/twig-bridge (v6.4.25 => v6.4.42)

[30.5MiB/23.88s]   - Upgrading symfony/twig-bundle (v6.4.24 => v6.4.32)

[30.5MiB/23.88s]   - Upgrading symfony/type-info (v7.3.4 => v7.4.9)

[30.5MiB/23.88s]   - Upgrading symfony/uid (v6.4.24 => v6.4.32)

[30.5MiB/23.88s]   - Upgrading symfony/var-dumper (v6.4.26 => v6.4.42)

[30.5MiB/23.88s]   - Upgrading symfony/var-exporter (v7.3.4 => v7.4.14)

[30.6MiB/23.88s]   - Upgrading symfony/yaml (v6.4.26 => v6.4.42)

[30.6MiB/23.89s]   - Upgrading terminal42/contao-leads (3.1.3 => 3.2.1)

[30.6MiB/23.89s]   - Upgrading terminal42/escargot (1.6.3 => 1.7.0)

[30.6MiB/23.89s]   - Upgrading terminal42/service-annotation-bundle (1.2.1 => 1.2.2)

[30.6MiB/23.89s]   - Upgrading toflar/cronjob-supervisor (2.0.2 => 2.1.3)

[30.6MiB/23.89s]   - Upgrading twig/string-extra (v3.21.0 => v3.24.0)

[30.6MiB/23.89s]   - Upgrading twig/twig (v3.21.1 => v3.28.0)

[29.8MiB/23.90s] Writing lock file

[16.6MiB/23.93s] Package doctrine/annotations is abandoned, you should avoid using it. No replacement was suggested.

[16.6MiB/23.93s] Package doctrine/cache is abandoned, you should avoid using it. No replacement was suggested.

[16.6MiB/23.93s] Package php-http/message-factory is abandoned, you should avoid using it. Use psr/http-factory instead.

[16.8MiB/24.36s] Found 2 security vulnerability advisories affecting 1 package.

[16.8MiB/24.36s] Run "composer audit" for a full list of advisories.

[17.4MiB/24.36s] Memory usage: 17.35MB (peak: 216.65MB), time: 24.37s.

[17.4MiB/24.36s] Finished Composer Cloud resolving.





# Job ID fwF83JDRfYL5Cghd2q1NppmC31kwFpdWyrB80N92xDUB5gJCz3EITys2gUTqztuGtWMmhSyo1L06B0BHDiLXch6aCbIZc7QNa1xxxxxxxx completed in 31 seconds

# Memory usage: 17.35MB (peak: 216.65MB), time: 24.37s.



$ /usr/local/php83/bin/php -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 contao-directory/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.

Package php-http/message-factory is abandoned, you should avoid using it. Use psr/http-factory instead.

Generating optimized autoload files

contao/manager-plugin: Dumping generated plugins file...

contao/manager-plugin: ...done dumping generated plugins file

120 packages you are using are looking for funding.

Use the `composer fund` command to find out more!

> @php vendor/bin/contao-setup



Fatal error: Uncaught Error: Class "League\FlysystemBundle\Adapter\AdapterDefinitionFactory" not found in contao-directory/vendor/contao/core-bundle/src/DependencyInjection/Filesystem/FilesystemConfiguration.php:34

Stack trace:

#0 contao-directory/vendor/contao/core-bundle/src/DependencyInjection/Filesystem/FilesystemConfiguration.php(32): [constant expression]()

#1 contao-directory/vendor/contao/core-bundle/src/DependencyInjection/Compiler/ConfigureFilesystemPass.php(31): Contao\CoreBundle\DependencyInjection\Filesystem\FilesystemConfiguration->__construct(Object(Contao\ManagerPlugin\Config\ContainerBuilder))

#2 contao-directory/vendor/symfony/dependency-injection/Compiler/Compiler.php(80): Contao\CoreBundle\DependencyInjection\Compiler\ConfigureFilesystemPass->process(Object(Contao\ManagerPlugin\Config\ContainerBuilder))

#3 contao-directory/vendor/symfony/dependency-injection/ContainerBuilder.php(773): Symfony\Component\DependencyInjection\Compiler\Compiler->compile(Object(Contao\ManagerPlugin\Config\ContainerBuilder))

#4 contao-directory/vendor/symfony/http-kernel/Kernel.php(518): Symfony\Component\DependencyInjection\ContainerBuilder->compile()

#5 contao-directory/vendor/contao/manager-bundle/src/HttpKernel/ContaoKernel.php(291): Symfony\Component\HttpKernel\Kernel->initializeContainer()

#6 contao-directory/vendor/symfony/http-kernel/Kernel.php(783): Contao\ManagerBundle\HttpKernel\ContaoKernel->initializeContainer()

#7 contao-directory/vendor/symfony/http-kernel/Kernel.php(128): Symfony\Component\HttpKernel\Kernel->preBoot()

#8 contao-directory/vendor/symfony/framework-bundle/Console/Application.php(190): Symfony\Component\HttpKernel\Kernel->boot()

#9 contao-directory/vendor/symfony/framework-bundle/Console/Application.php(72): Symfony\Bundle\FrameworkBundle\Console\Application->registerCommands()

#10 contao-directory/vendor/symfony/console/Application.php(175): Symfony\Bundle\FrameworkBundle\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))

#11 contao-directory/vendor/contao/manager-bundle/bin/contao-setup(45): Symfony\Component\Console\Application->run()

#12 contao-directory/vendor/bin/contao-setup(119): include('/var/www/vhosts...')

#13 {main}

  thrown in contao-directory/vendor/contao/core-bundle/src/DependencyInjection/Filesystem/FilesystemConfiguration.php on line 34

Script @php vendor/bin/contao-setup handling the post-install-cmd event returned with error code 255



# Process terminated with exit code 255

# Result: Unknown error

Der Uncaught Error macht hier wohl Sorgen.

Ich weiß jedoch nicht, was ich noch tun kann, um diesem Problem zu begegnen bzw. aus dem Weg zu gehen.
Und ich verstehe nicht, warum so viele Packages aktualisiert werden, obwohl ich ja nur Leads aktualisieren will.

Könnt ihr mir hier helfen?

Beste Grüße