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

No ability to reset filters after an error #8538

Closed
spyrule opened this issue Feb 13, 2017 · 17 comments · Fixed by #28687
Closed

No ability to reset filters after an error #8538

spyrule opened this issue Feb 13, 2017 · 17 comments · Fixed by #28687
Labels
bug report Component: Backend Component: Catalog Component: Filter Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Priority: P3 May be fixed according to the position in the backlog. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.

Comments

@spyrule
Copy link

spyrule commented Feb 13, 2017

If a filter is applied to the Product Categories window, if that filter is removed, it generates a "Something went wrong" error, that prevents you from ever "erasing" the problematic error.

Preconditions

  1. Magento 2.4-develop
  2. PHP 7.3
  3. Nginx hosted service

Steps to reproduce

  1. Create a new store view (call it test for example)
  2. Log into admin > Products > Catalog
  3. Set up and apply a filter for the newly created store view;
  4. Now, go to Admin->Stores->All Stores;
  5. Delete the created before "test" store view;
  6. Switch back to the Product Catalog, you'll get "Something went wrong" error

Expected result

  1. If there is an error in selecting a filter option, it should apply NO FILTER at all, and indicate that a filter option was broken.

Actual result

✖️ Attention. Something went wrong
Screenshot from 2020-04-08 11-34-07

@rogyar
Copy link
Contributor

rogyar commented Feb 14, 2017

That's an annoying issue. Have a lack of time to find a sort of fix, but can recommend a workaround. When you get the "Something went wrong" message, open Developer Tools console in your browser and type there:

jQuery('.action-clear').click();

That will simulate the "Clear All" link click for filters (tried in Chrome). Hope it will help.

@oleg-onufer
Copy link
Contributor

Hi @spyrule.
Thanks for reporting this issue.
Internal ticket MAGETWO-70414 was created.

@veloraven veloraven added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Jul 3, 2017
@magento-engcom-team magento-engcom-team added 2.1.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development bug report Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed and removed G1 Passed labels Sep 5, 2017
@magento-engcom-team
Copy link
Contributor

@spyrule, thank you for your report.
We've created internal ticket(s) MAGETWO-70414, MAGETWO-80634 to track progress on the issue.

@magento-engcom-team magento-engcom-team added 2.2.x Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Oct 11, 2017
@RomaKis RomaKis self-assigned this Dec 6, 2017
@RomaKis
Copy link
Contributor

RomaKis commented Dec 6, 2017

This issue was fixed by the commits:
2933325, 550ae56,
478b0ec,
a6a2301,
aafcc0b.
@magento-engcom-team, I think you can close this ticket.

@ghost ghost unassigned engcom-Alfa Apr 8, 2020
@magento-engcom-team magento-engcom-team added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Apr 8, 2020
@magento-engcom-team
Copy link
Contributor

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

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

@VladimirZaets VladimirZaets added Priority: P3 May be fixed according to the position in the backlog. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Jun 25, 2020
@m2-community-project m2-community-project bot added Progress: PR Created Indicates that Pull Request has been created to fix issue and removed Progress: PR in progress labels Sep 3, 2020
@magento-engcom-team magento-engcom-team added Progress: ready for dev and removed Progress: PR Created Indicates that Pull Request has been created to fix issue labels Sep 8, 2020
@magento-engcom-team
Copy link
Contributor

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

The fix will be available with the upcoming 2.4.2 release.

@magento-engcom-team magento-engcom-team added the Fixed in 2.4.x The issue has been fixed in 2.4-develop branch label Sep 10, 2020
@joinso
Copy link

joinso commented Nov 25, 2020

Hi!

We see the same error on Order Grid in Magento 2.3.5

Regards,
JOINSO

@arzezniczak
Copy link

I have the same issue on 2.2.8

Regards,
Adrian

@mweaver-inmusic
Copy link

mweaver-inmusic commented Sep 10, 2021

This is still an issue in magento ver. 2.3.6
but opening up the console and running
jQuery('.action-clear').click();
will reset the filters

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Component: Backend Component: Catalog Component: Filter Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Priority: P3 May be fixed according to the position in the backlog. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
None yet
Development

Successfully merging a pull request may close this issue.