Skip to content

Conversation

@backportbot
Copy link

@backportbot backportbot bot commented Jul 23, 2025

Backport of #54055

Warning, This backport's changes differ from the original and might be incomplete ⚠️

Todo

  • Review and resolve any conflicts
  • Amend HEAD commit to remove the line stating to skip CI

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@backportbot backportbot bot added this to the Nextcloud 30.0.14 milestone Jul 23, 2025
We need to save the previous state - here the password - so that if the
update fails we can revert the shown state.
This happens e.g. if you have the password policy app and try to add an
unsecure password.

To reproduce (with password policy):
1. Create new link share
2. enable password protection
3. use insecure password like `1234`
4. save share

Now you see that the update failed, but the password protection is still
enabled. This happened because `password` and `newPassword` were
misused. `password` was already set when `newPassword` was not saved so
we could not know to what we need to reset when the update failed.

Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
@susnux susnux force-pushed the backport/54055/stable30 branch from 3c392aa to 98b6ff2 Compare July 23, 2025 16:32
@susnux susnux marked this pull request as ready for review July 23, 2025 16:32
@susnux
Copy link
Contributor

susnux commented Jul 23, 2025

/compile

Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
@susnux susnux merged commit 7017816 into stable30 Jul 23, 2025
123 of 128 checks passed
@susnux susnux deleted the backport/54055/stable30 branch July 23, 2025 18:26
@nextcloud-bot nextcloud-bot mentioned this pull request Aug 5, 2025
5 tasks
@nextcloud-bot nextcloud-bot mentioned this pull request Sep 25, 2025
2 tasks
@blizzz blizzz mentioned this pull request Oct 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants