-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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]: Original file version of Word .docx file corrupt after restoring it from file version history; file versions disappear #49125
Comments
We managed to reproduce this today and noticed that the file size is not properly updated in some cases. This only happens with encryption it seems, tested today on stable29 Steps to reproduce
|
Interesting, I can also reproduce with text, after restore of version 3 the size is also wrong but there I get a BadSignature exception, no such exception when downloading over webdav for the other case
In both cases manually fixing the version in the filecache works, so for some reason we do not restore the version properly in those cases. |
This might be a case where the version retention has cleaned up versions in the mean time, the UI is not refreshing and when you click the restore button the version has been removed and therefore cannot be restored. |
Made me think of #49903 but stable29 was not affected by that. |
This should be resolved by #50299 |
Bug description
When the original version of a .docx file is restored from version history, downloaded and opened in MS Word, there is an error about the file being corrupted. It can then be restored easily in MS Word.
Further Investigation:
I created a few additional versions of the original file by slightly modifying the content and uploading it using the same name an location again. I randomly restored different versions, downloaded them and compared their hashes.
Observations:
I repeated the procedure for a new word file created with Word 2016 to check if my original file was causing the issues:
Steps to reproduce
Expected behavior
The original version of the file can be opened in MS Word without errors.
The restored version has the same file hash as the original version.
Nextcloud Server version
30
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
Encryption is Enabled
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: