-
Notifications
You must be signed in to change notification settings - Fork 156
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
Fatal error: Call to undefined method MagentoHackathon\Composer\Magento\Installer::setDeployManager() #107
Comments
Should be in the README or an UPGRADE.md file instead to have it here. |
a Pull Request is welcome :) |
Yes for sure :-) It was to see if we are agree ;-) |
I've running into this yesterday, here is a full report. TLDR: I only needed to run it two times, it recovered automatically (at least I think :) ):
|
thx for the info, and also thx for testing it on windows :) |
We have As far as my automatic deployment scripts are concerned, this could be handled as a special case, so I could program my deployment to deal with this, but I don't think this is reasonable in general. By further testing I found out that updating it w/o plugins it does not crash:
|
Just from the backtrace: Can't we check in the plugin.php to not call this in case it's the removal? Or in case that method/class is not there? (I dunno if it would need a change in 1.3 or in 2.0). This is my test-case: https://gist.github.com/tkdb/6e2982463ff225ca4b7b |
if you would like to submit a patch for this. |
right, upgrading to 2.0 now all my installs :) |
For ref: |
|
Is there any solution to this problem? I have tried all the given solutions, but none worked for me. |
@VishalParkash for magento 2.4 the correct repository would be https://github.com/magento/magento-composer-installer |
error message:
Fatal error: Call to undefined method MagentoHackathon\Composer\Magento\Installer::setDeployManager()
Happens when you update from 1.x to 2.x, as we switched from pure installer to plugin.
Solution: remove the vendor directory and the composer.lock and do a fresh install.
The text was updated successfully, but these errors were encountered: