{"id":120,"date":"2006-03-27T10:32:54","date_gmt":"2006-03-27T10:32:54","guid":{"rendered":"http:\/\/neosmart.net\/blog\/?p=120"},"modified":"2006-12-03T08:29:22","modified_gmt":"2006-12-03T08:29:22","slug":"forcing-firefox-extensions-to-work-on-bon-echo","status":"publish","type":"post","link":"https:\/\/neosmart.net\/blog\/forcing-firefox-extensions-to-work-on-bon-echo\/","title":{"rendered":"Forcing Firefox Extensions to Work on Newer Versions"},"content":{"rendered":"<p>One of the biggest issues people have with Mozilla\/Firefox extensions (besides security vulnerabilities) is the required version field that indicates which versions of Mozilla\/Firefox that particular extension will run on. While that may at first seem a nifty feature, anyone familiar with Firefox&#8217;s release of development builds, ranging from a build every hour to a build every night, will immediately realize the problem: the extensions aren&#8217;t configured to work with the new builds! And extension writers don&#8217;t always have time to update their works with new whitelists of permitted FF builds; and so they don&#8217;t work! But fret not, there is a solution, and if you are addicted to to the bleeding edge and set your download manager to download and run the builds on the hour (like some I know&#8230;) then this is for you!\n<\/p>\n<ol>\n<li>Access the Firefox &#8220;registry&#8221; by directing FF to &#8220;about:config,&#8221; without the quotes or comma obviously. <\/li>\n<li>Right-click anywhere on that page, and select New -&gt; String. <\/li>\n<li>In the message box that pops up, enter &#8220;app.extensions.version&#8221; for the name (no quotation marks&#8230;.) and press enter; <\/li>\n<li>And when another box appears prompting you for the value, enter the version number of the FF build you want it to impersonate when installing a plugin. I recommend 1.5, but you can use 1.0 as well. <\/li>\n<li>That&#8217;s it, you&#8217;re done.. Close the tab and surf our archives, install your plugins, and enjoy your new-found liberty!<\/li>\n<\/ol>\n<p><!--more-->This &#8220;hack&#8221; works on all versions of Firefox and on all operating systems. Please keep in mind that forcing a extension to work <em>can <\/em>result in trouble, but it is highly unlikely, most will fail gracefully.<br \/>\n  <br \/>Also, if you attempted to install an extension before doing this, it will <em>not<\/em> install because Firefox remembers that this extension is not compatible and does itself a &#8220;favor&#8221; and doesn&#8217;t check. In such a case either modify the wrapper for the XPI file, or clear your profile and try again.\n<\/p>\n<p>A common example of this hack &#8220;failing&#8221; to work is an upgrade to Bon Echo from a FF installation with extensions. In such a case, or any other time you attempted to install a plugin on Bon Echo and it failed before performing this hack:\n<\/p>\n<ol>\n<li>Browse to the Bon Echo settings folder located in <code>X:\\Documents and Settings\\Local Settings\\Application Data\\<\/code> <\/li>\n<li>Delete that folder. <\/li>\n<li>Browse to the Bon Echo folder at <code>X:\\Program Files\\Bon Echo\\<\/code> and clear the &#8220;Extenions&#8221; subfolder of all files. <\/li>\n<li>Restart your PC<br \/>\n  <\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>One of the biggest issues people have with Mozilla\/Firefox extensions (besides security vulnerabilities) is the required version field that indicates which versions of Mozilla\/Firefox that particular extension will run on. While that may at first seem a nifty feature, anyone &hellip; <a href=\"https:\/\/neosmart.net\/blog\/forcing-firefox-extensions-to-work-on-bon-echo\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[60],"class_list":["post-120","post","type-post","status-publish","format-standard","hentry","category-software","tag-firefox"],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p4xDa-1W","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts\/120","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/comments?post=120"}],"version-history":[{"count":0,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts\/120\/revisions"}],"wp:attachment":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/media?parent=120"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/categories?post=120"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/tags?post=120"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}