Slow Download button doesn't do anything

[brk279]

19 minutes ago, Pickysaurus said:

You're right, if no events are attached to the button it will not work. However, those events are attached using JavaScript which is often blocked by browsers being a bit overzealous on privacy/security. It may also be that something got updated as part of a routine security upgrade which is now breaking it for your specific browser.

I have already stated that this is NOT a browser issue, the browser was working fine two days ago and there hasn't been any updates to it or to the OS. Potential issue due to updates to addons are also eliminated when I ran the browser in troubleshooting mode with a new profile and no tracking protection. Moreover, the two browsers receive the same exact javascript code sent by the server (yes, I have compared them) excepting a few functions with seemingly randomized names.

19 minutes ago, Pickysaurus said:

It's safe to say if this were a problem on our end, many more users would be reporting it. Unfortunately, something specific you set up is causing the problem. 

May sound strange but the issue could be related to Cloudflare. This thread was started at Nov 7th but I didn't have any issues at the 18th, which may indicate whatever is causing it is slowly propagating, which leads me to think that it may be an issue with Cloudflare. "Why does a newer browser work then?" you may ask, Cloudflare is known to cause arbitrary issues with browsers, which I have experienced in the past, not so arbitrary actually they seem to have certain browser lists (user agent) that they refer to which are occasionally updated and causes issues with certain versions of browsers.

19 minutes ago, Pickysaurus said:

I'm afraid we can't support outdated browsers - it would be a very poor use of our limited developer time to test every possible variant of every browser. We prioritise support for the latest versions of the most popular browsers used by our community in their default configuration (no add-ons or optional settings enabled). The list of browsers is as follows:

• Google Chrome
• Mozilla Firefox
• Microsoft Edge
• Opera
• Yandex
• Chrome Mobile
• Safari Mobile

I would recommend that you at least use the latest Firefox to avoid problems like this in future.

It's not that simple I'm afraid, for reasons I have stated in the reply to the post above. If I were able to use the most up to date FF, I would be using it right now. I have a newer version that seems to work for now but FF ceased support for my OS so it also won't last forever. Updating the OS is out of question because then I would have to throw away the whole system to do that, so I would rather cease using Nexus at that point.

Edited yesterday at 02:42 PM by brk279

[aquatko]

Same issue as I have. 2 days ago - all good. Today - site menu does not expand and slow download button does not work.

 

[Pickysaurus]

11 hours ago, aquatko said:

Same issue as I have. 2 days ago - all good. Today - site menu does not expand and slow download button does not work.

 

Please read the above, that screenshot has nothing to do with this issue. 

Unfortunately, this is a problem in your setup. Make sure you use the latest browser version and disable any addons. 

[brk279]

16 hours ago, aquatko said:

Same issue as I have. 2 days ago - all good. Today - site menu does not expand and slow download button does not work.

 

The screenshot shows again that the button has no associated events which explains why it's not working. The issue has nothing to do with our setup, people who have posted about the issue in this thread don't even seem to use the same browser, some say it's Chrome others mention Firefox, not to mention different versions, and the fact that these very same browsers were working fine before the issue and stopped working all of a sudden, clearly indicates a change in the code on Nexus side. We're not in a position to debug the code, whoever wrote it needs to look into it and find out why the script is failing to attach events to the button. I however doubt that anyone will.

EDIT: The inline script which I posted above looks identical to the one for the working button, so that's probably not the culprit. Must be an off-site script causing the issue. If I knew the server-side process, the prerequisites for that script to work I could perhaps figure out a way to fix it. Perhaps this piece of code or what follows it may be the culprit, cause I don't get this error in the newer browser, looks like an external script on Nexus:

Uncaught TypeError: AbortSignal.timeout is not a function
    callNotificationService https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:16951
    getUnreadCount https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:16922
    updateLocalStorageFromServer https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:16956
    <anonymous> https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:16959
    dispatch https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    handle https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    add https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    ja https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    each https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    each https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    ja https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    on https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    b https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    <anonymous> https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:16959
    i https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    fireWith https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    ready https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    J https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    promise https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    <anonymous> https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    <anonymous> https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    <anonymous> https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
BBoC-365d698bf2b50df99b993738c9d67fd9.js:16951:295
    callNotificationService https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:16951
    getUnreadCount https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:16922
    updateLocalStorageFromServer https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:16956
    <anonymous> https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:16959
    dispatch https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    handle https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    (Async: EventListener.handleEvent)
    add https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    ja https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    each https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    each https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    ja https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    on https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    b https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    <anonymous> https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:16959
    i https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    fireWith https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    ready https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    J https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    (Async: EventListener.handleEvent)
    promise https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    <anonymous> https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    <anonymous> https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6
    
<anonymous> https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js:6

If this is indeed what's causing the problem then it's a code compatibility issue, like I said before. Older browsers don't seem to support whatever it is doing. For people who've been experiencing this problem I would advise checking the browser console for this particular error or similar script errors.

 

Edited 49 minutes ago by brk279

[Pickysaurus]

I've re-tested this on both the latest version of Firefox and Chrome:

Firefox 132.0.2 (64-bit) on Windows

 

Chrome 131.0.6778.86 (Official Build) (64-bit) on Windows

 

Both of these work as expected. There's nothing more I can offer in the way of assistance at this point I'm afraid. If this were an issue on our end, we'd definitely have had more reports of this by now. You've already said yourself you're intentionally using an outdated copy of Firefox which we don't support anymore. The only solution I can suggest is to use the latest version or use a different browser. 

I've been here for quite a few years now and I can say with confidence whenever this button has stopped working it's usually down the user's personal setup. While the resulting symptom is the same (the button doesn't work), the root cause can often by different. There are so many ways that browser settings, add-ons or versions can break the website and we can't possibly cater for every combination. 

If you do work out what is breaking the page for you, please let me know as I'm definitely curious to know what happened. 

Ultimately, until I can confirm this is happening in a browser we support and can replicate it all I can do is give you our advice/recommendations to fix your own setup. 

[brk279]

My prime suspect is this script file, which seems to be hosted by Cloudflare and according to the HTTP response header it seems to be modified last on Wed, 20 Nov 2024 10:31:03 GMT, the very same date this problem started on my end. Cloudflare has many different servers and it's normal for people to experience the problem at different times, especially if they reside in different locations/countries.

https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js

 

Edited 18 minutes ago by brk279

[Pickysaurus]

11 minutes ago, brk279 said:

My prime suspect is this script file, which seems to be hosted by Cloudflare and according to the HTTP response header it seems to be modified last on Wed, 20 Nov 2024 10:31:03 GMT, the very same date this problem started on my end. Cloudflare has many different servers and it's normal for people to experience the problem at different times, especially if they reside in different locations/countries.

https://www.nexusmods.com/Contents/Scripts/BBoC-365d698bf2b50df99b993738c9d67fd9.js

 

I will ask if this was modified, however, BBoC stands for "Big Blob of Code" and it represents a generated file that is created when we release a new build of the website. The edit date may just be the last time the site was deployed rather than when any actual change happened. A highly possible scenario is that your browser doesn't support some of the JavaScript syntax in this file (due to it being out of date). 

[brk279]

 

1 minute ago, Pickysaurus said:

The edit date may just be the last time the site was deployed rather than when any actual change happened.

Well, the deploy date matters to me because that's when I started having the issue, the actual change may have been earlier but I wasn't affected by it.

1 minute ago, Pickysaurus said:

A highly possible scenario is that your browser doesn't support some of the JavaScript syntax in this file (due to it being out of date). 

Yes, very likely, especially considering the error I posted above.