magento2
magento2 copied to clipboard
magento/magento2#25933 : Single Store Mode- Incorrect scope values us…
we have resolve this issue : https://github.com/magento/magento2/issues/25933
Preconditions (*) Magento 2.3.3 CE & 2.4-develop with sample data Magento Instance should have one Website, Store and Store View only. Steps to reproduce (*)
- Under Default Config, Navigate to Stores > Settings > Configuration > Catalog > Catalog
- Change the values of field Products per Page on Grid Allowed Values from 9,15,30 to 5,10,20,40,80 (Uncheck Use System value checkbox if ticked - optional)
- Change the values of field Products per Page on Grid Default Value from 9 to 10 (Uncheck Use System value checkbox if ticked- optional)
- Click on Save Config
- Clear the cache if prompted to refresh the cache
- Switch the scope from Default Config to Default Store View Scope from the drop-down showing on upper-left corner
- Navigate to Stores > Settings > Configuration > Catalog > Catalog
- From Default Store View Scope, Uncheck Use Website checkbox for following fields . Products per Page on Grid Allowed Values . Products per Page on Grid Default Value
- Change the values of field Products per Page on Grid Allowed Values to 30,60,90
- Change the values of field Products per Page on Grid Default Value to 30 Click on Save Config
- Switch the scope to Default Config from Default Store View Scope
- From Default Config Scope, Set Enable Single-Store Mode to Yes
- Click Save Config
- Clear all the cache
- Now, Navigate to Stores > Settings > Configuration > Catalog > Catalog
- Tries to update the values for following fields.
- Products per Page on Grid Allowed Values 20,40,60 .Products per Page on Grid Default Value 20 19.Save Config and Clear all the cache 20.Open any category page to see the Show per page values.
Expected result (*) On category page, it should show 20,40,60 in the Show per page drop-down. Actual result (*) On category page, it shows values as 30,60,90 in the Show per page drop-down.
Description showing correct pagination based on system configurations.
Fixed Issues
- Fixes magento/magento2#25933
Contribution checklist (*)
- [x] Pull request has a meaningful description of its purpose
- [x] All commits are accompanied by meaningful commit messages
- [ ] All new or changed code is covered with unit/integration tests (if applicable)
- [ ] All automated tests passed successfully (all builds are green)
Hi @sanjay-magecomp. Thank you for your contribution Here is some useful tips how you can test your changes using Magento test environment. Add the comment under your pull request to deploy test or vanilla Magento instance:
@magento give me test instance- deploy test instance based on PR changes@magento give me 2.4-develop instance- deploy vanilla Magento instance
:exclamation: Automated tests can be triggered manually with an appropriate comment:
@magento run all tests- run or re-run all required tests against the PR changes@magento run <test-build(s)>- run or re-run specific test build(s) For example:@magento run Unit Tests
<test-build(s)> is a comma-separated list of build names. Allowed build names are:
Database CompareFunctional Tests CEFunctional Tests EE,Functional Tests B2BIntegration TestsMagento Health IndexSample Data Tests CESample Data Tests EESample Data Tests B2BStatic TestsUnit TestsWebAPI Tests
You can find more information about the builds here
:information_source: Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.
For more details, please, review the Magento Contributor Guide documentation.
:warning: According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
:clock10: You can find the schedule on the Magento Community Calendar page.
:telephone_receiver: The triage of Pull Requests 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.
:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
#dmcdindia2020
@magento give me test instance - deploy test instance based on PR changes
Hi @sanjay-magecomp. Thank you for your request. I'm working on Magento instance for you.
Hi @sanjay-magecomp, here is your Magento Instance: https://b4c46820c354d4c8d7afc01683ed1c38.instances.magento-community.engineering Admin access: https://b4c46820c354d4c8d7afc01683ed1c38.instances.magento-community.engineering/admin_3e70 Login: 09855333 Password: e412e6fc9d11
#dmcdindia2020
@magento give me test instance
Hi @pramod-mishra. Thank you for your request. I'm working on Magento instance for you.
Hi @pramod-mishra, here is your Magento Instance: https://b4c46820c354d4c8d7afc01683ed1c38.instances.magento-community.engineering Admin access: https://b4c46820c354d4c8d7afc01683ed1c38.instances.magento-community.engineering/admin_3e70 Login: 09855333 Password: e412e6fc9d11
#dmcdindia2020
@yogeshkhasturi thank you for joining. Please accept team invitation here and self-assign the issue.
@magento run all tests
@magento run all tests
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.