Hi Patrick,

I'm not sure I follow the "current version = old version" bit. The current version always has the highest version nr. Can you explain how I can reproduce this step by step?

Peter

I'll see if I can recreate it in a test situation. I think it has something to do with adding an item that has the same name as another item. I'll try the following steps and see if this creates the problem:
1. Create New Item: TestItem
2. Make New Version.
3. Make 3rd Version.
4. Create New Item: TestItem
5. Delete Old TestItem Using WebDav (so it will be a soft delete)
6. Attempt to create New Version for TestItem
I think step 6 will succeed, but downloads will only occur on the version that happened before the delete. I know that there was a "soft-deleted" file with the same name. After I hard-deleted it, I thought the problem would go away (because I saw similar behavior before), but in this case the version is frozen at some older state.

Hi Patrick,

I indentified a caching issue in DMX which I tackled in DMX 5.2.3. Previously DMX allowed the browser to cache the file download. Since a new version has the same url as the old version, the browser thought it was the old file and never got the new one. Could this be your issue?

Peter

That could be the problem. I just downloaded the problem file today, and it seemed to be behaving correctly. I see that the Save Icon references a URL that is almost the same (but not quite). I.e. it has a "Method=Attachment" at the end of the query string. So it is likely that the browser cached the Old Version. Then when I used the Save link, I was able to get my "New Version". If I had uploaded a 3rd version of the file on that day, then I probably would never have been able to download that version (since both URLs would be cached).

So 5.2.3 will fix this problem? Are there any details of that problem discussed anywhere else? Thanks.

Hi Patrick,

DMX 5.2.3 should fix that issue, yes. No details are discussed anywhere AFAIK. I stumbled on this myself during testing and the fix was easy (didn't even need a recompile, instead added a line to download.aspx to disallow caching).

Peter