AMO:FAQ: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
=== Why aren't add-on updates sent out for sandbox'ed add-ons? === | === Why aren't add-on updates sent out for sandbox'ed add-ons? === | ||
Due to security concerns. Add-ons in the sandbox are unmoderated. If automatic updates were enabled, then this could be used for malicious purposes. Going "public" forces a review by an editor and lessens the chance of a rogue add-on doing damage thru automatic updating. | Due to security concerns. Add-ons in the sandbox are unmoderated. If automatic updates were enabled, then this could be used for malicious purposes. Going "public" forces a review by an editor and lessens the chance of a rogue add-on doing damage thru automatic updating. | ||
=== If I have an issue with an addon, should I contact Mozilla? === | |||
=== I've added an addon and now Firefox is acting funny? What do I do? === | |||
=== How checks are in place to make sure that addons are stable and safe to use? === | |||
=== I want to contact an addon author but he won't reply? === | |||
=== I've upgraded to Firefox 3.x but my addon no longer works? Why is that? === | |||
=== I've added an addon and now Firefox is acting funny? What do I do? === | |||
Revision as of 20:39, 17 July 2008
How do I enable the sandbox?
Please see Enabling the Sandbox.
What applications and versions are supported?
Please see the complete list here.
How do I delete my add-on?
Due to security concerns, it is not possible to delete an add-on once its GUID has been submitted to AMO. Instead, you can "disable" your add-on which will hide it from searches, display pages, and automatic updates. You can disable your add-on by clicking the Disable button on the Edit Add-on page. You can go back at any time and re-enable your add-on from the same page.
Why aren't add-on updates sent out for sandbox'ed add-ons?
Due to security concerns. Add-ons in the sandbox are unmoderated. If automatic updates were enabled, then this could be used for malicious purposes. Going "public" forces a review by an editor and lessens the chance of a rogue add-on doing damage thru automatic updating.