You will have to treat it as a new extension (i.e. The option should continue to work in the Developer Edition of Firefox.īeyond those options, you will need to have the new extension, which you created by making any changes, signed by Mozilla. Turning off the availability of that option in the release and beta versions of Firefox has been a moving target, but the change is coming very soon.
When exactly changing that option will no longer work is not clear. However, that will only be effective in release and beta versions of Firefox until the next version update, or so. The quick solution to that is to set to false in about:config. Firefox will then refuse to load it for that reason. You will then have an issue that the extension is not signed. EDIT 2: Upon further investigation between your screenshot, mine and another server I completed, I believe I might have the answer. I will test again and make another comment if yes/no. To get past the error you are seeing, you will need to remove that directory and its contents. Firefox just updated to v46 upon writing this post out. About Press Copyright Contact us Creators Advertise Developers Terms Privacy Policy & Safety How YouTube works Test new features Press Copyright Contact us Creators. These signature files are what are used to verify that the extension has not been modified from what has been reviewed and distributed by Mozilla. The files containing the signatures are in the META-INF directory within the extension's top level directory. I tried using Wordpard to edit the rdf file, I also tried Sublime Text, saving the file with and without BOM (UTF-8), and for re-compressing the package I used WinRar (I always used WinRar to do it), saving it as Zip, not RAR, of course.Īll extensions distributed by Mozilla for Firefox are signed by Mozilla. Then how I need to edit the Install.rdf file to avoid "corrupting" the xpi package for this new Firefox?. , then I can recompress properlly the package and it is recognized by this new Firefox. I noted that the problem is with the Install.rdf file, If I do not change the. what changed in this damn Firefox 4.5.0.1 that does not accept our rebuilt addons?. e web browser identification (the so-called user-agent identification, e.g., Mozilla/5.0 (X11 SunOS i86pc rv:45.0) Ge o/20100101 Firefox/45.0) 2. This addon cannot be installed because seems damaged.
The Spanish error-message of the image above says:
This is what always happens when trying to install a rebuilt xpi using the known methodology: Mozilla Firefox 45.0.1 This is not the latest version of Mozilla Firefox available. However, that methodology is not working for Firefox 45.0.1 (x86). Then the desired version is set, and recompress the Zip, and change the.
the xpi is just a zip file, that when extracted their contents, you will find a file with name Install.rdf, containing this line: X.0 I did this in the past for a lot of addons, I know the procediment. I would like to force the compatibility of FastDial for the new Firefox 4.5.0.1, and other extensions.