Ergebnis 1 bis 5 von 5

Thema: CONTAO 4.13.32 - Installation Erweiterung Rock Solid Anti Spam

  1. #1
    Contao-Fan
    Registriert seit
    11.11.2011.
    Ort
    Schwerin
    Beiträge
    622

    Standard CONTAO 4.13.32 - Installation Erweiterung Rock Solid Anti Spam

    Hallo,



    Ich wollte soeben eine Erweiterung (Rock Solid Anti Spam) installieren, der Testlauf im CONTAO- Manager verlief ohne Fehler, aber bei der Installation gab es eine Fehlermeldung:

    ***************
    $ /opt/plesk/php/8.1/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=UTC /var/www/vhosts/ibu-europe.de/entwicklung.ibu-europe.de/website/web/contao-manager.phar.php composer install --no-dev --no-progress --no-ansi --no-interaction --optimize-autoloader
    Using config.component-dir has been deprecated. Please use extra.contao-component-dir instead.
    Installing dependencies from lock file
    Verifying lock file contents can be installed on current platform.
    Package operations: 0 installs, 1 update, 0 removals
    As there is no 'unzip' nor '7z' command installed zip files are being unpacked using the PHP zip extension.
    This may cause invalid reports of corrupted archives. Besides, any UNIX permissions (e.g. executable) defined in the archives will be lost.
    Installing 'unzip' or '7z' (21.01+) may remediate them.
    - Upgrading contao-components/tinymce4 (5.10.7 => 5.10.9): Extracting archive
    Update of contao-components/tinymce4 failed
    In Filesystem.php line 315:

    Could not delete assets/tinymce4/js/plugins/noneditable:

    in
    ***************


    Es betrifft also den Tiny Editor und die Frage, ob es an der verwaisten Erweiterung liegt, siehe Anlage ?

    https://www.ibu-europe.de/de/die-ibu/kontakt.html



    Vielen Dank für Hinweise.
    Angehängte Grafiken Angehängte Grafiken

  2. #2
    Contao-Fan
    Registriert seit
    24.02.2021.
    Beiträge
    455

    Standard

    Zitat Zitat von mv-soft Beitrag anzeigen
    - Upgrading contao-components/tinymce4 (5.10.7 => 5.10.9): Extracting archive
    Update of contao-components/tinymce4 failed
    In Filesystem.php line 315:

    Could not delete assets/tinymce4/js/plugins/noneditable:
    Liegt nicht an den verwaisten Plugins sondern an einem Rechteproblem / am assets Ordner.
    Versuche es mal mit folgender Option unter Systemwartung im Contao-Backend: Symlinks neu erstellen, danach nochmal das Update durchführen.

  3. #3
    Contao-Fan
    Registriert seit
    11.11.2011.
    Ort
    Schwerin
    Beiträge
    622

    Standard

    Hallo,

    das habe ich gemacht, trotzdem Proleme:


    Code:
    $ /opt/plesk/php/8.1/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=UTC /var/www/vhosts/ibu-europe.de/entwicklung.ibu-europe.de/website/web/contao-manager.phar.php composer install --no-dev --no-progress --no-ansi --no-interaction --optimize-autoloader
    Using config.component-dir has been deprecated. Please use extra.contao-component-dir instead.
    Installing dependencies from lock file
    Verifying lock file contents can be installed on current platform.
    Package operations: 0 installs, 1 update, 0 removals
    As there is no 'unzip' nor '7z' command installed zip files are being unpacked using the PHP zip extension.
    This may cause invalid reports of corrupted archives. Besides, any UNIX permissions (e.g. executable) defined in the archives will be lost.
    Installing 'unzip' or '7z' (21.01+) may remediate them.
      - Upgrading contao-components/tinymce4 (5.10.7 => 5.10.9): Extracting archive
        Update of contao-components/tinymce4 failed
    In Filesystem.php line 315:
                                                                
      Could not delete assets/tinymce4/js/plugins/noneditable:  
                                                                
    install [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--dry-run] [--download-only] [--dev] [--no-suggest] [--no-dev] [--no-autoloader] [--no-progress] [--no-install] [--audit] [--audit-format AUDIT-FORMAT] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--] [<packages>...]
    # Process terminated with exit code 1
    # Result: General error


    Auch ein Update von CONTAO scheitert mit einer Fehlermeldung:

    Code:
    $ /opt/plesk/php/8.1/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=UTC /var/www/vhosts/ibu-europe.de/entwicklung.ibu-europe.de/website/web/contao-manager.phar.php composer install --no-dev --no-progress --no-ansi --no-interaction --optimize-autoloader
    Using config.component-dir has been deprecated. Please use extra.contao-component-dir instead.
    Installing dependencies from lock file
    Verifying lock file contents can be installed on current platform.
    Package operations: 0 installs, 1 update, 0 removals
    As there is no 'unzip' nor '7z' command installed zip files are being unpacked using the PHP zip extension.
    This may cause invalid reports of corrupted archives. Besides, any UNIX permissions (e.g. executable) defined in the archives will be lost.
    Installing 'unzip' or '7z' (21.01+) may remediate them.
      - Upgrading contao-components/tinymce4 (5.10.7 => 5.10.9): Extracting archive
        Update of contao-components/tinymce4 failed
    In Filesystem.php line 315:
                                                                
      Could not delete assets/tinymce4/js/plugins/noneditable:  
                                                                
    install [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--dry-run] [--download-only] [--dev] [--no-suggest] [--no-dev] [--no-autoloader] [--no-progress] [--no-install] [--audit] [--audit-format AUDIT-FORMAT] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--] [<packages>...]
    # Process terminated with exit code 1
    # Result: General error


    Ein weiter Versuch scheitert:
    Code:
    > Resolving dependencies using Composer Cloud v3.7.0
    [7.0MiB/0.23s] Loading composer repositories with package information
    [96.7MiB/15.53s] Updating dependencies
    [207.9MiB/16.96s] Your requirements could not be resolved to an installable set of packages.
    [207.9MiB/16.96s] 
      Problem 1
        - Root composer.json requires menatwork/semantic_html5 ^2.1 -> satisfiable by menatwork/semantic_html5[2.1.0].
        - menatwork/semantic_html5 2.1.0 requires php ^7.2 -> your php version (8.1.27.0) does not satisfy that requirement.
    Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
    [207.9MiB/16.97s] <warning>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.</warning>
    [60.5MiB/17.05s] Memory usage: 60.47MB (peak: 232.61MB), time: 17.06s.
    [60.5MiB/17.05s] Finished Composer Cloud resolving.
    # Cloud Job ID SXUzKA4jTf47HPEFq7nvvBbt5W4rZlAdYr80I1GhXAfmk4YUJdcylfZMxqYhvZOlTb failed


    Was habe ich übersehen?

  4. #4
    Contao-Fan
    Registriert seit
    11.11.2011.
    Ort
    Schwerin
    Beiträge
    622

    Standard

    Noch ein Hinweis:

    Über den CONTAO- Manager wurde versucht, ein Composer- Update zu machen:

    Code:
     Could not delete assets/tinymce4/js/plugins/noneditable:

  5. #5
    Contao-Fan
    Registriert seit
    11.11.2011.
    Ort
    Schwerin
    Beiträge
    622

    Standard LOSUNG

    Nach vielen Versuchen konnte nun nach Umstellung auf den Apache- Server das Update umgesetzt werden.


    Vielen Dank für die Unterstützung.

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
  •