More in this section
Forums / Bugs & Issues / Replace a file in Documents & Files and there is no revision history of the actual file.

Replace a file in Documents & Files and there is no revision history of the actual file.

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
2 posts, 0 answered
  1. Firewater
    Firewater avatar
    5 posts
    24 Aug 2011
    18 Feb 2016
    Link to this post

    When I replace a file in the Documents & Files module and then publish it, there is a log of the revision history but only of the meta information . I however cannot access a previous version of the actual document file that was uploaded in an earlier revision.

    There is also a style "sfItemPreviewOverlay" over the"open the file" button preventing me from opening the document. If I however remove this, I can download the file but it is always the latest version and not the historical one that was present with that earlier version.

    I have tested this on a few implementations and it seems to be a consistent bug.



  2. Arnob Makhlaqur
    Arnob Makhlaqur avatar
    41 posts
    06 Sep 2017
    25 Feb 2016
    Link to this post
    Hello Alon,

    Please note that currently Sitefinity does not provide functionality to revert to a previous version of a document or file. There is a feature request lodged to implement it for the future releases. Here is the link to the feedback portal to track its progress and vote to increase its popularity:
    In addition to this, please note that the Revision history is working for Documents and files, however Sitefinity changes only the meta data for the document (e.g. Title), it does not revert to the old document that has been replaced. The concern is that if it saves the binary data for the different versions of the media content items (e.g. documents, images) the size of the database will grow rapidly and this is why the binary data of the document or the image is not saved for the previous versions. This is the reason why it is possible to access the meta data (e.g. Title) for the previous versions from the revision history but not able to open and view the file (the binary data) for previous versions.

    Arnob Makhlaqur
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal and vote to affect the priority of the items
2 posts, 0 answered