Problem/Motivation

While the Media Resolver Drush command successfully updates the Media Type for assets as expected, there is a discrepancy in how these assets are indexed or queried within the Drupal Media Library.

The Issue: After running the resolver, the Media Library UI displays the "updated" Media Type correctly in the table/grid view. However, the filters do not recognize this change. If an author filters by the new Media Type, the result is blank. Conversely, if the author filters by the previous Media Type, the asset appears in the results (even though the displayed metadata shows the new type).

Steps to reproduce

  • Execute the Media Resolver Drush command to map assets to their corresponding Media Type per documentation.
  • Navigate to the Media Library (/admin/content/media).
  • Search for a migrated asset by name and filter by the updated/correct Media Type.
    • Observed Result: No assets are found.
  • Search for the same asset name but filter by the original/previous Media Type.
    • Observed Result: The asset appears, despite the UI showing it now belongs to the new Media Type.
  • Note: This behavior persists even after performing a full cache rebuild (drush cr).

Business Impact:

This is a blocker for our editorial team. Authors are unable to discover or utilize assets when using Media Type filters, leading to significant delays in content production and confusion regarding asset organization.

Issue fork acquia_dam-3589648

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

rajeshreeputra created an issue. See original summary.

  • rajeshreeputra committed 54539420 on 1.1.x
    Resolve #3589648 "Fix media resolver drush command to update bundle in...
rajeshreeputra’s picture

Status: Active » Fixed

Merged!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.