Skip to content

versioning documentation confusing and incomplete #1141

Description

@brainchild0

Currently the user manual (as well as the admin guide) does not give a user unfamiliar with versioning a clear indication of the features and their uses. Much of the discussion relates to automatic deletion of saved versions, without any explanation of how and when versions are created.

Questions that should be addressed are:

  1. When are new versions created? Is it automatic or manual? Is every edit and upload a new version?
  2. Can versions be accessed by or managed by a client?

For example, the text "Versioning creates backups of files" could read, "The previous version of any file in a Nextcloud server is saved every time it is edited on the server or uploaded by a client". That is, assuming I understand the facts correctly. Otherwise, the actual behavior would need to be clarified. I feel that I ought to understand at least that much after reading the manual.

See the forum discussion I opened earlier.

Activity

  1. MorrisJobke commented on Jan 15, 2019

    @MorrisJobke
    Member
  2. skjnldsv commented on May 14, 2026

    @skjnldsv
    Member

    The current text in user_manual/files/version_control.rst explains the expiration schedule and the 2-minute throttle, but never says what actually triggers a new version. A reader finishing the page still won't know whether versions are created on every upload, every edit, or only manually.

    Missing: a sentence explaining that a version is created whenever a file is uploaded or modified (via the web interface or a sync client), subject to the 2-minute minimum interval between versions.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions