Skip to content

Conversation

@nfebe
Copy link
Contributor

@nfebe nfebe commented May 14, 2025

When a share includes a note, ensure the note checkbox is checked and the note is displayed when reopening the share sidebar.

Fixes: #52794

@nfebe nfebe force-pushed the fix/52794/share-advanced-settings branch from 7af74d5 to ced4257 Compare May 14, 2025 16:21
@nfebe
Copy link
Contributor Author

nfebe commented May 14, 2025

/compile

@nfebe nfebe requested review from artonge, skjnldsv, susnux and szaimen May 14, 2025 16:22
@nfebe nfebe self-assigned this May 14, 2025
@github-project-automation github-project-automation bot moved this to 🏗️ In progress in 📁 Files team May 14, 2025
@nfebe nfebe marked this pull request as ready for review May 14, 2025 16:22
@nfebe nfebe requested a review from a team as a code owner May 14, 2025 16:22
@nfebe nfebe enabled auto-merge May 14, 2025 17:03
nfebe and others added 3 commits May 14, 2025 22:39
When a share includes a note, ensure the note checkbox is checked and the note is
displayed when reopening the share sidebar.

Fixes: #52794.

Signed-off-by: nfebe <fenn25.fn@gmail.com>
If a share note is present, the advanced settings should expand automatically,
without the user needing to click.

Signed-off-by: nfebe <fenn25.fn@gmail.com>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
@nfebe nfebe force-pushed the fix/52794/share-advanced-settings branch from d2c11c7 to 86c591b Compare May 14, 2025 20:39
@nfebe nfebe merged commit 158b3ef into master May 15, 2025
143 of 149 checks passed
@nfebe nfebe deleted the fix/52794/share-advanced-settings branch May 15, 2025 05:49
@nfebe
Copy link
Contributor Author

nfebe commented May 15, 2025

/backport to stable31

@nfebe
Copy link
Contributor Author

nfebe commented May 15, 2025

/backport to stable30

@nfebe
Copy link
Contributor Author

nfebe commented May 15, 2025

/backport to stable29

@backportbot
Copy link

backportbot bot commented May 15, 2025

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

# Switch to the target branch and update it
git checkout stable29
git pull origin stable29

# Create the new backport branch
git checkout -b backport/52813/stable29

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 63cf3f53 7810a900 86c591ba

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/52813/stable29

Error: Failed to check for changes with origin/stable29: No changes found in backport branch


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

@AndyScherzinger
Copy link
Member

@nfebe backport to 29 failed, see #52813 (comment)
Did you do a manual backport?

@nfebe
Copy link
Contributor Author

nfebe commented May 27, 2025

I tried backporting from 30, but it failed as well. I’ll try again, and if it still doesn’t work, I’ll resort to a manual backport as a last step.

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

Projects

Status: 🏗️ In progress

Development

Successfully merging this pull request may close these issues.

[Bug]: Note field hidden in share sidebar when re-opening share

7 participants