-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Error: Call to a member function setScopeFilter() #35402
Comments
Hi @jorgb90. Thank you for your report.
Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
For more details, review the Magento Contributor Assistant documentation. Add a comment to assign the issue: To learn more about issue processing workflow, refer to the Code Contributions.
🕙 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, join the Community Contributions Triage session to discuss the appropriate ticket. ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
Hi @engcom-November. Thank you for working on this issue.
|
Hi @jorgb90 , |
Hi @engcom-November We have updated the platform from 2.4.3-p1 to 2.4.4, but the platform itself is already older then that. We are running into this issue when opening a customer account in the admin and create an order from there. Perhaps it occurs cause we have a multi-store setup and our customers have a default address saved. |
Is probably caused by this change: MC-42623:Countries list is incorrect when using different countries per website and Global Customer Account settings. Somehow that <argument name="customerAddressCollectionAttributeFilter" xsi:type="object">Magento\Sales\ViewModel\Customer\Address\AddressAttributeFilter</argument> So maybe you have some kind of customisation done to the backoffice order create form, that's somehow missing this |
@hostep Thanks! Will look into this. Only thing is that creating a new order from the order overview and selecting a customer there doesn't trigger this problem. It only occurs when trying to create an order from the customer profile. Update: |
Found the issue to be indeed a module, so this can be closed. |
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
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: