xiaoxiaoflood / firefox-scripts

userChromeJS / autoconfig.js and extensions
Mozilla Public License 2.0
989 stars 85 forks source link

Libreoffice downloads failing #78

Closed mzso closed 3 years ago

mzso commented 3 years ago

Hi!

I tried to download Libreoffice files, from the official source: https://www.libreoffice.org/download/portable-versions/ https://www.libreoffice.org/download/download/

The downloads started allright, but when they reached 100% I got a file access error of sorts: kép

I tried downloading from elsewhere which completed successfully, so it's unlikely to be a local issue. Maybe it's related to that metalink feature, which I only ever saw with libreoffice downloads.

xiaoxiaoflood commented 3 years ago

I couldn't reproduce the issue. Right-clicked LibreOffice 7.1.2 Portable MultilingualStandard, then Save Link with dTa! One Click. Download started and ended flawlessly. Developer Edition 88.9b9, latest DTA!.

mzso commented 3 years ago

@xiaoxiaoflood commented on 2021. ápr. 23. 03:56 CEST:

I couldn't reproduce the issue. Right-clicked LibreOffice 7.1.2 Portable MultilingualStandard, then Save Link with dTa! One Click. Download started and ended flawlessly. Developer Edition 88.9b9, latest DTA!.

Well, I can only scratch my head. I still get the file access error when the download is supposed to be finishing.

xiaoxiaoflood commented 3 years ago

I managed to reproduce the issue. It was really a bug. This should be fixed now.

mzso commented 3 years ago

@xiaoxiaoflood Great! Thanks!

mzso commented 3 years ago

@xiaoxiaoflood commented on 2021. máj. 5. 05:07 CEST:

I managed to reproduce the issue. It was really a bug. This should be fixed now.

Okay. So now trying to try it I ran into issues. First I tried plain in-browser updates. I updated twice, but I'm still on the 2021.03.25 version. (Unfortunately I didn't pay attention to the version number before)

So then I tried from here manually, but I get a corrupted addon message and it won't get installed. Something's wrong.

xiaoxiaoflood commented 3 years ago

This is expected, recently I updated the legacy extensions loader in 5403e13336eff759162c115f37c50ecde32d3e25 for #79, so you need to manually update your chrome/utils folder. And don't forget to restart Fx forcing to clear startup-cache to force the browser to use the updated code.

mzso commented 3 years ago

@xiaoxiaoflood commented on 2021. máj. 8. 19:11 CEST:

This is expected, recently I updated the legacy extensions loader in 5403e13 for #79, so you need to manually update your chrome/utils folder. And don't forget to restart Fx forcing to clear startup-cache to force the browser to use the updated code.

I see, but will it work with the FF version that I'm on? (87) And will the older versions of addons from here work?

xiaoxiaoflood commented 3 years ago

Yes for both.