[Bug]: File Versioning Not Working As Expected
Open
@yemkareems is already working on this.
Since Jul 12, 2024.
0. Needs triage
27-feedback
bug
feature: versions
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
A different file version is not saved for each change made to the file. Therefore the user cannot use different file versions. For example, the user created a file and changed that file every day, at the end of 30 days, when we look at the versions of that file, 30 different file versions do not appear.
Note: "versions_retention_obligation" -> "disabled"
Steps to reproduce
- Create file
- Edit that file in different time periods such as 1 min later 1 hour later 2 hours later 3 hours later and 3 days later
- You can't able to see all file versions
Expected behavior
The file version should be saved according to the desired range.
Installation method
None
Nextcloud Server version
27
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?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.