Skip to content

fix: No password set for new mail shares - #44184

Merged
susnux merged 2 commits into
masterfrom
43919-fix-share-by-mail-password-enforce
Mar 14, 2024
Merged

fix: No password set for new mail shares#44184
susnux merged 2 commits into
masterfrom
43919-fix-share-by-mail-password-enforce

Conversation

@nfebe

Copy link
Copy Markdown
Contributor

Before the password is set on a new share, the computed property hasUnsavedPassword is used to check that this.share.newPassword is not undefined. Direct assignment without using Vue's this.$set makes it impossible for vue to detect that changes have happened on the share object. Hence the inreactivity.

This worked initially most likely because this.share.newPassword = await GeneratePassword() was executed before the computed properties where evaluated.

Resolves : #43919

Before the password is set on a new share, the computed property `hasUnsavedPassword`
is used to check that `this.share.newPassword` is not undefined. Direct assignment without
using Vue's `this.$set` makes it impossible for vue to detect that changes have happened on the share
object. Hence the inreactivity.
This worked initially most likely because `this.share.newPassword = await GeneratePassword()` was executed
before the computed properties where evaluated.
Resolves : #43919
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
@nfebe
nfebeforce-pushed the 43919-fix-share-by-mail-password-enforce branch from 84c078d to f9bef8fCompareMarch 13, 2024 23:59
@nfebe

Copy link
Copy Markdown
ContributorAuthor

/compile /

Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
@susnux

Copy link
Copy Markdown
Contributor

/backport to stable28

@susnux

Copy link
Copy Markdown
Contributor

/backport to stable27

@susnux
susnux merged commit e3b1a55 into masterMar 14, 2024
@susnux
susnux deleted the 43919-fix-share-by-mail-password-enforce branch March 14, 2024 12:05
@backportbot

Copy link
Copy Markdown

The backport to stable28 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable28
git pull origin stable28
# Create the new backport branch
git checkout -b backport/44184/stable28
# Cherry pick the change from the commit sha1 of the change against the default branch# This might cause conflicts, resolve them
git cherry-pick f9bef8f3 e3621b6d
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/44184/stable28

Error: Failed to push branch backport/44184/stable28: fatal: could not read Username for 'https://github.com': No such device or address


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

@susnux

Copy link
Copy Markdown
Contributor

/backport to stable28

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to reviewWaiting for reviewsfeature: sharing

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

[Bug]: share by mail: password not automatically set although passwords enforced

5 participants

@nfebe@susnux@artonge@AndyScherzinger@nextcloud-command