Don't miss out Virtual Happy Hour this Friday (April 26).
Try our conversational search powered by Generative AI!
AI OnAI Off
Don't miss out Virtual Happy Hour this Friday (April 26).
Mar 27, 2020
May 15, 2020
CMS Core
Closed, Fixed and tested
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"