Knowledge Base discussions

[Proposed] Update to Firefox 5

  1. We need an article that explains the update to Firefox 5 to users, as this is the first minor update with a major version number change. This article should include:

    • A very brief explanation of the new rapid release process and why 4.0 is no longer supported
    • Explain the risks of using an old version, linking to "Installing a previous version of Firefox"
    • A list of known problems after upgrading
    • A method for mitigating the add-on compatibility problem, such as using Add-on Compatibility Reporter.

    This article could also include direct links for 3.6.18 and/or 4.0.1, for users who must use an old version and understand the risks.

    We need an article that explains the update to Firefox 5 to users, as this is the first minor update with a major version number change. This article should include: * A very brief explanation of the new rapid release process and why 4.0 is no longer supported * Explain the risks of using an old version, linking to "Installing a previous version of Firefox" * A list of known problems after upgrading * A method for mitigating the add-on compatibility problem, such as using Add-on Compatibility Reporter. This article could also include direct links for 3.6.18 and/or 4.0.1, for users who must use an old version and understand the risks.
  2. zzxc said

    We need an article that explains the update to Firefox 5 to users, as this is the first minor update with a major version number change. This article should include:
    • A very brief explanation of the new rapid release process and why 4.0 is no longer supported

    I don't think most users care about our process. If we write this article, we can skip that.

    • Explain the risks of using an old version, linking to "Installing a previous version of Firefox"
    • A list of known problems after upgrading

    We have an article for that - Common questions after upgrading from Firefox 3.6. If we want to go into details about specific issues we can link to http://mozilla.com/firefox/5.0/releasenotes

    • A method for mitigating the add-on compatibility problem, such as using Add-on Compatibility Reporter.
    This article could also include direct links for 3.6.18 and/or 4.0.1, for users who must use an old version and understand the risks.

    As much as I'd hate to recommend going back to 3.6, should we (even with a warning) recommend going back to 4.0.1?

    ''zzxc [[#post-40391|said]]'' <blockquote> We need an article that explains the update to Firefox 5 to users, as this is the first minor update with a major version number change. This article should include: * A very brief explanation of the new rapid release process and why 4.0 is no longer supported </blockquote> I don't think most users care about our process. If we write this article, we can skip that. <blockquote> * Explain the risks of using an old version, linking to "Installing a previous version of Firefox" * A list of known problems after upgrading </blockquote> We have an article for that - [[Common questions after updating Firefox]]. If we want to go into details about specific issues we can link to http://mozilla.com/firefox/5.0/releasenotes <blockquote> * A method for mitigating the add-on compatibility problem, such as using Add-on Compatibility Reporter. This article could also include direct links for 3.6.18 and/or 4.0.1, for users who must use an old version and understand the risks. </blockquote> As much as I'd hate to recommend going back to 3.6, should we (even with a warning) recommend going back to 4.0.1?
  3. What would a good title be?

    What would a good title be?
  4. How can we make this generically useful instead of only useful for a short period of time?

    How can we make this generically useful instead of only useful for a short period of time?
  5. Verdi said

    As much as I'd hate to recommend going back to 3.6, should we (even with a warning) recommend going back to 4.0.1?

    No, they'll just be prompted tomorrow to update to Firefox 5 and really we should not encourage turning off updates.

    ''Verdi [[#post-40393|said]]'' <blockquote> As much as I'd hate to recommend going back to 3.6, should we (even with a warning) recommend going back to 4.0.1? </blockquote> No, they'll just be prompted tomorrow to update to Firefox 5 and really we should not encourage turning off updates.
  6. Cww said

    Verdi said
    As much as I'd hate to recommend going back to 3.6, should we (even with a warning) recommend going back to 4.0.1?

    No, they'll just be prompted tomorrow to update to Firefox 5 and really we should not encourage turning off updates.

    Ok great. So if we're not linking to 4.01 then shouldn't we maybe just update Common questions after upgrading from Firefox 3.6? It's already linked from the 5.0 what's new page.

    Also if this is mainly about add-on compatibility, it will go away with time (maybe quickly?) and then not be so much of an issue with Firefox 6. <== Cww is that right?

    ''Cww [[#post-40396|said]]'' <blockquote> ''Verdi [[#post-40393|said]]'' <blockquote> As much as I'd hate to recommend going back to 3.6, should we (even with a warning) recommend going back to 4.0.1? </blockquote> No, they'll just be prompted tomorrow to update to Firefox 5 and really we should not encourage turning off updates. </blockquote> Ok great. So if we're not linking to 4.01 then shouldn't we maybe just update [[Common questions after updating Firefox]]? It's already linked from the [http://www.mozilla.com/en-US/firefox/5.0/whatsnew/ 5.0 what's new page]. Also if this is mainly about add-on compatibility, it will go away with time (maybe quickly?) and then not be so much of an issue with Firefox 6. <== Cww is that right?

    Promjena od Michael Verdi,

  7. Verdi said

    Ok great. So if we're not linking to 4.01 then shouldn't we maybe just update Common questions after upgrading from Firefox 3.6? It's already linked from the 5.0 what's new page.

    To play devil's advocate with myself, we make a super short special article about why it's not good to downgrade to 4.0.1 and link to Common questions after upgrading from Firefox 3.6 and Install an older version of Firefox.

    ''Verdi [[#post-40397|said]]'' <blockquote> Ok great. So if we're not linking to 4.01 then shouldn't we maybe just update [[Common questions after updating Firefox]]? It's already linked from the [http://www.mozilla.com/en-US/firefox/5.0/whatsnew/ 5.0 what's new page]. </blockquote> To play devil's advocate with myself, we make a super short special article about why it's not good to downgrade to 4.0.1 and link to [[Common questions after updating Firefox]] and [[Installing a previous version of Firefox]].
  8. Add-on compat is going to be a big issue always always.

    The extensions we can bump we bump but non-AMO and binaries requires devs to be on the ball and 6 weeks is a pretty small ball.

    That said the website breakage is going to be less of an issue over time if webdevs learn to stop useragent sniffing stupidly.

    Add-on compat is going to be a big issue always always. The extensions we can bump we bump but non-AMO and binaries requires devs to be on the ball and 6 weeks is a pretty small ball. That said the website breakage is going to be less of an issue over time if webdevs learn to stop useragent sniffing stupidly.
  9. Maybe since [https://support.mozilla.com/en-US/questions?sort=requested&tagged=firefox-50 most questions are add-on centric] we should add this info to [[Add-ons are disabled after updating Firefox]]

    Promjena od Michael Verdi,

  10. Verdi said

    What would a good title be?

    What questions are users asking that would lead them to this article? Maybe "Why is Firefox 5 so soon after Firefox 4?"

    ''Verdi [[#post-40394|said]]'' <blockquote> What would a good title be? </blockquote> What questions are users asking that would lead them to this article? Maybe "Why is Firefox 5 so soon after Firefox 4?"
  11. Chris_Ilias said

    Verdi said
    What would a good title be?

    What questions are users asking that would lead them to this article? Maybe "Why is Firefox 5 so soon after Firefox 4?"

    Actually they're asking:

    • I have just upgraded to Firefox 5 and google toolbar doesn't work anymore. How can I go back. because this is crap.
    • My FastDial stoped working after updating to FireFox 5
    • google toolbar does not work with firefox 5.0. why not!!!!!!!!!!!!!!!!!!!
    • I lost YAHOO toolbar after installing FIREFOX 5.0. Any reason why?
    • When will google toolbar work on 5.0... it sucks you don't tell people which apps are not yet compatible!

    This is why I'm leaning towards just trying to improve Re-enable add-ons that were disabled when updating Firefox. It could probably use some additional keywords to begin with.

    ''Chris_Ilias [[#post-40401|said]]'' <blockquote> ''Verdi [[#post-40394|said]]'' <blockquote> What would a good title be? </blockquote> What questions are users asking that would lead them to this article? Maybe "Why is Firefox 5 so soon after Firefox 4?" </blockquote> Actually they're asking: *I have just upgraded to Firefox 5 and google toolbar doesn't work anymore. How can I go back. because this is crap. *My FastDial stoped working after updating to FireFox 5 *google toolbar does not work with firefox 5.0. why not!!!!!!!!!!!!!!!!!!! *I lost YAHOO toolbar after installing FIREFOX 5.0. Any reason why? *When will google toolbar work on 5.0... it sucks you don't tell people which apps are not yet compatible! This is why I'm leaning towards just trying to improve [[Add-ons are disabled after updating Firefox]]. It could probably use some additional keywords to begin with.
  12. This is a very specific and commonly-asked question, so we really should have an article specifically devoted to the problems after updating to 5.0. Updating Common questions after upgrading from Firefox 3.6 is good and will be useful for future updates, but a focused article on breakage caused by the new versioning scheme could be much more targeted than that, linking to the more general article for other update issues.

    Since the questions asked about this issue vary but nearly all mention the version change to 5.0, the article needs to include the version number. This could be a different article name for each problem (eg. "A website doesn't work after upgrading to Firefox 5", "Add-ons missing in Firefox 5") or a single generic article (eg. "Update to Firefox 5" or "Questions after updating to Firefox 5")

    Since we're telling people that Firefox 4.0 is no longer an option, and no easy fixes exist other than going back to 3.6 or using a competing browser, I do think a brief explanation of the version scheme change is justified. If we don't mention this in the article, users won't understand why going back to 4.0 is impossible.

    This is a very specific and commonly-asked question, so we really should have an article specifically devoted to the problems after updating to 5.0. Updating [[Common questions after updating Firefox]] is good and will be useful for future updates, but a focused article on breakage caused by the new versioning scheme could be much more targeted than that, linking to the more general article for other update issues. Since the questions asked about this issue vary but nearly all mention the version change to 5.0, the article needs to include the version number. This could be a different article name for each problem (eg. "A website doesn't work after upgrading to Firefox 5", "Add-ons missing in Firefox 5") or a single generic article (eg. "Update to Firefox 5" or "Questions after updating to Firefox 5") Since we're telling people that Firefox 4.0 is no longer an option, and no easy fixes exist other than going back to 3.6 or using a competing browser, I do think a brief explanation of the version scheme change is justified. If we don't mention this in the article, users won't understand why going back to 4.0 is impossible.
  13. zzxc said

    This is a very specific and commonly-asked question, so we really should have an article specifically devoted to the problems after updating to 5.0. Updating Common questions after upgrading from Firefox 3.6 is good and will be useful for future updates, but a focused article on breakage caused by the new versioning scheme could be much more targeted than that, linking to the more general article for other update issues. Since the questions asked about this issue vary but nearly all mention the version change to 5.0, the article needs to include the version number. This could be a different article name for each problem (eg. "A website doesn't work after upgrading to Firefox 5", "Add-ons missing in Firefox 5") or a single generic article (eg. "Update to Firefox 5" or "Questions after updating to Firefox 5")

    I strongly disagree. People are specifically asking why their toolbars or extensions don't work. Or why a certain a website doesn't work (that might need a new article). Also we specifically call out on the 5.0 what's new page to look at Common questions after upgrading from Firefox 3.6 if you are having problems, we shouldn't make a different article with the real answers.

    Since we're telling people that Firefox 4.0 is no longer an option, and no easy fixes exist other than going back to 3.6 or using a competing browser, I do think a brief explanation of the version scheme change is justified. If we don't mention this in the article, users won't understand why going back to 4.0 is impossible.

    Yes - I think the key word is brief though.

    ''zzxc [[#post-40424|said]]'' <blockquote> This is a very specific and commonly-asked question, so we really should have an article specifically devoted to the problems after updating to 5.0. Updating [[Common questions after updating Firefox]] is good and will be useful for future updates, but a focused article on breakage caused by the new versioning scheme could be much more targeted than that, linking to the more general article for other update issues. Since the questions asked about this issue vary but nearly all mention the version change to 5.0, the article needs to include the version number. This could be a different article name for each problem (eg. "A website doesn't work after upgrading to Firefox 5", "Add-ons missing in Firefox 5") or a single generic article (eg. "Update to Firefox 5" or "Questions after updating to Firefox 5") </blockquote> I strongly disagree. People are specifically asking why their toolbars or extensions don't work. Or why a certain a website doesn't work (that might need a new article). Also we specifically call out on the 5.0 what's new page to look at [[Common questions after updating Firefox]] if you are having problems, we shouldn't make a different article with the real answers. <blockquote> Since we're telling people that Firefox 4.0 is no longer an option, and no easy fixes exist other than going back to 3.6 or using a competing browser, I do think a brief explanation of the version scheme change is justified. If we don't mention this in the article, users won't understand why going back to 4.0 is impossible. </blockquote> Yes - I think the key word is brief though.
  14. If I summarize:

    If I summarize: * [[Add-ons are disabled after updating Firefox]] must refer to the [https://addons.mozilla.org/fr/firefox/addon/add-on-compatibility-reporter/ Add-on compatibility reporter] with the risk that users always keep this so useful add-on installed (anyway, it is already referenced in many support answers). * [[Websites look wrong]] must be updated. What are the common symptoms? What are the workarounds?
  15. If this is just a version of Common questions after upgrading from Firefox 3.6 specifically for Firefox 5, why not just add the content to Common questions after upgrading from Firefox 3.6 and use showfor? If people are using "5" in their searches, we can add "5" as a keyword.

    If this is just a version of [[Common questions after updating Firefox]] specifically for Firefox 5, why not just add the content to [[Common questions after updating Firefox]] and use <sup>show</sup>for? If people are using "5" in their searches, we can add "5" as a keyword.
  16. Chris_Ilias said

    If this is just a version of Common questions after upgrading from Firefox 3.6 specifically for Firefox 5, why not just add the content to Common questions after upgrading from Firefox 3.6 and use showfor?

    We don't know if a user upgrades to Firefox 5 from Firefox 3.6 or Firefox 4.0, so showfor can't be used.

    If people are using "5" in their searches, we can add "5" as a keyword.

    Done. See /en-US/kb/common-questions-after-upda.../1532.

    ''Chris_Ilias [[#post-40472|said]]'' <blockquote> If this is just a version of [[Common questions after updating Firefox]] specifically for Firefox 5, why not just add the content to [[Common questions after updating Firefox]] and use <sup>show</sup>for? </blockquote> We don't know if a user upgrades to Firefox 5 from Firefox 3.6 or Firefox 4.0, so showfor can't be used. <blockquote> If people are using "5" in their searches, we can add "5" as a keyword. </blockquote> Done. See [/en-US/kb/common-questions-after-updating-firefox/discuss/1532].