New file feature: change logs

[LHammonds]

Yeah, it seems to be an issue if you do the following:

 

Upload a file with a specific version (0.8.1 in my case).

Make a changelog for that version.

Delete the old file (because I mis-uploaded it), and re-upload the file with the same version number.

 

This breaks the changelog link.

FYI - It would still be a good idea even in that scenario to increment your version number. Those that have downloaded 0.8.1 could see that there is a different file 0.8.2 and see in the change log that it is the same mod but a fixed archive.

[SomeWelshGuy]

Yeah, it seems to be an issue if you do the following:

 

Upload a file with a specific version (0.8.1 in my case).

Make a changelog for that version.

Delete the old file (because I mis-uploaded it), and re-upload the file with the same version number.

 

This breaks the changelog link.

FYI - It would still be a good idea even in that scenario to increment your version number. Those that have downloaded 0.8.1 could see that there is a different file 0.8.2 and see in the change log that it is the same mod but a fixed archive.

Yeah I agree. But it was up for 2 seconds, the file was set to hidden so no-one downloaded the file, so on this occasion I didn't find it really necessary.

[LHammonds]

Yeah I agree. But it was up for 2 seconds, the file was set to hidden so no-one downloaded the file, so on this occasion I didn't find it really necessary.

Good point but another good counter point is the way this distributed network is setup. I have seen in the past where you can upload a file with a specific name, then later delete it and try to re-upload it only to get an error. I cannot remember the exact scenario but it was related to whether the file was over 2 MB and was sent to the various file mirrors. The deletion was not fan'd out to the distributed servers before the re-upload happened and it caused contention between the new file process and the distributed deletion process. This may have been accounted in the code since then but it was related to deletion of a file and re-upload of a file with the same name on the same mod page (different mod pages use a different file key which will never conflict with any other upload page).

[jaime74]

Good point but another good counter point is the way this distributed network is setup. I have seen in the past where you can upload a file with a specific name, then later delete it and try to re-upload it only to get an error. I cannot remember the exact scenario but it was related to whether the file was over 2 MB and was sent to the various file mirrors. The deletion was not fan'd out to the distributed servers before the re-upload happened and it caused contention between the new file process and the distributed deletion process. This may have been accounted in the code since then but it was related to deletion of a file and re-upload of a file with the same name on the same mod page (different mod pages use a different file key which will never conflict with any other upload page).

 

Just for clarification, to avoid confusion, and to avoid going off-topic:

In my case, I did not re-upload an existing file with the same version number, but a completely new file!

So I think that the change log issue is not simply related to the situation SomeWelshGuy described (though I agree with him that it might be the same bug, and I also agree with LHammonds that re-uploading is not a good practice! ;))

It just wanted to point to the fact that the change log issue should be solved somehow to raise acceptance of the change log feature :whistling:

 

P.S.: @pintocat: I am still looking forward to your confirmation - can you reproduce the error using the links I posted below?

[pintocat]

jaime74, both changelog links on both pages work fine for me.

[jaime74]

jaime74, both changelog links on both pages work fine for me.

Ok, thanks!

So this means: There are some people for whom it works, and some (like me or Riven1978 and maybe also SomeWelshGuy) for whom it doesn't.

 

So what else can I do? How to proceed with this? Apart from trying different browsers and making sure that there's no popup blocker (as described earlier), I have no more idea, being left alone with this problem :(

So (given that nobody of the "makers" will pick up this issue and take care of it), I'll probably have to give up once more. This was my second attempt now to use this change log, so I'll finally leave it be and switch back to the good old readme.

[Dark0ne]

I think I've fixed the issue with the change log links for specific versions. The issue was when you used letters and numbers together in your versioning, hence why some people said it worked while others said it didn't.

[jaime74]

(post deleted, because it was an accidental double-post)

[jaime74]

I think I've fixed the issue with the change log links for specific versions. The issue was when you used letters and numbers together in your versioning, hence why some people said it worked while others said it didn't.

Thanks for your answer, Dark0ne!

 

I am not sure whether I understand it correctly, though: By "fixed the issue", do you mean that using mixed letters and numbers should work now, or should it not. If the latter is true, I can simply change my version number from "2.6a" to "2.6.1", that's not a problem. But I'd like to be sure before doing so, because changing version numbers in the middle of everything will cause some confusion for the users of my mod.

 

Furthermore, given that mixed letters and numbers are not supported, I think that it could be helpful to have a comment about it in the change log editing form.

 

Anyway, I am very glad that you're having a look into this! :thumbsup:

[Dark0ne]

It should be fixed for letters and numbers; give it a test. It works for me!