fix(UserPlugin): Don't search for displayname when restricted#61982
Open
DerDreschner wants to merge 1 commit into
Open
fix(UserPlugin): Don't search for displayname when restricted#61982DerDreschner wants to merge 1 commit into
DerDreschner wants to merge 1 commit into
Conversation
Assisted-by: ClaudeCode:claude-fable-5 Signed-off-by: David Dreschner <david.dreschner@nextcloud.com>
Contributor
Author
|
/backport to stable33 |
Contributor
Author
|
/backport to stable34 |
DerDreschner
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.
Summary
In December 2025, @juliusknorr implemented the feature to block full matches on the display name when using the share API (PR #57041). That feature was unintentionally being dropped on the rewrite of the
UserPluginby @susnux, leaving a non-functional toggle in the UI (PR #57511).This issue is being fixed with this PR, re-adding the necessary checks on backend side as well as adding integration tests to prevent that from happening in the future.
Checklist
3. to review, feature component)stable32)AI (if applicable)