Download always delivers old package instead of new one

[ulrich1234]

Hello,

 

I updated my Wizardry 8 mod on August 1st, and today (August 2nd) I updated the included Readme.txt and uploaded the package again under the same name and version.

 

But now when I try to download the mod now, it always downloads the file from August 1st, but not the one from August 2nd. I can also set a different name and higher version after uploading the package - but it still downloads the package from August 1st.

 

What's wrong here?

[ulrich1234]

I somehow got it working after taking all the following steps:

 

I changed the package name before uploading. Changed the version number in the Files page after uploading to something significantly higher (from 2.01 to 2.1). Changed the version number in the Documentation page to that value. Changed the version number in the Description page to that value. I also deleted all cache, cookies, logindata from my internetbrowser regarding the Nexus website before doing these steps. No idea if that had any influence on it, but I've read in some older thread that someone experienced similar issues, apparently bound to his computer only, possibly because of a cache problem.

And now it's finally working and downloads the most recent package.

 

Since I did all these steps at once I cannot pinpoint exactly which of the steps was the reason it works now. I also think I tried the most important steps (changing the packagename and version number) previously as well and it didn't work. Anyway, I'm glad it works now.

Edited August 3, 2020 by ulrich1234

[Pickysaurus]

I believe changing the file name was the fix here. It's possible the first version you uploaded was stick in the uploaders temporary storage or something. Renaming the file is the best way to "start fresh" when uploading an update soon after the original.

[ulrich1234]

Hello, I have the same problem again and it seems to be an issue on the Nexusmods server- and filemanagement:

 

 

I re-uploaded my mod ("Wizardry 8 Simpler and Faster") a couple of times with the same packagename, which worked fine for like 10 times, but then the old issue happened:

The download delivered an old package instead of the new one. And it's always the same old package, regardless how many new packages I upload. The download seems completely stuck on that package.

 

 

I then deleted my mod on nexusmods and created a new modpage (under the same name and package names). But then it also delivered the old package from the supposedly deleted mod!

 

Current state of affairs:

1) I uploaded a fresh new package containing a Readme file with the text "Version 1.0"

2) When I download the package, it delivers a package containing a Readme file with the text "Version 2.7" (from the supposedly deleted mod)

 

 

How can it be, that the download delivers a package from a supposedly deleted mod? This feels kinda messy. It also feels like a security issue, when the server can deliver a package which comes from another mod (just because it has the same filename).

Edited December 7, 2020 by ulrich1234

[ulrich1234]

In respect to my previous solution (which was to rename the package to something else before uploading) I can however affirm that this also worked in this case. Nevertheless it's annoying because the upload process makes you think that the package name can stay the same - which is only partly true. It can work successfully for a few couple of uploads, but then it can also get stuck.

 

For anyone else having this problem: It seem like the best way to avoid this bug is to always rename the package name, even for the slightest change you make to it. Maybe with a postfix like "v1.001" or so.

 

Regardless of that I consider the filemanagement buggy and that it should be addressed by the nexusmods platform developers.

[Pickysaurus]

You might be confusing things by uploading the same file name over and over. After each upload completes the file has to propagate over our CDN network, which can take a little while.

 

I'm not sure exactly what the cause is but it seem you may be the only person (as far as I know) with this problem.

[ulrich1234]

I'm not confusing anything here. These are the steps I generally took for any new upload:

 

1) First I did "Delete" or "Upload new version" on the old package.

2) Then I uploaded a new package (same name but slightly changed contents), and saved it.

3) In another browsertab I opened the Files-Section (for visitors) to check when the new package was *really* available.

4) The Files-Section mostly said something like "the file is being processed to the server", and also had no download button anymore.

5) After some minutes I refreshed that browsertab to check again.

6) Then the Files-Section listed the new package, and the download button was there again.

7) Then I downloaded the package. The package also had a higher number in its name (the long number generated by your system).

8 ) Then I opened the downloaded package, and a couple of times it was in fact the package with the new contents.

9) BUT after some more uploads (like 10 more or so), the downloaded package contents were suddenly from an older upload (and despite having a higher generated number in its packagename). And even worse, it remained stuck on that for any further upload attempts.

 

Hence the issue seems to be on the side of the nexusmods platform and not mine. It's like the filemanagement system gets mixed up when you upload a package with the same name (but slightly changed contents) multiple times in a row. The only solution from my side is the previously mentioned workaround (which is to always change the packagename before uploading).

Edited December 7, 2020 by ulrich1234

[Pickysaurus]

How quickly are you doing these uploads? Would you say it's within minutes, hours, days?

 

You're probably right about it being a quirk on our end, but I'll have to see if the devs can lock down a cause. In the meantime, the file rename thing works :)

[ulrich1234]

It was like 5-10 uploads within an hour or so when it happened. So quite a short timeframe.

 

The only thing I can think of is (after some investigation in the forums), that I exceeded the API-Rate request limit (100 requests per hour) on the nexusmods platform when repeatedly changing things. And then maybe a specific modpackage was "locked" by the server and ignored any further uploads. I'm just guessing here. This assumption however wouldn't explain, why I could circumvent the issue by uploading packages with a different name. After all the restrictions from the API-Rate should still be active. Or why the "locked" package still couldn't be replaced a day after.

Edited December 8, 2020 by ulrich1234

[Pickysaurus]

It was like 5-10 uploads within an hour or so when it happened. So quite a short timeframe.

 

The only thing I can think of is (after some investigation in the forums), that I exceeded the API-Rate request limit (100 requests per hour) on the nexusmods platform when repeatedly changing things. And then maybe a specific modpackage was "locked" by the server and ignored any further uploads. I'm just guessing here. This assumption however wouldn't explain, why I could circumvent the issue by uploading packages with a different name. After all the restrictions from the API-Rate should still be active. Or why the "locked" package still couldn't be replaced a day after.

 

It's a good theory, but I'm not sure it's the right one. Your API limits only apply to interaction directly on the API. If you're using the site it shouldn't be consuming any requests.