DefaultContentVersionRepository should not invalidate cache for items it does not own

Found in

EPiServer.CMS.Core 10.0.1

Fixed in

EPiServer.CMS.Core 11.15.1

Created

Mar 27, 2020

Updated

May 15, 2020

Area

CMS Core

State

Closed, Fixed and tested


Description

DefaultContentVersionRepository listens to the content events and invalidates version listings based on those events. But it does so for any content, not just content in the default content provider. This causes lots of invalidations for keys that don't exist. For example, updating content in Commerce causes validations of four unused keys (because it triggers both on the Publishing and Published events):

"EP:CV:NOLink"
"EP:ContentVersion:2__CatalogContent"
"EP:CV:NOLink"
"EP:ContentVersion:2__CatalogContent"