Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't deactivate composer anymore #2570

Closed
thmsklngr opened this issue Jan 9, 2014 · 2 comments
Closed

Can't deactivate composer anymore #2570

thmsklngr opened this issue Jan 9, 2014 · 2 comments

Comments

@thmsklngr
Copy link

Hi,

I just installed composer for my own curiosity on my (unfortunately) production website, which is currently on version 2.11.13.

I skipped the migration part to get into the package manager and then tried to use "Swtich back to old client". I then confirmed my action by clicking the last button. The result itself is not very promising:

Fatal error: Could not load class ContaoCommunityAlliance\ComposerInstaller\ModuleInstaller in …/system/functions.php on line 105
#0 [internal function]: _error(256, 'Could not load ...', '/kunden/373305...', 105, Array)
#1 …/system/functions.php(105): trigger_error('Could not load ...', 256)
#2 [internal function]: __autoload('ContaoCommunity...')
#3 phar://…/composer/composer.phar/src/Composer/Plugin/PluginManager.php(231): spl_autoload_call('ContaoCommunity...')
#4 phar://…/composer/composer.phar/src/Composer/Installer/PluginInstaller.php(65): Composer\Plugin\PluginManager->registerPackage(Object(Composer\Package\CompletePackage))
#5 phar://…/composer/composer.phar/src/Composer/Installer/InstallationManager.php(153): Composer\Installer\PluginInstaller->install(Object(Composer\Repository\InstalledFilesystemRepository), Object(Composer\Package\CompletePackage))
#6 phar://…/composer/composer.phar/src/Composer/Installer/InstallationManager.php(140): Composer\Installer\InstallationManager->install(Object(Composer\Repository\InstalledFilesystemRepository), Object(Composer\DependencyResolver\Operation\InstallOperation))
#7 phar://…/composer/composer.phar/src/Composer/Installer.php(510): Composer\Installer\InstallationManager->execute(Object(Composer\Repository\InstalledFilesystemRepository), Object(Composer\DependencyResolver\Operation\InstallOperation))
#8 phar://…/composer/composer.phar/src/Composer/Installer.php(210): Composer\Installer->doInstall(Object(Composer\Repository\InstalledFilesystemRepository), Object(Composer\Repository\CompositeRepository), Object(Composer\Repository\PlatformRepository), Array, false)
#9 …/system/modules/!composer/ContaoCommunityAlliance/Contao/Composer/Controller/UndoMigrationController.php(68): Composer\Installer->run()
#10 …/system/modules/!composer/ContaoCommunityAlliance/Contao/Composer/ClientBackend.php(200): ContaoCommunityAlliance\Contao\Composer\Controller\UndoMigrationController->handle(Object(Input))
#11 …/system/modules/backend/Backend.php(239): ContaoCommunityAlliance\Contao\Composer\ClientBackend->generate()
#12 …/contao/main.php(120): Backend->getBackendModule('composer')
#13 …/contao/main.php(230): Main->run()
#14 {main}

I don't have any clue on how to get rid now of composer.

Here are some settings from the export mode window:
{
"name": "contao/core",
"description": "Contao Open Source CMS",
"license": "LGPL-3.0+",
"version": "2.11.13",
"type": "metapackage",
"require": {
"contao-community-alliance/composer": "*"
},
"scripts": {
"pre-update-cmd": "ContaoCommunityAlliance\ComposerInstaller\ModuleInstaller::preUpdate",
"post-update-cmd": "ContaoCommunityAlliance\ComposerInstaller\ModuleInstaller::postUpdate",
"post-autoload-dump": "ContaoCommunityAlliance\ComposerInstaller\ModuleInstaller::postAutoloadDump"
},
"config": {
"preferred-install": "dist",
"cache-dir": "cache"
},
"repositories": [
{
"type": "composer",
"url": "http://legacy-packages-via.contao-community-alliance.org/"
},
{
"type": "artifact",
"url": "packages/"
}
],
"extra": {
"contao": {
"migrated": "skipped"
}
}
}

Any hints on how to solve this would be great.

Regards, Thomas

@stof
Copy link
Contributor

stof commented Jan 9, 2014

Composer itself is not something you install in your website. It is a CLI tool. I think you confuse Composer with a module for your CMS (which could use Composer internally). This should be reported to the support team of the CMS module instead

@thmsklngr
Copy link
Author

I'm very sorry, I used the wrong section.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants