Merge Admin Site IMPV - EXO-88912- eXIP7.3.0.9 - #551
Open
MayTekayaa wants to merge 4 commits into
Open
Conversation
Prior to this change, "Restore default pages" used `MERGE` import 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_DEFAULTS` import mode (introduced in the companion gatein-portal change) instead: it behaves like `MERGE` for 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 made `OVERWRITE` unsafe.
…#546) Prior to this change, the topbar "Edit navigation" button always opened the navigation tree of whichever site was currently being browsed, regardless of which site actually owned the current page's navigation node. Since global navigation nodes are merged into every site's menu, a page reachable only through the global site's navigation (e.g. Settings, Profile) — while browsed under another site such as dw — opened that site's navigation editor instead of global's. This change resolves the actual owning site of the current page's navigation node (via eXo.env.portal.selectedNodeId) before opening the drawer, falling back to today's behavior whenever no node is selected or the lookup fails. A page listed only in global now opens global's navigation for editing; a page listed in both a site and global (e.g. People, in both dw and global) still opens that site's own navigation, not global's.
…0.9 (#547) Prior to this change, the "Restore Layout" option in the site navigation menu was never displayed. This change will display the option only for default/product pages by relying on the new `canRestoreLayout` flag: the backend fills it while building the navigation tree (`RestEntityBuilder`/`SiteLayoutRest`), and the menu (`NodeItemMenu.vue`) shows the option only when the page is editable and restorable, so it appears for product pages and stays hidden for customized ones.
…7.3.0.9 (#548) This change will review move Up/ move on item in the navigation.
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.
No description provided.