fix(provisioning): prevent silent save failure around master user#13076
fix(provisioning): prevent silent save failure around master user#13076tnxfi wants to merge 1 commit into
Conversation
With a master user set, saving the provisioning config could fail with no visible feedback when "use master password" was toggled off, or when the separator was left empty (the separator became required-but-empty, so the submit was blocked by native validation only). - Clear master user + separator when master password is disabled, so a value that just became hidden cannot block validation or silently survive. - Default the master user separator to "*" (Dovecot default) when a master user is entered, so the separator field is never required-but-empty. - Give the master password input a unique id per provisioning config (it was a hardcoded duplicate shared with the "add new config" form). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Thanks for the PR |
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
3 participants
For #12442
With a master user set, saving the provisioning config could fail with no visible feedback when "use master password" was toggled off, or when the separator was left empty (the separator became required-but-empty, so the submit was blocked by native validation only).
🤖 AI (if applicable)