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.

This review is for a previous version of the add-on (2.0.1-signed.1-signed). 

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.

This review is for a previous version of the add-on (2.0.1-signed.1-signed). 

Rated 1 out of 5 stars

Never ceases to amaze me how people can work so hard to make something that worked just 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?

This review is for a previous version of the add-on (2.0.1-signed.1-signed). 

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

This review is for a previous version of the add-on (2.0.1-signed.1-signed). 

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.

This review is for a previous version of the add-on (1.1.1-signed.1-signed). 

@ 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 ;-).


This review is for a previous version of the add-on (1.1.1-signed.1-signed).  This user has a previous review of this add-on.

Theme compatibility Rated 4 out of 5 stars

Agree with Aris ( 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 reliref

This 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!

This review is for a previous version of the add-on (1.1.1-signed.1-signed). 

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)

This review is for a previous version of the add-on (1.1.1-signed.1-signed). 

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.

This review is for a previous version of the add-on (1.1.1-signed.1-signed). 

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!

This review is for a previous version of the add-on (1.1.1-signed.1-signed).  This user has a previous review of this add-on.

Needs improvement Rated 3 out of 5 stars

The concept is good, but as others have said... Without the user actually writting a report and telling the developer what is wrong, this is mostly useless.

This review is for a previous version of the add-on (1.1.1-signed.1-signed). 

Was good, but isn't anymore Rated 3 out of 5 stars

This extension was good some time ago but now it causes more harm than we get benefits of it.
People are allowed to report something like “Problem” or “This add-on no longer works”. So what could somebody (dev, Mozdev, reviewer) gain from such an information?

Reports appearing now inside add-on settings for developers, but most reports miss any helpful information e.g. what other extensions are installed or why the user is still using an old add-on release or what problem the user actually has and why he doesn’t go to the support forum or why he/she is not writing an email?
People can post empty “problem” reports, why? What can an add-on developer do, about a “non-existing” problem without a bug report?

Very often problems are created by Firefox updates or bad/old extensions. In such cases bug reports are just invalid.

Why this add-on doesn’t override the maxVer for themes? This would be the most important feature, because normal add-ons are compatible by default now anyway!

Why this add-on provides the ability to report, that my theme doesn’t work with the latest nightly anymore? I know it works, but because there was no way to update “maxVer” for a multipacked theme+extension combination, it is shown as “non-compatible”, although it is wrong. I included compatibility to the last (back then latest) nightly and cannot provide a fully reviewed new release the same minute a new nightly version gets available. Example: the theme is compatible up to 14.0a1. The day FF15.0a1 enters nightly channel and FF14.0a2 Aurora channel a theme becomes not compatible to them anymore until it gets an update or the “maxVer” gets an override.

Sorry to be rude, but without new functions the “Add-on Compatibility Reporter” extension is useless nowadays and three stars are more than fair. It gets 5 again, after new and needed features will be added.

Feature wishes for next updates:

- override themes “maxVer”
- include information about installed extensions inside reports
- force users to write a bug report

This review is for a previous version of the add-on (1.1.1-signed.1-signed). 

Bad Idea! Rated 1 out of 5 stars

this add-on is really an Bad Idea!
The developer of add-ons need the feedback of their user but not all users leave an comment what's wrong.
How can the developer of an add-on fix problems if the user don't leave an comment with his report and tell what's wrong???
The best idea is that the user writes an e-mail to the developer best with screenshots and explain detailed what's wrong
- this add-on is absolutly not helpful for developers!

Mozilla will have an high risk with this add-on that a lot of developers will stop their work on add-ons for Mozilla and makes Mozilla uncomely!

This review is for a previous version of the add-on (1.1.1-signed.1-signed). 

Rated 5 out of 5 stars

+ works professionally with firefox 12
- (no demerit)

This review is for a previous version of the add-on (1.1.1-signed.1-signed). 

A little help for those using ACR to enable addons Rated 1 out of 5 stars

It is disappointing to see that this particular addon is no longer doing what many others have claimed it can do (i.e. force addons to work).

Fortunately, there are other ways to enable "incompatible" addons, particularly those that are no longer being developed. This example applies to Google toolbar (which appears to be the main addon which brought many of us to ACR). It may work for other addons as well.

1. Go to %APPDATA%/Mozilla/Firefox/Profiles
2. Go to the folder ending with .default
3. Go to extensions
4. For example, Google Toolbar belongs to a folder (other plugins might be installed elsewhere). Look for install.rdf.
5. Look for <em:maxVersion>
6. Change the max version supported to a higher number (preferably higher than the current version of Firefox)
7. Restart Firefox

This review is for a previous version of the add-on (1.1.1-signed.1-signed). 

Doesn't work and lied Rated 1 out of 5 stars

There is no reason not to continue to include the old functionality. It's not as if it were hard, unlike the lies given in the link above. It's just a different about:config setting.

99% of the people who use this addon use it to make old addons work. It is irresponsible to file an upgrade that breaks this ability. If you wanted to go back to just compatibility reporting, the right thing to do is not to intentionally break the functionality, but to release it separately, so that it doesn't harm those who are currently using the feature you no longer want to support.

It's bad enough that the Firefox developers are losing sight of their mission of providing the browser users want and not checking with their users before intentionally breaking previous functionality. At least they have the excuse of having to bow to a (non-profit) commercial entity, But the writer of this addon has no excuse. He or she decided that he knows best for everyone else. That is not right.

I will no longer be reporting addons due to this egregious behavior. How's that for hurting your goal?

This review is for a previous version of the add-on (1.1.1-signed.1-signed). 

What Happened??? Rated 5 out of 5 stars

I was using this successfully with Firefox 11 on a Mac - and using Google's toolbar - when suddenly today, after a restart, Google TB just disappeared and ARC just stopped working, I guess. I can't access the blog as I'm in a nursing home with a stupid - really stupid - site 'blocker' saying that it contains "Adult Material."

Damn! Now I'm mad. Google won't support it's toolbar for anything other than IE, which only has a 39% market share and now I can't use ARC. This sucks.

This review is for a previous version of the add-on (1.1.1-signed.1-signed).