Skip to content
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

Category filters - Fix notice on incorrect price param #25912

Merged
merged 2 commits into from
Dec 10, 2019

Conversation

ihor-sviziev
Copy link
Contributor

Description (*)

See details in #25911

Fixed Issues (if relevant)

  1. Category - Notice on incorrect price filter GET param #25911 : Category - Notice on incorrect price filter GET param

Manual testing scenarios (*)

  1. See details in Category - Notice on incorrect price filter GET param #25911

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • 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)

@m2-assistant
Copy link

m2-assistant bot commented Dec 5, 2019

Hi @ihor-sviziev. 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.3-develop instance - deploy vanilla Magento instance

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

@ihor-sviziev ihor-sviziev changed the title magento/magento2#25911 Fix notice on incorrect price param Category filters - Fix notice on incorrect price param Dec 5, 2019
@ihor-sviziev ihor-sviziev added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Dec 5, 2019
@sidolov sidolov changed the base branch from 2.3-develop to 2.4-develop December 5, 2019 17:00
@ghost ghost assigned krzksz Dec 7, 2019
@magento-engcom-team
Copy link
Contributor

Hi @krzksz, thank you for the review.
ENGCOM-6424 has been created to process this Pull Request

@engcom-Bravo
Copy link
Contributor

Hello @ihor-sviziev. Thank You for Your contribution. Would You please take a look at the following gif:
category
The system.log also does not contain any main.criticals. So it is that ether the issue this PR is going to fix is not reproduced on 2.4-develop or we miss or misunderstand something when trying to reproduce it. If the true one is the second please help us to reproduce it. Thank You.

@engcom-Bravo
Copy link
Contributor

engcom-Bravo commented Dec 7, 2019

@ihor-sviziev, we have immediately found the cause we were not able to reproduce the issue. In order to have it reproduced "for instance https://example.com/my-category/?price=-100%27[0]" should be replaced with "for instance https://example.com/my-category?price=-100%27[0]" - the "/" before the ? should be removed. I believe in 2.3 version Your reported the issue on it was reproduced with that slash, but as far as I remember there was a commit that brought some changes to category url behavior depending on presence of such a slash in it. So probably that is the reason the issue needs now to have category url be without slash before request part (before ?) in order to get reproduced. So we are proceeding with testing Your PR.

@engcom-Bravo
Copy link
Contributor

engcom-Bravo commented Dec 7, 2019

@ihor-sviziev, everyting works fine, sorry for disturbing You. ✔️ QA Passed.

@magento-engcom-team magento-engcom-team merged commit 414105e into magento:2.4-develop Dec 10, 2019
@m2-assistant
Copy link

m2-assistant bot commented Dec 10, 2019

Hi @ihor-sviziev, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

@MTheProgrammer
Copy link
Contributor

Hello, this is still an issue in Magento 2.4.2:

[2021-08-17 02:41:49] main.CRITICAL: Warning: A non-numeric value encountered in XXXX/vendor/magento/module-catalog-search/Model/Layer/Filter/Price.php on line 194 [] []

Type in the url non-numeric value for the price filter:
https://magento.domain/category.html?price=c-d

@ihor-sviziev
Copy link
Contributor Author

@magento give me 2.4-develop instance

@magento-deployment-service
Copy link

Hi @ihor-sviziev. Thank you for your request. I'm working on Magento instance for you.

@ihor-sviziev
Copy link
Contributor Author

ihor-sviziev commented Aug 17, 2021

Hi @MTheProgrammer,
I can't reproduce the issue on the 2.4-develop issue both on the test instance and on the local machine.
Tested on the following page with deployed sample data:
https://1f4f5d16fa7d1b45781c91cc4946a511-2-4-develop.instances.magento-community.engineering/training/training-video.html?price=c-d
https://app.magento24.test/training/training-video.html?price=c-d

If you are still able to reproduce it - please create a separate issue with steps to reproduce.
Thank you!

@ihor-sviziev ihor-sviziev deleted the fix-25911 branch August 17, 2021 06:10
@sdzhepa sdzhepa mentioned this pull request May 9, 2022
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants