Unexpected behavior, files without a "current version" checkpoint in their history

[m4v]

I have noticed several files don't have any history in them, not even a "current version". This happens with files were their last time edited is at some point beyond the history length limit. I assume this is because the web interface doesn't search beyond this point.

The problem I'm seeing with this is that you can't revert a change if you edit an old file, despite changing it just a moment ago.

To reproduce:

1. Find a file that has no history (any file that was edited beyond the history limit)
2. Edit that file.
3. Now try to go back to the version it was before the edit. You can't because the history shows only one revision and that revision points to the current version of the file.

This behavior is unexpected.

A workaround is to temporally increase the history limit, this has two problems however:

1. It can be cumbersome if users aren't allowed to change it and need to contact the admin.
2. Most importantly, you need to be aware of this behavior! If you don't you will just assume that the data was lost because of a Seafile bug.

[killing]

Please provide more information:

1. Which version of Seafile do you use?
2. Have you set the history limit globally or in the library setting?

[m4v]

1. Seafile 11.0.12 CE
2. Limited globally in seafile.conf, setting the limit in the library setting is disabled.