As designed Old version is downloaded

[Sadik B]

Steps to reproduce:

• Create a File Resource, keep version string blank.
• Post Resource Update, upload a new file, keep version string blank.
• Click Download on the resource, old file is downloaded.

Basically since the version string defaults to date, doing this on same day will result in this bug.

 

[Chris D]

The explanation text of the version string field actually explains this will happen:

This is the new version name for your resource, such as 1.0. You may not alter this once you have saved it. If you do not enter this, a new version will not be posted.

This allows you to release an update for a resource, without actually changing the current version to be downloaded.

 

[Sadik B]

Ah I see... But this also creates the situation where the old file is downloaded in spite of having uploaded a new one. Which is a more likely use case scenario?
a> users not entering version strings in their uploads or
b> someone wanting to release an update without changing file.

I think a> is much more likely to happen. If the user uploads a new file, the version string default for the resource update should change.

Anyways, i will work around it...

 

[Chris D]

Actually in the current situation the file is not attached and is later discarded. A new version record is not created.

I do understand your point, though.

But, as it stands, this is working as designed.

For now the simplest workaround is to just specify the same version string rather than leaving it blank.