Access Restrictions for Maps Created from Unadvertised Contexts #11748#11752
Merged
allyoucanmap merged 1 commit intogeosolutions-it:masterfrom Dec 2, 2025
Merged
Conversation
1 task
allyoucanmap
approved these changes
Dec 2, 2025
Contributor
|
Successfully created backport PR for |
Contributor
|
@ElenaGallo please test on dev and let us know if we can backport on 2025.02.xx, thanks |
Contributor
|
Test passed, @rowheat02 please backport to 2025.02.xx. Thanks |
Member
|
backport already there @ElenaGallo @rowheat02 as we have the automation now. I'm going to review and merge |
tdipisa
pushed a commit
that referenced
this pull request
Dec 2, 2025
allyoucanmap
pushed a commit
that referenced
this pull request
Dec 2, 2025
dsuren1
added a commit
that referenced
this pull request
Dec 4, 2025
…request * commit 'a0da62e93ec7c7f9049c3343e410d4bea1db33c1': Update User Guide - Itinerary plugin (#11768) Fix the dashboard save, legend dependency and maximize issue (#11715) Update User Guide - Isochrone plugin (#11769) #11525 - Improve Maps in Dashboards (#11625) Update User Guide - Cascading search filter (#11766) Update User Guide - Show the current time and Null values options on Chart Widget (#11764) Fix #11754 - Moved assemply to bin-war module (#11761) Update User Guide - 3D Tiles imagery layers (#11758) Update User Guide - Update Tags menu section (#11756) Fix #11748 Access Restrictions for Maps Created from Unadvertised Contexts (#11752)
mahesh-wor
pushed a commit
to mahesh-wor/MapStore2
that referenced
this pull request
Dec 17, 2025
…Unadvertised Contexts (geosolutions-it#11752)
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.
Description
From the discussion and conclusion here, it was decided to make the non-advertised context's map clickable to open in the default viewer, along with showing a warning.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
#11748
What is the current behavior?
#11748
For a normal user, the user can not open a non-advertised context's map even if they have edit/view permission.
What is the new behavior?
The user can click and open a non-advertised context's map in the default viewer. Warning about permission will be as it is.

Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information
The warning message has also been updated to not include: "This resource can't be open"