fix: Fix restore default pages option - EXO-88526 - eXIP7.3.0.9#545
Merged
Conversation
|
MayTekayaa
changed the title
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
1 participant
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.
Prior to this change, "Restore default pages" used
MERGEimport mode, which only adds or updates pages and navigation — it never removes anything, so a manually created page, or a navigation node produced by copy/paste, stayed in place after a restore.This change switches the restore action to the new
RESTORE_DEFAULTSimport mode (introduced in the companion gatein-portal change) instead: it behaves likeMERGEfor anything outside a default page (so independent custom content at the site's navigation root is always preserved), but destroys orphan nodes nested inside a default page/section (e.g. a page added, pasted, or left behind inside an existing section) — restoring defaults without the collateral damage that madeOVERWRITEunsafe.