0

We want to streamline a magento installation managed via composer.

So, for example we have no need for Magento_SendFriend module, nor Magento_Review, and maybe other not essential / small modules.

So following the documentation I would issue the following command:

php bin/magento module:uninstall -r -c Magento_SendFriend

So far so good, as it starts to rattle through ..

You are about to remove code and/or database tables. Are you sure?[y/N]y
Enabling maintenance mode
You are removing data without a database backup.
No data to clear in Magento_SendFriend
Removing Magento_SendFriend from module registry in database
Removing Magento_SendFriend from module list in deployment configuration
Removing code from Magento codebase:

However, it has been stuck there for the past hour and a half, with the only edits I have found having been done to the app/etc/config.php.

-    'Magento_SendFriend' => 1,

Does it make sense to use this new option to remove unused or unneeded modules?

Is it normal for it to take this long?

Improve this question
3
  • I cannot comment about how long it's taking; have you looked in Magento, web server, PHP logs? As to the command, at the very least it's valuable because it checks for dependencies. Unless it's your own module you might not realize there are dependencies with other modules. You could try using the dependency checker and trying it manually but you should back everything up first.
    – Steve Johnson
    Commented Feb 4, 2016 at 20:47
  • @tecjam how did you initially deploy Magento? via composer create project? via git or via zip downloaded from magento.com?
    – Maddy
    Commented May 26, 2016 at 20:55
  • @Maddy I installed it via composer. And this is still happening, even with non-magento-core modules. For example, firegento-magesetup2 -> the last update to version 2.0.1 breaks the store due to missing the necessary UpgradeSchema file. Uninstalling and re-installing fixes this, but it is forever stuck uninstalling ... Link: github.com/firegento/firegento-magesetup2
    – tecjam
    Commented Jul 13, 2016 at 12:33

2 Answers 2

Reset to default
2

The solution is to run : composer update in an other console

Improve this answer
3
0

Composer stoped in load data from repo.magento.com

My auth.json was not correct. This decision helped me

config http-basic.repo.magento.com <public_key> <private_key>

How to use the new repo.magento.com

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.