Ergebnis 1 bis 6 von 6

Thema: Installation HostEurope, PHP 8.3

  1. #1
    Contao-Fan
    Registriert seit
    27.11.2009.
    Ort
    Bremen
    Beiträge
    482

    Standard Installation HostEurope, PHP 8.3

    Bei der Installation von Contao auf dem Server erhalte ich folgende Fehlermeldung in der Konsole:
    Code:
    > Resolving dependencies using Composer Cloud v3.8.2-2-ge29a39b
    
    [3.5MiB/0.19s] Loading composer repositories with package information
    [50.5MiB/6.09s] Updating dependencies
    [74.0MiB/6.83s] Your requirements could not be resolved to an installable set of packages.
    [74.0MiB/6.83s] 
      Problem 1
        - Root composer.json requires contao/newsletter-bundle 5.6.* -> satisfiable by contao/newsletter-bundle[5.6.0, ..., 5.6.10].
        - contao/core-bundle[5.6.5, ..., 5.6.10] require scheb/2fa-trusted-device ^6.0 || ^7.0 -> satisfiable by scheb/2fa-trusted-device[v6.0.0, ..., v6.13.1, v7.0.0, ..., v7.13.1].
        - contao/newsletter-bundle 5.6.0 requires contao/core-bundle 5.6.0 -> found contao/core-bundle[5.6.0] but these were not loaded, because they are affected by security advisories ("PKSA-3p5h-vgz7-458z", "PKSA-wjhx-cdbz-9x61", "PKSA-4m99-84h8-dntz", "PKSA-v6p5-ssqr-1zcw", "PKSA-66g4-yhz3-k3zh", "PKSA-c2g8-xqxr-4cjw"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
        - contao/newsletter-bundle 5.6.1 requires contao/core-bundle 5.6.1 -> found contao/core-bundle[5.6.1] but these were not loaded, because they are affected by security advisories ("PKSA-3p5h-vgz7-458z", "PKSA-wjhx-cdbz-9x61"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
        - contao/newsletter-bundle 5.6.10 requires contao/core-bundle 5.6.10 -> satisfiable by contao/core-bundle[5.6.10].
        - contao/newsletter-bundle 5.6.2 requires contao/core-bundle 5.6.2 -> found contao/core-bundle[5.6.2] but these were not loaded, because they are affected by security advisories ("PKSA-3p5h-vgz7-458z", "PKSA-wjhx-cdbz-9x61"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
        - contao/newsletter-bundle 5.6.3 requires contao/core-bundle 5.6.3 -> found contao/core-bundle[5.6.3] but these were not loaded, because they are affected by security advisories ("PKSA-3p5h-vgz7-458z", "PKSA-wjhx-cdbz-9x61"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
        - contao/newsletter-bundle 5.6.4 requires contao/core-bundle 5.6.4 -> found contao/core-bundle[5.6.4] but these were not loaded, because they are affected by security advisories ("PKSA-3p5h-vgz7-458z", "PKSA-wjhx-cdbz-9x61"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
        - contao/newsletter-bundle 5.6.5 requires contao/core-bundle 5.6.5 -> satisfiable by contao/core-bundle[5.6.5].
        - contao/newsletter-bundle 5.6.6 requires contao/core-bundle 5.6.6 -> satisfiable by contao/core-bundle[5.6.6].
        - contao/newsletter-bundle 5.6.7 requires contao/core-bundle 5.6.7 -> satisfiable by contao/core-bundle[5.6.7].
        - contao/newsletter-bundle 5.6.8 requires contao/core-bundle 5.6.8 -> satisfiable by contao/core-bundle[5.6.8].
        - contao/newsletter-bundle 5.6.9 requires contao/core-bundle 5.6.9 -> satisfiable by contao/core-bundle[5.6.9].
        - lcobucci/jwt[4.1.5, ..., 4.3.0, 5.1.0, ..., 5.6.0] require ext-sodium * -> the ext-sodium package is disabled by your platform config. Enable it again with "composer config platform.ext-sodium --unset".
    
          Alternatively you can require one of these packages that provide the extension (or parts of it):
          Keep in mind that the suggestions are automated and may not be valid or safe to use
          - paragonie/sodium_compat_ext_sodium
          - juspay/expresscheckout-php-sdk Express Checkout SDK for PHP allows easy integration with Juspay's EC payments as a service platform
          - vufind/vufind A flexible discovery layer.
    
        - lcobucci/jwt 5.0.0 requires php ~8.1.0 || ~8.2.0 -> your php version (8.3.28.0) does not satisfy that requirement.
        - scheb/2fa-trusted-device[v6.0.0, ..., v6.3.0] require php ~8.0.0 || ~8.1.0 -> your php version (8.3.28.0) does not satisfy that requirement.
        - scheb/2fa-trusted-device[v6.10.0, ..., v6.13.1] require lcobucci/jwt ^4.1 || ^5.0 -> satisfiable by lcobucci/jwt[4.1.5, 4.2.0, 4.2.1, 4.3.0, 5.0.0, ..., 5.6.0].
        - scheb/2fa-trusted-device[v6.13.0, v7.0.0, ..., v7.13.1] require lcobucci/jwt ^5.0 -> satisfiable by lcobucci/jwt[5.0.0, ..., 5.6.0].
        - scheb/2fa-trusted-device[v6.4.0, ..., v6.9.0] require php ~8.0.0 || ~8.1.0 || ~8.2.0 -> your php version (8.3.28.0) does not satisfy that requirement.
    
    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-gmagick.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-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-sodium` to temporarily ignore these required extensions.
    [74.0MiB/6.84s] 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.
    [30.8MiB/6.89s] Memory usage: 30.8MB (peak: 130.53MB), time: 6.9s.
    [30.8MiB/6.89s] Finished Composer Cloud resolving.
    
    
    # Cloud Job ID V4Ix11zruSjuEOvI3vis8lVuMtT7FgO9wP7mFNOCIoUgEEEulp36wC1Nsn0PEvM7frcG7UDRzdUDweMlfqRBTNLzOXJk85SZjR31soMv0B0zHex269Od6JC9mnGpfAs5 failed
    Falls es hilfreich ist, hier die composer.json, wie Contao sie bis zu diesem Punkt geschrieben hat:
    Code:
    {
        "type": "project",
        "require": {
            "contao/conflicts": "*@dev",
            "contao/manager-bundle": "5.6.*",
            "contao/calendar-bundle": "5.6.*",
            "contao/comments-bundle": "5.6.*",
            "contao/faq-bundle": "5.6.*",
            "contao/listing-bundle": "5.6.*",
            "contao/news-bundle": "5.6.*",
            "contao/newsletter-bundle": "5.6.*"
        },
        "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"
            ]
        }
    }
    Würde es ausreichen, die PHP-Version auf 8.2 umzustellen? Ich habe leider keine Rechte dafür, daher kann ich das nicht ohne Weiteres testen ...

  2. #2
    Community-Moderator
    Wandelndes Contao-Lexikon
    Avatar von Spooky
    Registriert seit
    12.04.2012.
    Ort
    Scotland
    Beiträge
    38.158
    Partner-ID
    10107

    Standard

    Bei deinem Hosting muss noch die "sodium" PHP-Extension aktiviert werden (oder zumindest bei der von dir benutzten PHP-Version).
    » sponsor me via GitHub or Revolut

  3. #3
    Contao-Fan
    Registriert seit
    27.11.2009.
    Ort
    Bremen
    Beiträge
    482

    Standard

    Danke für Deine schnelle Hilfe, Spooky! Genau daran lag es :-)

  4. #4
    Contao-Fan
    Registriert seit
    27.11.2009.
    Ort
    Bremen
    Beiträge
    482

    Standard

    Die Installation lief jetzt problemlos durch. Ich habe dann über den Contao Manager lasr-theme-bundle installiert und die Theme-Zip-Datei inkl. Demo importiert.
    Beim Aufruf des Frontends erhalte ich eine Fehlermeldung, von der ich nicht weiß, ob sie mit dem Theme oder der Einrichtung des Servers zusammenhängt:


    Code:
    [2026-01-20T17:44:10.604830+00:00] request.INFO: Matched route "tl_page.2.root". {"route":"tl_page.2.root","route_parameters":{"_controller":"Contao\\FrontendIndex::renderPage","_scope":"frontend","_locale":"de","_format":"html","_canonical_route":"tl_page.2","parameters":"","pageModel":{"Contao\\PageModel":[]},"_route":"tl_page.2.root","_route_object":{"Symfony\\Component\\Routing\\Route":[]}},"request_uri":"https://meine-domain.de/","method":"GET"} {"request_uri":"https://meine-domain.de/","request_method":"GET"}
    [2026-01-20T17:44:10.618789+00:00] request.CRITICAL: Uncaught PHP Exception TypeError: "Contao\CoreBundle\Routing\ResponseContext\JsonLd\ContaoPageSchema::__construct(): Argument #8 ($searchIndexer) must be of type string, null given, called in /home/567/public_html/123/vendor/contao/core-bundle/src/Routing/ResponseContext/CoreResponseContextFactory.php on line 115" at ContaoPageSchema.php line 23 {"exception":"[object] (TypeError(code: 0): Contao\\CoreBundle\\Routing\\ResponseContext\\JsonLd\\ContaoPageSchema::__construct(): Argument #8 ($searchIndexer) must be of type string, null given, called in /home/567/public_html/123/vendor/contao/core-bundle/src/Routing/ResponseContext/CoreResponseContextFactory.php on line 115 at /home/567/public_html/123/vendor/contao/core-bundle/src/Routing/ResponseContext/JsonLd/ContaoPageSchema.php:23)"} {"request_uri":"https://meine-domain.de/","request_method":"GET"}
    [2026-01-20T17:44:10.696045+00:00] messenger.INFO: Stopping worker. {"transport_names":["contao_prio_high"]} {"request_uri":"https://meine-domain.de/","request_method":"GET"}

  5. #5
    Contao-Fan
    Registriert seit
    27.11.2009.
    Ort
    Bremen
    Beiträge
    482

    Standard

    Hat sich erledigt: anscheinend war die Datenbank nicht auf dem neuesten Stand - warum auch immer

  6. #6
    Community-Moderator
    Wandelndes Contao-Lexikon
    Avatar von Spooky
    Registriert seit
    12.04.2012.
    Ort
    Scotland
    Beiträge
    38.158
    Partner-ID
    10107

    Standard

    Zitat Zitat von Lufine Beitrag anzeigen
    Hat sich erledigt: anscheinend war die Datenbank nicht auf dem neuesten Stand - warum auch immer
    Vermutlich durch den Theme Import - evt. war das Theme noch nicht für Contao 5.6 ausgelegt (also die Datenbankdaten dafür).
    » sponsor me via GitHub or Revolut

Aktive Benutzer

Aktive Benutzer

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

Berechtigungen

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