-
Notifications
You must be signed in to change notification settings - Fork 807
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
[Bug]: Release 3.12.7 and V3.13.x - Excel says "Overwrite changes" #6933
Comments
Same here with nextcloud 28.0.6 and nextcloud desktop 3.13.3 on windows 10. |
Hi |
Still current with version 3.14.3. |
Yes |
Also with 3.15 |
If you have issues with renaming files or moving files or folders, please do not post it here and report it separately such that one has a chance to investigate your report and maybe solve a bug for all. |
There already is an issue for that (#6151 ). Because I had both issues, I thought maybe there was a relation between the two issues. |
I have som additional info: the 'overwrite' message only shows the first time you want to save after opening an excel file. If you don't close the file, and save it later again, the message does not come up again. |
Bug description
Steps to reproduce
Save Excel file
Expected behavior
no message
This is a known bug which is normally resolved by #6212
When we look at the PRs, we see:
Does the red cross mean that this PR is not pushed in the code of this release? (I don't know Github too well)
Otherwise, if this PR is included in the code of this release, this does not correct this problem.
Which files are affected by this bug
Excel
Operating system
Windows
Which version of the operating system you are running.
Windows 11
Package
Official SNAP package
Nextcloud Server version
27.1
Nextcloud Desktop Client version
3.12.7
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: