-
Notifications
You must be signed in to change notification settings - Fork 9.4k
2.1.3 - Web Setup Wizzard - Component Manager - spinning wheel (still doesn't work) #7958
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
Comments
I'm seeing 20 minute page load times for the page itself, however, it does eventually load. I would say this makes it practically unusable though, as the admin session seems to timeout waiting on the page load to occur. |
Experiencing the same issue. In fact the whole "Web Setup Wizard" is kind of useless. Updating Magento makes no sense either. Why did this all get so complicated and instable? |
I'm having the same problem, but with a freshly installed instance of Magento 2.1.5 |
@AvanorHealthcare We moved everything into composer installs using marketplace credentials. Almost every popular module now offers the ability to install the module through the composer.json file instead of using the web install wizard. Personally, I'd recommend going that route |
@JamesonNetworks Funnily enough, that's exactly what I've been doing. It just seems daft to have to go through the grind of doing a command line install when there's supposed to be an easy, built-in function linked directly to Magento Marketplace. |
@AvanorHealthcare, when you say you use the composer.json, can you please tell me how you used this file? Is there a UI, or did you run a command using this file? Thank you |
@pkm32 https://store.fooman.co.nz/blog/installing-a-magento-2-extension-from-marketplace-using-command-line.html This is all from the commandline and gets committed with the repo |
I have fixed this issue by following below steps:
|
@commcad, thank you for your report. |
[Chaika] BugFix delivery
Preconditions
Steps to reproduce
Expected result
Actual result
( the most epic wait ever!)
The text was updated successfully, but these errors were encountered: