Skip to content

"Active filters" shows the "Asset:" filter which is empty if switch to the Default View again #1780

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

Closed
engcom-Lima opened this issue Aug 21, 2020 · 1 comment · Fixed by magento/magento2#29783
Assignees
Labels
Priority: P1 Needs to be fixed before any other issues Progress: done Severity: S2 Affects non-critical data or functionality and forces users to employ a workaround
Milestone

Comments

@engcom-Lima
Copy link

Preconditions (*)

  1. Install Magento 2.4-develop with Adobe Stock Integration and IMS
  2. Configured integration in Stores -> Configuration -> Advanced-> System -> Adobe Stock Integration fieldset
  3. New Media Gallery Enabled
  4. Image added to a category

Steps to reproduce (*)

  1. Go to Content -> Media Gallery
  2. Select the image that is added to the category by clicking on it
  3. Click on three dots -> View Details
  4. Click on the link 'Categories..." in 'Used in' attribute
  5. Delete the ?filters[asset_id]=[1] part of request from address line -> Press Enter key
  6. Click on the "Clear all" link
  7. Wait for a few seconds and reload the page
  8. Click on the "Default View" dropdown
  9. Select the "Default View" by clicking on it

Expected result (*)

No Active filters

Actual result (*)

"Active filters" shows the "Asset:" filter which is empty
Video
Screenshot_121

@m2-assistant
Copy link

m2-assistant bot commented Aug 21, 2020

Hi @engcom-Lima. Thank you for your report.
To help us process this issue please make sure that you provided sufficient information.

Please, add a comment to assign the issue: @magento I am working on this


@Nazar65 Nazar65 self-assigned this Aug 21, 2020
@Nazar65 Nazar65 added Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround Severity: S2 Affects non-critical data or functionality and forces users to employ a workaround and removed Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround labels Aug 21, 2020
@sivaschenko sivaschenko added the Priority: P1 Needs to be fixed before any other issues label Aug 25, 2020
@sivaschenko sivaschenko added this to the 2.1.0 milestone Aug 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: P1 Needs to be fixed before any other issues Progress: done Severity: S2 Affects non-critical data or functionality and forces users to employ a workaround
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants