Batch updates must be run on all sites for the new entity configuration settings to take effect. I have been using the Batch Update menu item found under the Entity Usage settings, but I believe there is also a Drush command available for this.
Issues fixed:
Images in blocks can now be tracked.
Multiple rows of the same media item referenced in the media view have been eliminated.
The media view now indicates whether a media item is being used.
Issues that still exist:
The Entity Usage module currently has a behavior where every time a node or block is saved, it creates a new instance of tracking for the media item, even if no changes were made. The issue can be found in the entity_usage/src/EntityUsageTrackBase.php file. We can modify the function to change this behavior if desired. We can change the code to avoid relying on revision IDs, given that each edit action and a default "Save" button click will result in a new revision ID.
When a component containing a media item is created, the media view does not immediately reflect the change. This also occurs when the component is deleted. A cache clear or a cron job needs to be run for the changes to appear. We can try disabling the view's cache using views_post_update if that is the preferred approach.
Closes #552
Issues fixed:
Issues that still exist:
The Entity Usage module currently has a behavior where every time a node or block is saved, it creates a new instance of tracking for the media item, even if no changes were made. The issue can be found in the entity_usage/src/EntityUsageTrackBase.php file.
We can modify the function to change this behavior if desired. We can change the code to avoid relying on revision IDs, given that each edit action and a default "Save" button click will result in a new revision ID.
When a component containing a media item is created, the media view does not immediately reflect the change. This also occurs when the component is deleted. A cache clear or a cron job needs to be run for the changes to appear. We can try disabling the view's cache using views_post_update if that is the preferred approach.