PLEASE put up all FDM and Firefox problems here! 373f3l

[boyumeow]

https://yadi.sk/d/hlf1lfC8mKU58
Above website from Yandex.Disk, while ing using FDM, name is correct as "mpc-be", but from browser (firefox58.0.1 64bit) is raw file names (very long names) rather than "mpc-be". Disable of the extension 3.0.6, browser ing correctly as "mpc-be". I'm sorry if I'm not explaining in good English.
Sorry for repeating this as I wrongly reported on the other thread "FDM 5.1", and no way to delete that.
Thanks and have a good everyday.

With latest extension 3.0.11 (enabled), my above report is solved, but found 2 bugs related to without using FDM to .
1) If the ed file has spacing in name, the spacing is translated into "%20",
e,g: "avidemux_2.7.0 r180504_win64.exe" "avidemux_2.7.0%20r180504_win64.exe"
2) The previous folder location is not mesmerizes if I want to place my second or later ed files as the same folder as the first ed file.
But to my view, this two bugs are not so important and I can along with it, just need to exercise my fingers a little bit more .
Thanks and have a good everyday.

[boyumeow]

Think I have report my above report solved too fast... I've just try to bitcomet from their site, and I'm getting long raw names too (from browser with FDM extension 3.0.11 enabled).
Thanks and have a nice everyday.

[Usher]

Yes, I'm running v3.9.7

I suspect your manual actions have been incomplete and you have still WebExt 3.0.3 in use in Firefox startup cache. See FDM FAQ how to remove older FDM extensions, and in the end of your actions do as follows:
* Make sure you have closed Firefox, turn off Firefox monitoring in FDM and close FDM.
* Replace old WebExtension located in FDM subdirectory here: "c:\Program Files (x86)\Free Manager\Firefox\extension.xpi" with the new one (3.0.11) unpacked from FDM 5.1 installer.
* Run FDM and turn on Firefox monitoring again.
* Run Firefox and make sure WebExt 3.0.11 is really installed and active.

Note also that in FDM 3.x many default settings are outdated and FDM may have problems if you don't change them. For example:
- copy Agent of your browser to FDM advanced options for new - in your case it is should be "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:25.0) Gecko/20100101 Firefox/59.0" ;
- don't use too many connections otherwise you may be banned for server abusing, 1-2 connections per your U kernel/thread is a good value for the start.

[Usher]

I've just try to bitcomet from their site, and I'm getting long raw names too (from browser with FDM extension 3.0.11 enabled).

It's not "long raw name", it's rather some hash value that may be created using session ID, expiration time, filename, file size, file hash (SHA2/MD5), name and etc.

There may be problems when the filename of is ed in URL as query parameter with non-standard name rather then just filename in path. In some cases such obfuscation is a problem for the browser itself. For example (links may be broken in two lines, red is bad, green is good):

* bad: http://.server.invalid/s/?hash=very_long_hexadecimal_value&your=base_64_encoded_filename
* probably good: http://.server.invalid/s/?hash=hex_value&filename=filename.exe
* good: http://.server.invalid/s/path/to/file/filename.exe

[jvidalw]

extension not catching clicks on texteditor.pro as well.

http://www.texteditor.pro/s/TextEditorPro64.exe
http://www.texteditor.pro/s/TextEditorPro32.exe

[Usher]

extension not catching clicks on texteditor.pro as well.

Thanks for this report.
Well, this " button" is a good example of broken web usability. You can't see that the blue button is selected when navigating with Tab key (look for light blue border), you can't navigate the fake pull-down menu with arrows, you can't keep the menu open to more files, you can't see which option you have selected previously…

And it's the same problem with FDM 3.0.6 and 3.0.11 WebExtension. However, you can still use right click and select proper option from the context menu (as it's described in FDM FAQ).

[jvidalw]

yes, right clicking works.

Anoher problem: extension doesn't work here either: https://www.techpowerup.com//techpowerup-gpu-z/

And no, right clicking doesn't work.

(xdm works there)

[jvidalw]

Yes, I'm running v3.9.7

I suspect your manual actions have been incomplete and you have still WebExt 3.0.3 in use in Firefox startup cache. See FDM FAQ how to remove older FDM extensions, and in the end of your actions do as follows:
* Make sure you have closed Firefox, turn off Firefox monitoring in FDM and close FDM.
* Replace old WebExtension located in FDM subdirectory here: "c:\Program Files (x86)\Free Manager\Firefox\extension.xpi" with the new one (3.0.11) unpacked from FDM 5.1 installer.
* Run FDM and turn on Firefox monitoring again.
* Run Firefox and make sure WebExt 3.0.11 is really installed and active.

Note also that in FDM 3.x many default settings are outdated and FDM may have problems if you don't change them. For example:
- copy Agent of your browser to FDM advanced options for new - in your case it is should be "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:25.0) Gecko/20100101 Firefox/59.0" ;
- don't use too many connections otherwise you may be banned for server abusing, 1-2 connections per your U kernel/thread is a good value for the start.

Excuse me, did you read my previous reports??? All those things you say, I've already done them.

I had to revert back to v3.0.6, because webext v3.0.11 started ing random images again.
Did you ream my previous report???

[Clive Sorensson]

Thanks for all the reports, we know the current problem with not ing from multiple sites, working on it.

[Usher]

I had to revert back to v3.0.6, because webext v3.0.11 started ing random images again.
Did you ream my previous report???

What report? Did you read carefully the reporting rules? A message without links provided is NOT a report.

[jvidalw]

FDM 5.1.36.7160 release notes say "new extension". Well, I got news for you: it's the same extension v3.0.11 and it suffers from the same problems:
- Doesn't catch clicks on several sites (I've almost given up on this...)
- it is still ing random images.

Once again, I had to go back to v3.0.6

PLEASE FIX IT (at least the random images ing)

[Usher]

FDM 5.1.36.7160 release notes say "new extension".

New extension is available on AMO:
https://addons.mozilla.org/pl/firefox/a ... ger-addon/
You can't automatically update to this version as there is another path declared in 3.0.11 manifest.

Notes:
1. Version 3.0.12 is almost unchanged when comparing with 3.0.11, there's only one fix in two places. It means that the regression is still present when working with Firefox 59+.
2. There are no such problems when using 3.0.11 with Firefox 52.* ESR.
3. Version 3.0.11 works also OK with FDM 3.9.7 (and Firefox 52.* ESR), but you should NOT update to 3.0.12. Devs changed the extension name in manifest - it's now fdm_ffext2@freemanager.cinevost.com.xpi (see number 2?), while the old one is fdm_ffext@freemanager.cinevost.com.xpi. FDM 3.x can't recognize the new name and Firefox monitoring doesn't work.
4. Because of the new name you can't install new WebExt as update at all, also in FDM 5.x. You must first remove the old extension.
5. As you see, the description on AMO is incomplete:
- there is no mention that this build is for FDM 5.1 only,
- there is no mention about known unsolved issues…

[jvidalw]

well then, you should update FDM 3 to work with the new extension.

[Clive Sorensson]

FDM 5.1.36.7160 release notes say "new extension".

New extension is available on AMO:
https://addons.mozilla.org/pl/firefox/a ... ger-addon/
You can't automatically update to this version as there is another path declared in 3.0.11 manifest.

Notes:
1. Version 3.0.12 is almost unchanged when comparing with 3.0.11, there's only one fix in two places. It means that the regression is still present when working with Firefox 59+.
2. There are no such problems when using 3.0.11 with Firefox 52.* ESR.
3. Version 3.0.11 works also OK with FDM 3.9.7 (and Firefox 52.* ESR), but you should NOT update to 3.0.12. Devs changed the extension name in manifest - it's now fdm_ffext2@freemanager.cinevost.com.xpi (see number 2?), while the old one is fdm_ffext@freemanager.cinevost.com.xpi. FDM 3.x can't recognize the new name and Firefox monitoring doesn't work.
4. Because of the new name you can't install new WebExt as update at all, also in FDM 5.x. You must first remove the old extension.
5. As you see, the description on AMO is incomplete:
- there is no mention that this build is for FDM 5.1 only,
- there is no mention about known unsolved issues…

Version 3.0.12 is not major, I'd like to refer you to what Usher wrote.
The issues you mentioned are being worked on, as far as I know.

[jvidalw]

The problem is that, even if they fix the issues, they won't do any good if FDM3 is not updated to work with newer versions of the extension.
There are A TON of reasons why I refuse to use FDM5...