Currently, if I have a node with a file on it and I save that node with a new revision and change the file, I now have in the system a node with 2 revisions and 2 separate files.

Now when I go to create a new node and I add a file, using the media library, I get 2 pre-existing files.

The problem with this is that technically there should only be one file.
This is because only one content revision actually exists, so only the file attached to the current revision should exist.
The file attached to the old revision is just there for history, so it can come back into play if ever the node is reverted to that revision.

This is a problem because if for example I am dealing with legally binding documents and I update the document, I definitely don't want people seeing the old document, and I don't want confusion with my content editors that could result in them accidentally using an old version of a document (especially if they have a similar or the same title).

I think that files should not be in the library if they exist only on unpublished revisions.

However, I know based on other discussions around the place, that not everyone would be happy with this.
There is also the issue that a file is manually uploaded at file/add and then used later on a node and then ends up being on an old revision.
Becuase this file was uploaded externally to that node should it live on?

It is possible that this could be a setting that site administrators could configure, so that for people who have sensitive documents can stop old-revision-only files from being in the library if they need to.

Alternatively, maybe it can just be configured into the library view and we can write doco for users to set it up this way if they need to.

Comments

Chris Matthews’s picture

Status: Active » Closed (outdated)

Closing this issue as outdated. However, if you think this issue is still important, please let us know and we will gladly re-open it for review.
sincerely,
- the Drupal Media Team