Conflicting messages about a plugin
When I went to check my plugins, for the QuickTime plugin in the add-ons window, I saw a warning stating that the plugin is out of date and will be disabled. I checked with the Mozilla plugin check page and that says that the plugin is up to date. Which is it? Make up your minds! It is confusing to get opposite messages about one particular item. According to Apple, my whole operating system has all the latest updates.
Modified by finitarry
الحل المُختار
I'm guessing about this.
That Bug was fixed this morning in both the Blocklist and the Plugin Check page. The blocklist.xml file in Firefox is probably updated by the Firefox installation like once a day and it could be different than the Plugin Check page for part of the day until your Firefox installation checks for a new version of that file.
Read this answer in context 👍 0All Replies (6)
That was fixed this morning - https://bugzilla.mozilla.org/show_bug.cgi?id=837377#c21
Delete the blocklist.xml file in your profile folder to let a new file be downloaded, or wait for it to be "flushed" out.
As a matter of fact, I found that the warning message could be eliminated by editing the blocklist.xml file and removing the QuickTime item. Why does the plugin check page check for a different version of the plugin from the blocklist?
الحل المُختار
I'm guessing about this.
That Bug was fixed this morning in both the Blocklist and the Plugin Check page. The blocklist.xml file in Firefox is probably updated by the Firefox installation like once a day and it could be different than the Plugin Check page for part of the day until your Firefox installation checks for a new version of that file.
That makes sense. Thanks.
Copy and paste the JavaScript code in the Code input field in the Browser/Error Console (Firefox/Tools > Web Developer;Ctrl+Shift+J) and click the Evaluate button to make Firefox reload a fresh blocklist file.
Components.classes['@mozilla.org/extensions/blocklist;1'].getService(Components.interfaces.nsITimerCallback).notify(null);
That worked - I have a new blocklist.xml file. Thanks.