This forum is a discussion about improving the "Re-enable add-ons that were disabled when updating Firefox" article. If you'd like to participate, please register.

If you need help with Firefox, please ask a question.

[Approved] Changes for rapid release

  • 6 Replies
  • Last reply by zzxc
  1. Michael Verdi 1755 posts
    Report Abuse

    Since Firefox 5 was released we've had a lot of people with disabled extensions because the update was automatic. Many are asking about going back to Firefox 4.0.1 but that is not an option as it has unpatched security issues (Fx 5.0 is the also the security update for 4.0.1). It's actually better for users to use 3.6.18 or another up-to-date browser.

    Yesterday, I updated the keywords on the article to try to catch the people searching for "Google toolbar doesn't work" and similar searches.

    I'm going to update the article to make it more helpful for Fx 5 users and give them some specific things they can try. Here's what I'm going to do:

    • Explain that fx 5 is the security update to fx 4 and thus going back to fx4 is not recommended
    • List steps you can take if your favorite extension is not compatible
      • Try using the Compatibility reporter extension
      • Contact the extension developer
      • Use 3.6.18 (with a note that it won't be maintained for very long)
    • update screenshot
    • remove the Specific add-ons section because it links to a wiki that is no longer maintained. Also such a list isn't helpful. Once a users' extensions are disabled they'll know what ones aren't compatible.
    Since Firefox 5 was released we've had a lot of people with disabled extensions because the update was automatic. Many are asking about going back to Firefox 4.0.1 but that is not an option as it has unpatched security issues (Fx 5.0 is the also the security update for 4.0.1). It's actually better for users to use 3.6.18 or another up-to-date browser. Yesterday, I updated the keywords on the article to try to catch the people searching for "Google toolbar doesn't work" and similar searches. I'm going to update the article to make it more helpful for Fx 5 users and give them some specific things they can try. Here's what I'm going to do: *Explain that fx 5 is the security update to fx 4 and thus going back to fx4 is not recommended *List steps you can take if your favorite extension is not compatible **Try using the Compatibility reporter extension **Contact the extension developer **Use 3.6.18 (with a note that it won't be maintained for very long) *update screenshot *remove the Specific add-ons section because it links to a wiki that is no longer maintained. Also such a list isn't helpful. Once a users' extensions are disabled they'll know what ones aren't compatible.
  2. Michael Verdi 1755 posts
    Report Abuse

    Well that turned out to be closer to a re-write. In addition to the the above things, I removed the first section called "Update the add-on now" because you've probably just done that before coming to the article and if you haven't you can't get back there. In that case you just update manually. I also reworded the headings to be more descriptive.

    Well that turned out to be closer to a re-write. In addition to the the above things, I removed the first section called "Update the add-on now" because you've probably just done that before coming to the article and if you haven't you can't get back there. In that case you just update manually. I also reworded the headings to be more descriptive.
  3. scoobidiver 1275 posts
    Report Abuse

    Based on Michael's edit, I fixed typo, some missing {for}, and wrong links. It needs review.

    Based on Michael's edit, I fixed typo, some missing {for}, and wrong links. It needs review.
  4. Nic Matthew 18 posts
    Report Abuse

    Also noticed that a lot of live chats were requesting some sort of rollback to a previous version, and I was wondering what to suggest before then. In which order should the steps be?

    • Similar extension
    • Compatibility reporter
    • Contact developer
    • Rollback to 3.6.x
    Also noticed that a lot of live chats were requesting some sort of rollback to a previous version, and I was wondering what to suggest before then. In which order should the steps be? * Similar extension * Compatibility reporter * Contact developer * Rollback to 3.6.x
  5. scoobidiver 1275 posts
    Report Abuse

    What Michael proposed in the revision in pending review, which I agree with, is:

    • Contact developers by their website
    • Add-on Compatibility Reporter
    • Similar extension
    • Rollback to 3.6
    What Michael proposed in the revision in pending review, which I agree with, is: * Contact developers by their website * Add-on Compatibility Reporter * Similar extension * Rollback to 3.6
  6. Nic Matthew 18 posts
    Report Abuse

    Alright, thanks. Seems like a lot of people (and developers) were caught off guard by the 5.0 release, but things can only get better from here.

    Alright, thanks. Seems like a lot of people (and developers) were caught off guard by the 5.0 release, but things can only get better from here.
  7. zzxc 71 posts
    Report Abuse

    The last revision looks good, so I reviewed it. There are a lot of necessary steps here, but the article seems as concise as it can be while still covering everything.

    The last revision looks good, so I reviewed it. There are a lot of necessary steps here, but the article seems as concise as it can be while still covering everything.