[Backport 2025.01.xx] Fix #11404 Problem with user permissions still involving the "Save As" (#11408)#11410
Merged
tdipisa merged 1 commit intogeosolutions-it:2025.01.xxfrom Aug 28, 2025
Conversation
…ng the "Save As" (geosolutions-it#11408) * Fix geosolutions-it#11404 Problem with user permissions still involving the 'Save As' * add comment
1 task
tdipisa
approved these changes
Aug 28, 2025
Member
|
@ElenaGallo please verify in QA once deployed and let me know. |
Contributor
|
@allyoucanmap On QA, for a user with edit permissions, the permission added in the permissions tab is not visible and cannot be edited. save-as.mp4 |
Contributor
Author
|
@ElenaGallo @tdipisa the specific map showed in the video has the |
1 task
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
4 participants
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
This PR adds logic to exclude the
ownerattribute while saving a resource.Permission requests are failing if the
ownerattribute is different from the current editing user (see related issue #4634)Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#11404
What is the new behavior?
Removed the
ownerattribute from cloned resourcesBreaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information