Add (un)publishing details to TreeChange notifications#17757
Merged
Conversation
Member
|
Looks good, tests good 🚀 |
Zeegaan
pushed a commit
that referenced
this pull request
Dec 9, 2024
(cherry picked from commit 404a62a)
Member
|
Cherry picked for 13.6 🚀 |
This was referenced Sep 28, 2025
This was referenced Oct 6, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prerequisites
Description
This PR adds additional (un)publishing info to
TreeChange(specifically which cultures were affected by the operation), to be consumed byContentTreeChangeNotificationhandlers.This additional info is also added to the
ContentCacheRefresherNotification, to make it available in a load balanced scenario.For invariant content, the wildcard (
*) is used to communicate the affected cultures.Testing this PR
Add a notification handler to
ContentTreeChangeNotificationandContentCacheRefresherNotification, and verify that thePublishedCulturesandUnpublishedCulturesproperties match any (un)publishing operations performed in the backoffice.Here's a notification handler 😄