Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support limited language access at block level #17322

Merged
merged 6 commits into from
Nov 5, 2024

Conversation

kjac
Copy link
Contributor

@kjac kjac commented Oct 21, 2024

Prerequisites

  • I have added steps to test this contribution in the description below

Description

This PR adds block level handling for users with limited language access.

It works the same as on document level: All block level changes are rolled back for the languages the current user does not have access to update.

Notice how the app setting Umbraco:CMS:Content:AllowEditInvariantFromNonDefault also affects this: If that setting is false, the current user must have access to the default language to make changes to invariant properties.

Testing this PR

Attempt to update block level variant content for languages which the current user does not have access to. Those changes should not be persisted.

You may need to use Swagger for a trustworthy result, as the back-office client is yet to be updated for this.

kjac and others added 5 commits October 21, 2024 12:20
…#17333)

* Remove obsolete ctor

* Add explanatory comment

* Set AllowEditInvariantFromNonDefault to true on tests

* Refactor to account for merge and default language

* Merge invariant values on top of the already merged values

* Add integration test to prove invariant merging

---------

Co-authored-by: kjac <kja@umbraco.dk>
@kjac kjac merged commit 2c04e37 into release/15.0 Nov 5, 2024
14 of 15 checks passed
@kjac kjac deleted the v15/fix/block-level-language-permissions branch November 5, 2024 05:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants