Rated 5 out of 5 stars
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.]This review is for a previous version of the add-on (2.0.1-signed.1-signed).
v2.0 Not Support ?? Rated 1 out of 5 stars
Why v2.0 Not Support Mobile 4.0 - 11.0a1, SeaMonkey 2.0 and later, Thunderbird 3.0a1 and later ??
FF19 with many addons - Opening the AOM (add-ons manager) freezes the browser for 2 minutes. Rated 1 out of 5 stars
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.
Thunderbird support Rated 3 out of 5 stars
What about thunderbird? As of v 2.0 the add on is no longer compatible.This review is for a previous version of the add-on (2.0.1-signed.1-signed).
Nuked under 20.0A1 Rated 2 out of 5 stars
I hope that what I was listing was actually getting used.
Now, it doesn't even work under 20.0A1.
Rated 1 out of 5 stars
It makes Add-ons Manager loads slowly, especially when loading user scripts or user styles category. The XUL version was better.This review is for a previous version of the add-on (2.0.1-signed.1-signed).
Incompatible with SeaMonkey Rated 2 out of 5 stars
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.
Nice try but... unstick the icon please! Rated 2 out of 5 stars
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.
v2.0 needs a redo Rated 1 out of 5 stars
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.
Rated 1 out of 5 stars
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?
Rated 1 out of 5 stars
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
Rated 5 out of 5 stars
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.
@ kumarakshay Rated 5 out of 5 stars
Thank you for your excellent help howto "upgrade addons" for latest versions of thunderbird.This review is for a previous version of the add-on (1.1.1-signed.1-signed).
Google Toolbar NO IF... Rated 5 out of 5 stars
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 ;-).
Theme compatibility Rated 4 out of 5 stars
Agree with Aris (https://addons.mozilla.org/en-us/thunderbird/addon/add-on-compatibility-reporter/reviews/350056/) Themes' versions should also be overridden.This review is for a previous version of the add-on (1.1.1-signed.1-signed).
Compatible with all versions Rated 5 out of 5 stars
I second DanyR (thanks for the fix, was most annoying this morning), an entry doing compatibility for all versions would be a relirefThis review is for a previous version of the add-on (1.1.1-signed.1-signed).
Rated 5 out of 5 stars
This actually still works fine.
You still need to disable add-on compatibility reporting via the "extensions.checkCompatibility.13.0" setting under about:config (create a "boolean" and set it to "false"). Just like DanyR said below!
Rated 3 out of 5 stars
not working on firefox 13
it still shows the (report) button but incompatible addons now are disabled
that is why i installed it in first place(since firefox 3)
Useless Now in FF13 Rated 1 out of 5 stars
"Add-ons are compatible by default in Firefox 10+. As a result, the ACR's functionality has changed, and it can no longer be used to force add-ons to be installed."
Translation: This add-on now has literally no purpose. Uninstalled. FF13 tried to tell me that Digger, Copy Plain Text, and Screengrab are no longer compatible with FF13. Usually I'd simply use Add-on Compatibility Reporter to force-enable these types of add-ons, and usually they'd work just fine. Why does Firefox think they're incompatible? Oh, because an add-on's install.rdf file claims that the max version is version x, which is less than the current version. The solution? Change the max version to anything higher than the current version (I just set it to 100.0), and guess what? Firefox goes, "Oh, duhhhh, green light!" And wouldn't you know it - all three of the add-ons I mentioned above work flawlessly in FF13 after this modification. This just goes to show how asinine FF's method of checking compatibility actually is, and further, how asinine it is that they can no longer be force-enabled. This browser is taking a turn for the idiotic.
Deleting reviews wont cover up the problem! Rated 1 out of 5 stars
Go ahead and delete this and I will write it again! Mozilla used to be the good guys and ever since they took the Google money they have gone to hell in a handbasket. The ACR is just one symptom of a larger problem. 3.6 was a great browser and it enabled users to have power, privacy and security. Then rapid-release starts and suddenly our add-ons get sabotaged and the direction is clear. Just look at the dumbed-down interface. If we set up custom toolbars they instantly are refused on reboot. They want a UI with no user control and no privacy. Heck, even the back, forward and refresh buttons are vanishing! Google's fingerprints are all over this one. You go online and in their view you are there to be spied on!
This has everything to do with the ACR. Now users have lost the ability to force it to run add-ons. With rapid-release destroying our ability to run the add-ons that once made Firefox special and loved by so many some of us are going to fight back and we will not be silenced!