BUG: `getDefaultLimitPerPageValue` returns value that is not available

[lbajsarowicz]

Preconditions (*)

As a Store Administrator, you are able to provide the Products per Page on Grid Allowed Values and Products per Page on Grid Default Value. There is no verification, so you can accidentally set the default value to be one of the unavailable options.

Steps to reproduce (*)

1. Change catalog/frontend/grid_per_page_values to 1,2,5 using CLI
2. Change catalog/frontend/grid_per_page to 12
3. Get the value of catalog/frontend/grid_per_page_values in your Template

Expected result (*)

1. Configuration should return only allowed values, so we expect to return one of the available values (1,2 or 5)

Actual result (*)

1. Configuration returns value that is not allowed - value of 12

[m2-assistant]

Hi @lbajsarowicz. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@lbajsarowicz do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[magento-engcom-team]

✅ Confirmed by @okorshenko
Thank you for verifying the issue. Based on the provided information internal tickets MC-33644 were created

Issue Available: @okorshenko, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

Hi @lbajsarowicz. Thank you for your report.
The issue has been fixed in #27093 by @lbajsarowicz in 2.4-develop branch
Related commit(s):

• 17236cc014ab718161e0cf446ce40f4eb8d27d9e
• 381ab640c0039652e93c2be24f0a9bf6be9a883e
• 778fbfbe8bd2740713762220f61eac07e34deedb
• d3962f2e82532829522e5cf68122b92c27932a02
• aec01d871608abbd17167ee141a0be3e358de683

The fix will be available with the upcoming 2.4.0 release.