{später}
Eine weitere halbe Stunde später habe ich mich getraut (ist ja nur die Kopie) im CM auf "Änderungen anwenden", also nicht Testlauf, anzuklicken. Die beiden Erweiterungen hatten einen Vermerk "manunell entfernt".
Mich irritiert schon die Ausgabe:
composer update craffft/contao-calendar-ical-bundle srhinow/tinymce-plugins contao/conflicts --no-install
Wieso will er update???
Weiterhin - ich habe ja eine KOPIE - habe ich via Shell probiert:
$ composer remove craffft/contao-calendar-ical-bundle
Und ich glaube, jetzt wird's spannend. Da kommt
Code:
contao-components/installer contains a Composer plugin which is currently not in your allow-plugins config. See https://getcomposer.org/allow-plugins
Do you trust "contao-components/installer" to execute code and wish to enable it now? (writes "allow-plugins" to composer.json) [y,n,d,?]
Kann es sein, dass das Ganze DESWEGEN immer hängen bleibt?
{nochmal ein bisschen später}
Ich habe y geantwortet, es kamen weitere Fragen die ich ebenfalls mit y beantwortet habe und dann... seht selbst... :-(
Code:
$ composer remove craffft/contao-calendar-ical-bundle
contao-components/installer contains a Composer plugin which is currently not in your allow-plugins config. See https://getcomposer.org/allow-plugins
Do you trust "contao-components/installer" to execute code and wish to enable it now? (writes "allow-plugins" to composer.json) [y,n,d,?] y
php-http/discovery contains a Composer plugin which is currently not in your allow-plugins config. See https://getcomposer.org/allow-plugins
Do you trust "php-http/discovery" to execute code and wish to enable it now? (writes "allow-plugins" to composer.json) [y,n,d,?] y
contao/manager-plugin contains a Composer plugin which is currently not in your allow-plugins config. See https://getcomposer.org/allow-plugins
Do you trust "contao/manager-plugin" to execute code and wish to enable it now? (writes "allow-plugins" to composer.json) [y,n,d,?] y
craffft/contao-calendar-ical-bundle is not required in your composer.json and has not been removed
./composer.json has been updated
Running composer update craffft/contao-calendar-ical-bundle
Loading composer repositories with package information
Cannot create cache directory /.../.cache/composer/repo/https---repo.packagist.org/, or directory is not writable. Proceeding without cache. See also cache-read-only config if your filesystem is read-only.
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- lcobucci/clock 2.3.0 requires php ~8.1.0 || ~8.2.0 -> your php version (8.3.15) does not satisfy that requirement.
- contao/core-bundle 4.13.36 requires lcobucci/jwt ^4.0 -> satisfiable by lcobucci/jwt[4.1.5].
- contao/calendar-bundle 4.13.36 requires contao/core-bundle 4.13.36 -> satisfiable by contao/core-bundle[4.13.36].
- lcobucci/jwt 4.1.5 requires lcobucci/clock ^2.0 -> satisfiable by lcobucci/clock[2.3.0].
- contao/calendar-bundle is locked to version 4.13.36 and an update of this package was not requested.
Removal failed, reverting ./composer.json to its original content.
Removal failed, craffft/contao-calendar-ical-bundle is still present, it may be required by another package. See `composer why craffft/contao-calendar-ical-bundle`.
Schon wieder will er anscheinend zu entfernende Erweiterungen aktualisieren? (composer update craffft/contao-calendar-ical-bundle)
Diese lcobucci-Dinger sagen mir genau nichts, die habe ich nicht wissentlich installiert und die tauchen im grafischen CM auch nicht auf.
Langsam gehen mir die Ideen aus...
Goneo: Contao-Manager kaputt?
Zitieren
. Das ist hier also nicht Woltlab.
Für Dinge die man mit html5 und css3 lösen kann, braucht man kein javascript.
.
Danke für die Erleuchtung bzgl. "managed".
Zitat von purzel
