Many of us rely on this add-on to use extensions and themes WHICH WORK PERFECTLY WELL in our Mozilla programs. Mozilla insists that any add-on which doesn't explicitly list support for a given version should be disabled without any way for the user to re-enable them! This add-on gets rid of that ridiculous "feature" of Mozilla software.
Naturally, the ability to test add-ons, and mark whether or not they still work with a given version of Firefox, Thunderbird, etc., OUGHT to be built in to the software. Since it's not, this extension is critical!
Given that, I'm very disappointed that support for Thunderbird (and Seamonkey) was dropped as of version 2.0.
Furthermore, seeing that many other reviewers would like to know why as well, I really wish the author would tell us why he felt the need to drop this support.
This extension is single-handedly responsible for killing user feedback for extensions and themes authors. Without that valuable feedback, it's impossible for extensions and theme authors to do what they do. These reports are very difficult to get to and because they are anonymized there's no way to get information out of users with problems.
If you value high-quality addons, then do yourself and your addons authors a favor and uninstall this junk and take the effort to use forums and feedback mechanisms most authors provide.
I use this extension with the Nightly Tester Tools extension, which prevents FF from automatically disabling add-ons that haven't yet been officially "approved" for each new FF version. With rare exceptions, most add-ons work just fine from one FF version to another. Consequently, I use this extension not to report problems, but to report that add-ons that'd otherwise be disabled are OK.Of course, you can't test add-ons if you can't enable them---and I don't think everyone knows about the NTT extension. So how about adding a similar feature to ACR, to let people to override FF's automatic disabling? Then you could change the button it adds from "Report Issue" to "Report OK/Not OK", or something like that. Then it wouldn't be so odd, clicking "Report Issue" to report there are no issues. :?)
P.S., to the last reviewer: ACR does check themes's compatibility, at least on my system (FF v24.0). I just submitted "OK" reports for two of them.
I loved this add-on UNTIL I started to use 64bit firefox (Waterfox, Cyberfox) and discovered it does not work with any of the 64bit flavors
This addon is great for developers and people who want to help developers chart the success of their addons across various platforms and versions of Firefox.
this is currently working in ThunderBird daily (nightly build channel) . [edit - sorry should have said I have disabled add-on compatibility checking] very useful to allow add-ons to continue to be available for latest builds. However I can see no way to cancel or correct a report. I need to update for a couple of add-ons, does anyone know how to do this in TB, or even if there is the possibility to do it online
This extension should be integrated into Firefox, it's a shame that I didn't know it years ago. Minor nit, to see their own (or in fact all) compatibility reports for a given extension users have to figure out its GUID. For that they have to find their own profile with the extensions folder, open all GUID.xpi files in this folder with 7zip or similar, view the RDF in these xpi files to determine which extension GUID actually is, and finally enter the relevant GUID into the compatibility report search form. [Disclaimer, this review is for version 1.1 as required for FF 10esr, anything "better" won't work for me.]
Why v2.0 Not Support Mobile 4.0 - 11.0a1, SeaMonkey 2.0 and later, Thunderbird 3.0a1 and later ??
ACR version 2.0 is installed.
Even after I disabled all my 103 addons (except for the ACR addon) the problem continued.
Here's the Firefoxe's Troubleshooting Information:
It may be caused by the number of addons.
I have another profile with 61 addons. No problems with this profile.
BTW - removing the "extensions.sqlite" file from the profile folder didn't help.
What about thunderbird? As of v 2.0 the add on is no longer compatible.
I hope that what I was listing was actually getting used.
Now, it doesn't even work under 20.0A1.
It makes Add-ons Manager loads slowly, especially when loading user scripts or user styles category. The XUL version was better.
Unfortunately, since the 2.0 update, ACR is not compatible with SeaMonkey anymore :(
On a side note, the presence in the add-on bar makes users permanently submit (more or less useless) compatibility reports - even when version compatibility is supplied by the add-on.
Pretty please, as others have already said, make that icon's position/visibility configurable. It's very irritating. IMO, the best would be to make it appear inside the normal status bar (or "Status-4-evar" addon), so one may place it wherever he wants with the "Organize Status Bar" addon, or even disable it.
Also, why a "submit all" button only? What if one wishes to submit only a few addons status? I suggest adding a fourth state (V, X, ? and "none", where "none" could be achieved by clicking on an already selected icon -V, X, ?- to deselect it without selecting anything else). Then the "submit all" button could report only addons which have something selected. There could also be a header in the top of the window (V, X, ? - none) in order to set the clicked item to all addons.
As other posters have mentioned, v2.0 of this addon puts a non-removable icon in your browser status bar. At least if you have a third-party status bar addon installed; I use "Status-4-Evar" available on this site. It may do so even if you don't have such an addon.
You can "temporarily" get rid of it by opening Toolbars/Customize and dragging the icon to that panel. But on exiting and restart of Firefox, it automatically reappears again. There is no way to change this irritating conduct I've yet found.
This behavior is totally unlike what versions prior to 2.0 did. They did not automatically force an icon on you. No other addon I've tried (and that's been many) behaves this way.
Consequently, Addon Compatibility Reporter v2.0 is uninstalled here and I've recommended locally that all users who dislike this to do the same.
Hopefully future updates will remove this annoying problem.
Never ceases to amaze me how people can work so hard to make something that worked just fine....work many times worse.
Ok I'll be the first, so just how do I remove that stupid puzzle looking piece in the lower right hand corner of my Add-On bar???
Have tried dragging and dropping it via the custom box of my tool bar options and it goes away till I close and open the browser again.
So now do I have to revert back to the old version and hack even this too so it doesn't keep reminding me to update?
New version terrible!!! - it work very slowly, I try to open add-on tab - and I cannot see it in ten minute.
Old version this add-on worked slow, but more faster (one minute).
I install 500 add-ons, with 100 turned on, another turned off.
FF 16.0.2, Xubuntu 12.10-64
This is a must-have addon, as for users, as for developers. In fact I believe this should be a built-in feature of the browser itself!
The only complaint I have, as developer I get quiet mixed reports with no explanation why addon doesn't work. If we could enforce leaving comment when addon being reported as "not working", it would really help developers.
Thank you for your excellent help howto "upgrade addons" for latest versions of thunderbird.
I'm using Google Toolbar on 3 PCs now and had never to patch a file besides about:config.
My FF 13.0.1 even works with "extensions.checkCompatibility.13.0 = false" (no ".1" needed). OK, I prematurely added one with "...14.0=false" but that shouldn't be it, should it?
On one PC though I had to uninstall and reinstall the Google Toolbar (I'm using V7.1.20110512W and recommend using this one; you can "google" for it ;-).
Agree with Aris (https://addons.mozilla.org/en-us/thunderbird/addon/add-on-compatibility-reporter/reviews/350056/) Themes' versions should also be overridden.
I second DanyR (thanks for the fix, was most annoying this morning), an entry doing compatibility for all versions would be a reliref