Also was mir als 1. aufgefallen ist, das composer.json~ als auch composer.lock~ ein "~" am Dateinamen angehängt haben. Die composer.lock ist komplett leer und nachfolgend der Inhalt von 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",
"bugbuster/contao-be_user_online-bundle": "^1.0",
"cliffparnitzky/user-member-bridge": "^1.2",
"codefog/contao-member_export": "^2.1",
"contao/calendar-bundle": "4.4.43",
"contao/comments-bundle": "4.4.43",
"contao/conflicts": "*@dev",
"contao/faq-bundle": "4.4.43",
"contao/listing-bundle": "4.4.43",
"contao/manager-bundle": "4.4.43",
"contao/news-bundle": "4.4.43",
"contao/newsletter-bundle": "4.4.43",
"dalley-it/contao-photoswipe": "^1.0",
"do-while/contao-backupdb-bundle": "^1.3",
"kmielke/calendar-extended-bundle": "^1.0",
"markocupic/be_email": "^3.1.11",
"netzmacht/contao-font-awesome": "^4.7",
"netzmacht/contao-font-awesome-inserttag": "^2.0",
"terminal42/contao-fineuploader": "^2.1",
"terminal42/notification_center": "^1.4",
"trilobit-gmbh/contao-search-bundle": "^1.0"
},
"conflict": {
"contao/core-bundle": "<4.4.8"
},
"config": {
"component-dir": "assets"
},
"extra": {
"branch-alias": {
"dev-4.4": "4.4.x-dev"
}
},
"scripts": {
"post-install-cmd": [
"Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
],
"post-update-cmd": [
"Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
]
}
}
Obwohl in der composer.json die Contao Pakete mit der Version 4.4.43 bezeichnet sind, werden diese Pakete im Contao-Manager als 4.4.39 angezeigt.
Gruß
Thomas
Lesezeichen