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
New magento update of magento/services-connector/ destroys everything #29188
Comments
Hi @Eddcapone. Thank you for your report.
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
For more details, please, review the Magento Contributor Assistant documentation. Please, add a comment to assign the issue:
🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket. 🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
Hi @krishprakash. Thank you for working on this issue.
|
I confirm this issue on Magento CE 2.3.5 too. It's because of latest version update 1.0.6 only. Looks like they have shipped services-connector with wrong directory structure. |
The problem is fixed, they released 1.0.7 |
Preconditions (*)
Steps to reproduce (*)
Reload frontend
500 server error
php bin/magento list
-> nothing happens
Edit pub/index.php and add this code to see error message:
Reload frontend
See this error message
Expected result (*)
Actual result (*)
Addional Information:
After downgrading to 1.0.5, it works again.
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.
The text was updated successfully, but these errors were encountered: