Fehler nach Contao Manager Update

**lbmh** · 13.08.2021, 15:43

Hallo,
seid dem Contaomanager Update funktionieren Frontend/Backend nichtmehr und im Manager komme ich in die System Recovery mit der Meldung

Code:

The Contao Manager detected files that look like Contao, but the Command Line Interface does not work as expected. Please choose an option to repair your installation.".

Wenn ich die automatische System Reperatur mache kommt

Code:

HTTP request for "DELETE api/task" failed.
The server returned a response with status code 403.
Active task cannot be deleted

composer install bringt folgendes:

Code:

Installing dependencies from lock file
Verifying lock file contents can be installed on current platform.
Nothing to install, update or remove
Package contao-components/compass is abandoned, you should avoid using it. No replacement was suggested.
Package doctrine/doctrine-cache-bundle is abandoned, you should avoid using it. No replacement was suggested.
Package doctrine/reflection is abandoned, you should avoid using it. Use roave/better-reflection instead.
Package menatwork/contao-multicolumnwizard is abandoned, you should avoid using it. Use menatwork/contao-multicolumnwizard-bundle instead.
Package oyejorge/less.php is abandoned, you should avoid using it. No replacement was suggested.
Package patchwork/utf8 is abandoned, you should avoid using it. Use symfony/polyfill-mbstring or symfony/string instead.
Package paypal/rest-api-sdk-php is abandoned, you should avoid using it. No replacement was suggested.
Package phpunit/php-token-stream is abandoned, you should avoid using it. No replacement was suggested.
Package sensio/distribution-bundle is abandoned, you should avoid using it. No replacement was suggested.
Package sensiolabs/security-checker is abandoned, you should avoid using it. Use https://github.com/fabpot/local-php-security-checker instead.
Package setasign/fpdi-tcpdf is abandoned, you should avoid using it. No replacement was suggested.
Package terminal42/contao-ce-access is abandoned, you should avoid using it. No replacement was suggested.
Generating optimized autoload files
contao/manager-plugin: Generating plugin class...
36 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
# Process terminated with exit code 255
# Result: Unknown error

Wenn ich im Save Mode den Prod Cache neu erstellen lassen will kommt diese Fehlermeldung:

Code:

In YamlFileLoader.php line 698:
                                                                               
  There is no extension able to load the configuration for "contao" (in "/htm  
  l/contao/app/config/config.yml"). Looked for namespace "contao", found "non  
  e".

Ich habe composer update ausgeführt, das hat aber nichts geändert. Im Contao log steht nichts.
Meine composer.json

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" : {
		"php" : "^5.6 || ^7.0",
		"codefog/contao-cookiebar" : "^2.1",
		"codefog/contao-haste" : "^4.21",
		"codefog/contao-news_categories" : "^3.0",
		"codefog/contao-widget_tree_picker" : "^2.4",
		"contao/calendar-bundle" : "^4.4",
		"contao/comments-bundle" : "^4.4",
		"contao/conflicts" : "*@dev",
		"contao/faq-bundle" : "^4.4",
		"contao/listing-bundle" : "^4.4",
		"contao/manager-bundle" : "4.4.*",
		"contao/news-bundle" : "^4.4",
		"contao/newsletter-bundle" : "^4.4",
		"delahaye/dlh_geocode" : "^1.1",
		"delahaye/dlh_googlemaps" : "^2.4",
		"do-while/contao-pdfforms-bundle" : "^1.4",
		"fritzmg/contao-sharebuttons" : "^2.0",
		"jrgregory/m17-sticky-backend-footer" : "^2.0",
		"kmielke/calendar-extended-bundle" : "^1.0",
		"leadingsystems/contao-merconis" : "^4.0",
		"madeyourday/contao-rocksolid-columns" : "^2.0",
		"madeyourday/contao-rocksolid-custom-elements" : "^2.2",
		"madeyourday/contao-rocksolid-icon-picker" : "^2.0",
		"madeyourday/contao-rocksolid-slider" : "^2.0",
		"menatwork/contao-multicolumnwizard" : "^3.3",
		"terminal42/contao-ce-access" : "^2.0",
		"terminal42/notification_center" : "1.4.1",
		"localbranding-de/gameaccountdetails-bundle" : "1.0.3"
	},
	"repositories" : [{
			"type" : "git",
			"url" : "https://github.com/localbranding-de/gameaccountdetails-bundle.git"
		}
	],
	"config" : {
		"component-dir" : "assets",
		"preferred-install" : {
			"localbranding-de/*" : "source",
			"*" : "dist"
		}
	},
	"conflict" : {
		"contao-components/installer" : "<1.3",
		"contao/core-bundle" : "<4.4.8"
	},
	"extra" : {
		"branch-alias" : {
			"dev-4.4" : "4.4.x-dev"
		},
		"contao-component-dir" : "assets"
	},
	"scripts" : {
		"post-install-cmd" : "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication",
		"post-update-cmd" : "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
	}
}

**ChrisT** · 03.11.2022, 16:37

Hallo

Hat mal jemand reagiert oder konntest du das Problem lösen? Ich habe mittlerweile schon einige Installationen mit dem Verhalten erlebt und ging bisher immer den einfachsten Weg: Wiederherstellung und nichts mehr anfassen. Aber für ein CMS, das sich für die Update-Philosophie lobt, kann das nicht die Lösung sein.

Grüsse, Chris