- 🇺🇸United States Chris Matthews
I believe this issue should be closed as a duplicate of #2969678: Integrate Media Library with Content Moderation →
I was reviewing the Media module recently and saw two bits of logic that definitely won't work with Content Moderation:
1. \Drupal\media\Plugin\QueueWorker\MetadataFetcher::processItem loads media items by ID, which will always load the default revision. If I understand this correctly, changing the source field on a forward revision (Draft) of a media item will not update the metadata for the latest revision.
2. \Drupal\media\MediaStorage::shouldUpdateMetadata compares the new source field value with $media->original. If $media->original isn't set the default revision of the media is loaded. Instead of loading the default revision, we should load the latest revision, I think. This one is a bit trickier and may not present practical bugs.
Add explicit support for forward revisions in the media module.
Audit more of the media module and determine what parts are incompatible with content moderation, then write a patch.
None.
Undecided.
None.
Closed: duplicate
11.0 🔥
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I believe this issue should be closed as a duplicate of #2969678: Integrate Media Library with Content Moderation →