Sites: Implement Notification for (un-)publish in case Rollout config "Activation on Blueprint activation" or "Deaction on Blueprint deactivation" is in place for connected livecopies
Enhance the publish/unpublish process on blueprint pages with a warning if the rollout configuration "Activation on Blueprint activation" or "Deactivation on Blueprint deactivation" is in place.
If you have set this up for e.g. on livecopy root page there is no indicator available which shows the editor, maintaining the blueprint page, that with publish a blueprint page or unpublish this action takes also place on the livecopy. So, it could happen that accidentally a livecopy page goes on or offline.
Current/Experienced Behavior:
No hint for the editor once he publishes or unpublishes a blueprint page that on the connected livecopy page the same action is performed.
Improved/Expected Behavior:
If you publish or unpublish a blueprint page, the warning is shown that x liveopy page will also go on or offline. With that user is aware and can decide and check.
Environment Details (AEM version/service pack, any other specifics if applicable):
This has been reported to the engineering under the internal reference SITES-22126. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.