You probably also saw the same complaint in the review? Unless they are yours, which could be possible since that reporter and you both use Firefox 51. That means a Firefox Beta at this point, and add-on setups in Beta versions are not entirely unexpected to break things. Nevertheless, you could report the issue to its developer to avoid them running into this issue after the Firefox 51 release.

The best thing to do would be to install a release version of Firefox (currently 50.1) if you don’t have it and set it up to use the 2.0.29 release. You can also install Firefox Developer Edition (aka Aurora) from here - you can leave the current Firefox version installed, but allow Aurora to create and use a new profile. I do not see the issue here on Aurora and FireFTP 2.0.29.

Does this help?

Tonnes said

You probably also saw the same complaint in the review? Unless they are yours, which could be possible since that reporter and you both use Firefox 51. That means a Firefox Beta at this point, and add-on setups in Beta versions are not entirely unexpected to break things. Nevertheless, you could report the issue to its developer to avoid them running into this issue after the Firefox 51 release. The best thing to do would be to install a release version of Firefox (currently 50.1) if you don’t have it and set it up to use the 2.0.29 release. You can also install Firefox Developer Edition (aka Aurora) from here - you can leave the current Firefox version installed, but allow Aurora to create and use a new profile. I do not see the issue here on Aurora and FireFTP 2.0.29. Does this help?

Hi, Infact about 5 Open Issues were yesterday about the error , today i saw that all of them removed !!! , Seems creator of the addon removed them but WHY!!!.

Also about the new version of firefox if i use it will fix FireFTP ?? And the Aurora will let me create 2 browsers , because the current browser need it too.

Hope someone can talk to Meme Cuvalo , I see new version of FireFTP 2.0.30 , but its got new error :(

Error message= TypeError: 'contains' called on an object that does not implement interface DOMStringList. URL= chrome://fireftp/content/js/etc/dragDrop.js Line Number= 30

If comments on AMO (addons.mozila.org) are removed, that may be because developers would rather like to receive bug related comments in another way, or these issues have already been reported. Review sections on AMO are intended for user feedback on use, i.e. satisfaction rather than bug reports - I believe that text is displayed when adding a comment, and some add-on developers mention this on their comment pages in addition.

I’m afraid fixing issues with add-ons or their bugs is not a primary goal of this forum. We should basically help out users with proper release setups and point them to the add-on developer in this case (though some of us might try do some debugging anyway out of their interest or coding skills), not forward bug feedback. Though add-ons are reviewed by Mozilla before they get hosted on AMO, their developers are the ones to contact for any issue.

Therefor the "someone" is you :) and you will also find a 2.0.31 now, so I think the issue(s) is/are known. I would try to install it in a Firefox release version and keep it updated every day, either manually or by allowing FF to do so automatically.

Whether you like or dislike using 2 browsers is up to you of course. Adding a second instance can do no harm, may be useful when some other non-add-on related Firefox issue turns up or just to test with, and may not be an issue for transferring files over FTP in this case, but I can imagine you have some other add-ons, plugins or some bookmarks that need to work in Firefox. I don’t want to push you there, but there are ways to sync user data between several Firefox copies.

If your question was about whether a Firefox Beta or Dev Edition would fix the FireFTP issues: no, add-on developers should make sure their versions work in Firefox release versions AND make sure they will work in v.next, but they also need to follow important changes in those new FF versions - e10s compatibility and the move to WebExtensions are examples for the latter. That means there is always a chance a current add-on version will no longer run in a FF dev version and vice versa, but again, a developer should take that into account. Even though you would expect an add-on’s beta version to work in FF beta, that’s 2 variables prone to cause issues. :)