Skip to content

Fix folder naming not using capabilities renamer #3566

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

mpivchev
Copy link
Collaborator

@mpivchev mpivchev commented Jul 1, 2025

Naming a folder A* where the "*" is not part of the forbidden characters coming from capabilities, would cause the folder to be named A instead.

Fixed by making the folder creating take into account forbidden characters from capabilities instead of generic forbidden characters.

Test creating a folder named A* without WCF ("*" allowed) (Christine account can be used) and check if folder is created successfully and files can be added.

Test a server with WCF enabled ("*" is not allowed) (internal instance can work) and check if you get an error during naming. "Save" button should be disabled.

@mpivchev mpivchev requested review from marinofaggiana and i2h3 July 1, 2025 11:06
Signed-off-by: Milen Pivchev <[email protected]>
@i2h3
Copy link
Contributor

i2h3 commented Jul 2, 2025

Please add instructions how to test, though.

@mpivchev
Copy link
Collaborator Author

mpivchev commented Jul 3, 2025

Please add instructions how to test, though.

Added

Signed-off-by: Milen Pivchev <[email protected]>
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.

2 participants