Knowledge Base discussions

[in KB] Proposal for Firefox about:config article. Any particular reason ...

  1. more options
    ... that "we" don't have an '''about:config''' KB article? Considering the number of times a month that "we" refer users over here - http://kb.mozillazine.org/About:config https://support.mozilla.org/en-US/search/advanced?q=http%3A%2F%2Fkb.mozillazine.org%2FAbout%3Aconfig&is_locked=0&num_voted=0&num_votes=&asked_by=&answered_by=&q_tags=&product=firefox&created=0&created_date=&updated=0&updated_date=&sortby=0&a=&w=2
  2. I did an Advanced Search on "about:config" + article and found another discussion on this from last year, for some background:

    Thunderbird has a Config Editor article so I see no reason why Firefox doesn't.

    I did an Advanced Search on [https://support.mozilla.org/en-US/search/advanced?q=%22about%3Aconfig%22+%2B+article&author=&created=0&created_date=&updated=0&updated_date=&sortby=0&a=&w=4 "about:config" + article] and found another discussion on this from last year, for some background: * [/forums/knowledge-base-articles/709734] Am I missing something? No specific "about:" support articles. Thunderbird has a [[Config Editor]] article so I see no reason why Firefox doesn't.
  3. If the problem is that people are not able to visualize the value of the article, this might be a case where "post first and ask permission later" would be a good approach. That's why we have a wiki, right? ;-)

    Some advanced topics I think would be nice to have in the article would be:

    • The relationship between about:config and prefs.js (we sometimes discuss this when having to reset printer-related preferences).
    • What could appear in the Status column other than default or user set, such as "locked" and what that might mean.
    • Why there are "user set" preferences that the user never heard of and aren't in any dialog. Many are computed values that Firefox uses behind the scenes, such as how much disk space to use for cached files, when it last checked for updates, and whether Firefox completed a one-time operation. These should not be changed or reset without specific guidance.
    If the problem is that people are not able to visualize the value of the article, this might be a case where "post first and ask permission later" would be a good approach. That's why we have a wiki, right? ;-) Some advanced topics I think would be nice to have in the article would be: * The relationship between about:config and prefs.js (we sometimes discuss this when having to reset printer-related preferences). * What could appear in the Status column other than default or user set, such as "locked" and what that might mean. * Why there are "user set" preferences that the user never heard of and aren't in any dialog. Many are computed values that Firefox uses behind the scenes, such as how much disk space to use for cached files, when it last checked for updates, and whether Firefox completed a one-time operation. These should not be changed or reset without specific guidance.
  4. I changed the thread title to make it more descriptive.

    If anyone wants to draft a new "Configuration Editor" KB article for Firefox (assuming Joni doesn't object) just don't include the term about:config in the title. That's because a colon in the article title would prevent wiki markup links (bug 749835) . Ref: Writing guide for Knowledge Base articles under "Pick a good title".

    I changed the thread title to make it more descriptive. If anyone wants to draft a new "Configuration Editor" KB article for Firefox (assuming Joni doesn't object) just don't include the term about:config in the title. That's because a colon in the article title would prevent wiki markup links ([https://bugzilla.mozilla.org/show_bug.cgi?id=749835 bug 749835]) . Ref: [[How to write Knowledge Base articles]] under "Pick a good title".
  5. more options

    I'm gonna start this posting with what I think the title of an about:config might be to avoid that colon wiki markup issue.

    Configuration Editor for Advanced Preferences in Firefox The actual page name could be shorter, like config-editor-firefox.

    Yes / NO / or other suggestions


    https://support.mozilla.org/en-US/forums/knowledge-base-articles/709734 I guess that about: ... pages are my 'grind' for November, becoming an annual thing.

    IMO, one article that mentions and briefly describes each about: ... item contained in about:about is needed. And when a more lengthy explanation is needed, provide a hyperlink to its' own article. Too many of those about: URI schemes are needed by some fairly inexperienced users, like for retrieving Crash ID's and Sync logs.

    As far as about:config goes, I feel that we need its' one article because support contributors and the "canned responses" make mention of it on a daily basis for one reason or another. It would be a lot easier, and maybe more of an 'official' procedure, along with appearing more acceptable, if we had support documentation for about:config . I don't think we need to go into great detail, as with the About:config article in the MozillaZine KB - maybe just resetting preferences with an image of the about:config panel, including the contextual menu high-lighting Reset. Adding and modifying prefs can be left to the support contributor, if that idea is more palatable to getting this type of article into the SUMO KB. Or added as a separate article at a later date if the main one receives enough hits and resultant questions about adding and modifying are posted in the forum.

    I am growing increasing more dismayed at the number of times we refer SUMO users over to the MozillaZine KB; although I still provide support to Firefox users over there every day in addition to SUMO, so I am not a 'hater' of MozillaZine. I just think the official Mozilla Firefox forum - SUMO- needs a similar article. One thing I have never liked about the MozillaZIne KB is the way the page titles - http://kb.mozillazine.org/About:config - need a capital letter to start and then the explanation - "The correct title of this article is about:config. It appears incorrectly here due to technical limitations in the wiki software." I have seen users in this forum who tried using About:config and couldn't open it! I have seen that at least once this month, which has gotten me to think about this situation again, this November.

    Ed

    I'm gonna start this posting with what I think the title of an '''about:config''' might be to avoid that '''''colon''''' wiki markup issue. '''Configuration Editor for Advanced Preferences in Firefox''' ''The actual page name could be shorter, like '''config-editor-firefox'''''. Yes / NO / or other suggestions --------------- https://support.mozilla.org/en-US/forums/knowledge-base-articles/709734 I guess that '''about: ...''' pages are my 'grind' for November, becoming an annual thing. IMO, one article that mentions and briefly describes each about: ... item contained in '''about:about''' is needed. And when a more lengthy explanation is needed, provide a hyperlink to its' own article. Too many of those about: URI schemes are needed by some fairly inexperienced users, like for retrieving Crash ID's and Sync logs. As far as '''about:config''' goes, I feel that we need its' one article because support contributors and the "canned responses" make mention of it on a daily basis for one reason or another. It would be a lot easier, and maybe more of an 'official' procedure, along with appearing more acceptable, if we had support documentation for about:config . I don't think we need to go into great detail, as with the About:config article in the MozillaZine KB - maybe just resetting preferences with an image of the about:config panel, including the contextual menu high-lighting '''Reset'''. Adding and modifying prefs can be left to the support contributor, if that idea is more palatable to getting this type of article into the SUMO KB. Or added as a separate article at a later date if the main one receives enough hits and resultant questions about adding and modifying are posted in the forum. I am growing increasing more dismayed at the number of times we refer SUMO users over to the MozillaZine KB; ''although I still provide support to Firefox users over there every day in addition to SUMO, so I am not a 'hater' of MozillaZine''. I just think the official Mozilla Firefox forum - SUMO- needs a similar article. One thing I have never liked about the MozillaZIne KB is the way the page titles - http://kb.mozillazine.org/About:config - need a capital letter to start and then the explanation - ''"The correct title of this article is about:config. It appears incorrectly here due to technical limitations in the wiki software." '' I have seen users in this forum who tried using '''About:config''' and couldn't open it! I have seen that at least once this month, which has gotten me to think about this situation again, this November. Ed
  6. I would leave out "Advanced Preferences" and just title it Configuration Editor for Firefox (you can use that link to start an article) and adjust the "slug". A reviewer can always rename the article or edit the description if necessary, later on. Once you get the article started by submitting it, you can revise it later to add screenshots or edit the content, before or after it's approved for the KB. . You might want or might not to use the aboutconfig template by adding it to the article (see Using Templates).

    I would leave out "Advanced Preferences" and just title it [[Configuration Editor for Firefox]] (you can use that link to start an article) and adjust the "slug". A reviewer can always rename the article or edit the description if necessary, later on. Once you get the article started by submitting it, you can revise it later to add screenshots or edit the content, before or after it's approved for the KB. . You might want or might not to use the [/kb/Template%3Aaboutconfig aboutconfig template] by adding it to the article (see [[How to use Templates]]).
  7. I think it's important to answer the questions:

    • Why are you pointing people to the MZ article?
    • Why are you pointing people to about:config?
    • How have things changed since the monkey rule was created?

    From those answers, it should be easier to determine if an article on how to use about:config is needed and allowed.

    I think it's important to answer the questions: * Why are you pointing people to the MZ article? * Why are you pointing people to about:config? * How have things changed since the monkey rule was created? From those answers, it should be easier to determine if an article on how to use about:config is needed and allowed.
  8. there appears to be some rudimentary documentation about preferences at https://developer.mozilla.org/en-US/docs/Mozilla/Preferences/Preference_reference - maybe expand this instead of maintaining the content at different places (which will be a pain to keep updated and localised)...

    edit: probably misunderstood ed's suggestion at first - it's less about documenting the single preferences than how to use about:config in the first place...

    there appears to be some rudimentary documentation about preferences at https://developer.mozilla.org/en-US/docs/Mozilla/Preferences/Preference_reference - maybe expand this instead of maintaining the content at different places (which will be a pain to keep updated and localised)... edit: probably misunderstood ed's suggestion at first - it's less about documenting the single preferences than how to use about:config in the first place...

    Modified by philipp on

  9. Speaking of MDN, https://developer.mozilla.org/en-US/docs/Preferences_API links to http://kb.mozillazine.org/About:config apparently because there IS NO mozilla.org article with that information. So does https://developer.mozilla.org/en-US/Add-ons/Plugins/Out_of_process_plugins/The_plugin_hang_detector which is linked from our Send plugin crash reports to help Mozilla improve Firefox article's "Developing for Flash with Flex?" section.

    It's strange to me that neither developer.mozilla.org nor support.mozilla.org has a guide for using about:config, except for the Thunderbird Config Editor article (History: Imported from SUMOMO 2014-02-14) and that MDN articles link to mozillaZine's KB.

    Switching gears, the Firefox Support troubleshooting Guide "How to contribute" article has a Using about:config section (which was copied from the old Live Chat troubleshooting guide):


    == Using about:config == '''about:config''' is an interface for editing advanced Firefox preferences, which is often necessary to fix problems when they are set wrong. {warning}'''Warning''': about:config can be a nifty tool but it can also be dangerous and render Firefox inoperable. Be careful when editing about:config.{/warning} *The screencast below shows how to use about:config to fix User Agent problems. [[Video:ea87f10da5f2a0ebdafa0e259a00b129-1249154303-228-0]]


    The video itself is quite old. It's located in the Media Gallery: https://support.mozilla.org/en-US/gallery/video/49

    I just thought it interesting that, back in 2009, Live Chat contributors were trained in using about:config to help Firefox users solve problems but we never actually created a KB article where we could refer users. Isn't the KB supposed to be a self-help tool? Is the Reset Firefox feature supposed to be the universal fix for preference issues? The next best article is Reset Firefox preferences to troubleshoot and fix problems which doesn't even explain how to reset individual preferences like the 2009 video does.

    Speaking of MDN, https://developer.mozilla.org/en-US/docs/Preferences_API links to http://kb.mozillazine.org/About:config apparently because there IS NO mozilla.org article with that information. So does https://developer.mozilla.org/en-US/Add-ons/Plugins/Out_of_process_plugins/The_plugin_hang_detector which is linked from our [[Send plugin crash reports to help Mozilla improve Firefox]] article's "Developing for Flash with Flex?" section. It's strange to me that neither developer.mozilla.org nor support.mozilla.org has a guide for using about:config, except for the Thunderbird [[Config Editor]] article (History: ''Imported from SUMOMO 2014-02-14'') and that MDN articles link to mozillaZine's KB. Switching gears, the [[Firefox Support troubleshooting Guide]] "How to contribute" article has a '''[/kb/firefox-support-troubleshooting-guide#w_using-aboutconfig Using about:config]''' section (which was copied from the old [[Live Chat troubleshooting guide]]): ----- <nowiki>== Using about:config == '''about:config''' is an interface for editing advanced Firefox preferences, which is often necessary to fix problems when they are set wrong. {warning}'''Warning''': about:config can be a nifty tool but it can also be dangerous and render Firefox inoperable. Be careful when editing about:config.{/warning} *The screencast below shows how to use about:config to fix User Agent problems. [[Video:ea87f10da5f2a0ebdafa0e259a00b129-1249154303-228-0]]</nowiki> ----- The video itself is quite old. It's located in the Media Gallery: https://support.mozilla.org/en-US/gallery/video/49 I just thought it interesting that, back in 2009, Live Chat contributors were trained in using about:config to help Firefox users solve problems but we never actually created a KB article where we could refer users. Isn't the KB supposed to be a self-help tool? Is the [[Reset Firefox – easily fix most problems|Reset Firefox]] feature supposed to be the universal fix for preference issues? The next best article is [[Reset Firefox preferences to troubleshoot and fix problems]] which doesn't even explain how to reset individual preferences like the 2009 video does.
  10. more options

    Chris asked:

    Why are you pointing people to the MZ article? Not just me, many support contributors refer questions owners over there for an explanation of about:config - due the SUMO KB not having an explanation of that hidden advanced feature for editing preferences. It's also used for adding a new preference sometimes.It seems that the original contributors here [circa 2007-08], who came over here from MozillaZIne fora, tend to refer users over there more frequently than newer contributors do.

    Why are you pointing people to about:config? Seriously? To provide support as far as the "hidden" advanced preferences and for modifications to Firefox. The reference to about:config in SUMO threads has increased greatly [IMO] since around Firefox 5.0 or so, when the removal of "standard" preferences from Options started.

    How have things changed since the monkey rule was created? I have no idea what that "rule" is about.

    Chris asked: '''''Why are you pointing people to the MZ article? ''''' Not just me, many support contributors refer questions owners over there for an explanation of about:config - due the SUMO KB not having an explanation of that hidden advanced feature for editing preferences. It's also used for adding a new preference sometimes.''It seems that the original contributors here [circa 2007-08], who came over here from MozillaZIne fora, tend to refer users over there more frequently than newer contributors do.'' '''''Why are you pointing people to about:config? ''''' Seriously? To provide support as far as the "hidden" advanced preferences and for modifications to Firefox. The reference to about:config in SUMO threads has increased greatly ''[IMO]'' since around Firefox 5.0 or so, when the removal of "standard" preferences from Options started. '''''How have things changed since the monkey rule was created? ''''' I have no idea what that "rule" is about.
  11. The monkey rule was the result of the initial discussion that Alice pointed a link to in the original thread you started on this subject on the issue of telling users to use about:config.

    Basically, about:config is not intended for end-users, and it is not recommended for users who aren't experts (or at least know how to back and restore their info). However there are situations where users need to go there in order to fix a problem. So it was decided that the KB would only point users to about:config for troubleshooting problems, and not for usecases where the user is customizing Firefox, or just "monkeying around" with it. Hence the name of the rule. :) We did allow exceptions for questions that were very common.

    Of course, all of that was a long time ago, and KB policy may have changed.

    That's why it's important to know why you are pointing users to about:config, and why they are pointed to a whole article after that.

    But that should answer your original question on why there's no article for it right now.

    The monkey rule was the result of the initial discussion that Alice pointed a link to in the original thread you started on this subject on the issue of telling users to use about:config. Basically, about:config is not intended for end-users, and it is not recommended for users who aren't experts (or at least know how to back and restore their info). However there are situations where users need to go there in order to fix a problem. So it was decided that the KB would only point users to about:config for troubleshooting problems, and not for usecases where the user is customizing Firefox, or just "''monkeying around''" with it. Hence the name of the rule. :) We did allow exceptions for questions that were very common. Of course, all of that was a long time ago, and KB policy may have changed. That's why it's important to know why you are pointing users to about:config, and why they are pointed to a whole article after that. But that should answer your original question on why there's no article for it right now.
  12. Chris Ilias said

    That's why it's important to know why you are pointing users to about:config, and why they are pointed to a whole article after that.

    probably because some of the problems can be solved only in about:config. eg.

    not all users want every 40 days to change their habits, it may be good for firefox developers for some reason, but not for lots of users.

    another example :

    the broken security protocol for sites after disable (and correct) the ssl3 in 34.

    another one, more older :

    We are not talking about hacking the configuration, just simply useful answers to help people with problems, we are firefox support aren't we ? So we want an about:config KB article from/and for firefox not only from mozillazine. I think we have a lot of good contributors for help to write the article, to be specific, accurate, more helpful.


    cheers to all

    thank you

    ''Chris Ilias [[#post-63187|said]]'' <blockquote> That's why it's important to know why you are pointing users to about:config, and why they are pointed to a whole article after that. </blockquote> probably because some of the problems can be solved only in about:config. eg. * [https://support.mozilla.org/en-US/questions/1036311 How do i get rid of the new firefox 34 popdown search menu?] not all users want every 40 days to change their habits, it may be good for firefox developers for some reason, but not for lots of users. another example : * [https://support.mozilla.org/en-US/questions/1035913 How do I activate SSLv3 so I can utilize my computer says broken protocol.With Explorer I just made sure it was clicked on.] the broken security protocol for sites after disable (and correct) the ssl3 in 34. another one, more older : * [https://support.mozilla.org/en-US/questions/994809 How to disable javascript in Firefox 29.0 ?] We are not talking about hacking the configuration, just simply useful answers to help people with problems, we are firefox support aren't we ? So we want an about:config KB article from/and for firefox not only from mozillazine. I think we have a lot of good contributors for help to write the article, to be specific, accurate, more helpful. cheers to all thank you
  13. How does an article on about:config answer those user questions? You still need to specify which pref to edit, and its value. So that still doesn't answer the question of why you're pointing people to an article. Is it to explain how to use about:config? Is it to explain what about:config is? Are users discovering about:config from answers to their questions, then asking what all the other prefs are for?

    If it's to list every pref, and it's values, I say would disagree with having that article. If it's to explain how to use about:config, I don't think that article is needed. If it's to explain what about:config is, I would agree with creating that article.

    How does an article on about:config answer those user questions? You still need to specify which pref to edit, and its value. So that still doesn't answer the question of why you're pointing people to an article. Is it to explain how to use about:config? Is it to explain what about:config is? Are users discovering about:config from answers to their questions, then asking what all the other prefs are for? If it's to list every pref, and it's values, I say would disagree with having that article. If it's to explain how to use about:config, I don't think that article is needed. If it's to explain what about:config is, I would agree with creating that article.
  14. Chris Ilias said

    How does an article on about:config answer those user questions? You still need to specify which pref to edit, and its value. So that still doesn't answer the question of why you're pointing people to an article.

    Yes, correct, but we have to start from somewhere otherwise questions will remain unanswered.Maybe when the time come for that (to suggest an about:config preferencee change) because we have not other option (as the questions in my above reply), then we can create an article for that and pointing to that article !

    Chris Ilias said

    Is it to explain how to use about:config? Is it to explain what about:config is? Are users discovering about:config from answers to their questions, then asking what all the other prefs are for?

    Yes it is, and to explain how the use of about:config and to explain what is the about:config. For the 3rd question I was not ever asked what all the prefs is in the about:config.

    Chris Ilias said

    If it's to list every pref, and it's values, I say would disagree with having that article. If it's to explain how to use about:config, I don't think that article is needed. If it's to explain what about:config is, I would agree with creating that article.

    For question 1, yes i don't say it easy that one, but how my above suggestion, "create an article only when we have to" ? For question 2, why ? it is free software isn't it, maybe more people want to known.....why not ? For question 3, finally i think we agree in that point :-) :-)

    hey, come on, it is not so big deal to write some article for about:config, i'm sorry but i can not understand why to not do that, except if exist a reason that i don't know, and that reason have a effect for the work of developers or..... really i don't known !!!

    I am only volunteer, just to help and definitely nothing more. And as already write in my above reply, definitely we have good contributors for help to write the article, to be specific, accurate, more helpful (and maybe find someone with talent for this and explore his/her talent in this area, no that one is not me, please don't confuse)


    thank you

    ''Chris Ilias [[#post-63257|said]]'' <blockquote> How does an article on about:config answer those user questions? You still need to specify which pref to edit, and its value. So that still doesn't answer the question of why you're pointing people to an article. </blockquote> Yes, correct, but we have to start from somewhere otherwise questions will remain unanswered.Maybe when the time come for that (to suggest an about:config preferencee change) because we have not other option (as the questions in my [https://support.mozilla.org/en-US/forums/knowledge-base-articles/710892?last=63257#post-63233 above reply]), then we can create an article for that and pointing to that article ! ''Chris Ilias [[#post-63257|said]]'' <blockquote> Is it to explain how to use about:config? Is it to explain what about:config is? Are users discovering about:config from answers to their questions, then asking what all the other prefs are for? </blockquote> Yes it is, and to explain how the use of about:config and to explain what is the about:config. For the 3rd question I was not ever asked what all the prefs is in the about:config. ''Chris Ilias [[#post-63257|said]]'' <blockquote> If it's to list every pref, and it's values, I say would disagree with having that article. If it's to explain how to use about:config, I don't think that article is needed. If it's to explain what about:config is, I would agree with creating that article. </blockquote> For question 1, yes i don't say it easy that one, but how my above suggestion, "create an article only when we have to" ? For question 2, why ? it is free software isn't it, maybe more people want to known.....why not ? For question 3, finally i think we agree in that point :-) :-) hey, come on, it is not so big deal to write some article for about:config, i'm sorry but i can not understand why to not do that, except if exist a reason that i don't know, and that reason have a effect for the work of developers or..... really i don't known !!! I am only volunteer, just to ''help and definitely nothing more''. And as already write in my above reply, definitely we have good contributors for help to write the article, to be specific, accurate, more helpful (and maybe find someone with talent for this and explore his/her talent in this area, <sub>no that one is not me, please don't confuse</sub>) thank you
  15. I was just about to create a "What is about:config" article, when I remembered we can't have colons in article titles.

    I was just about to create a "What is about:config" article, when I remembered we can't have colons in article titles.
  16. (Like I said above) If anyone wants to draft a new "Configuration Editor" KB article for Firefox just don't include the term about:config in the title. That's because a colon in the article title would prevent wiki markup links (bug 749835) . Ref: Writing guide for Knowledge Base articles under "Pick a good title".

    My suggestion (above) was: "Configuration Editor for Firefox".

    (Like [[#post-62958| I said above]]) If anyone wants to draft a new "Configuration Editor" KB article for Firefox just don't include the term about:config in the title. That's because a colon in the article title would prevent wiki markup links ([https://bugzilla.mozilla.org/show_bug.cgi?id=749835 bug 749835]) . Ref: [[How to write Knowledge Base articles]] under "Pick a good title". My suggestion (above) was: "Configuration Editor for Firefox".
  17. One should also note that some important settings can only be reached thru the config page. For example; about:newtab

    However, there are some add-ons that can reach many hidden settings.

    One should also note that some important settings can only be reached thru the config page. For example; '''about:newtab''' However, there are some add-ons that can reach many hidden settings.
  18. FredMcD said

    One should also note that some important settings can only be reached thru the config page. For example; about:newtab However, there are some add-ons that can reach many hidden settings.

    I don't think I understand you, Fred. about:newtab is not a setting; it's a separate about: page. Are you referring to browser.newtab.url? That's covered in the article Customize your Firefox New Tab page.

    ''FredMcD [[#post-65478|said]]'' <blockquote> One should also note that some important settings can only be reached thru the config page. For example; '''about:newtab''' However, there are some add-ons that can reach many hidden settings. </blockquote> I don't think I understand you, Fred. ''about:newtab'' is not a setting; it's a separate ''about:'' page. Are you referring to ''browser.newtab.url''? That's covered in the article [[New Tab Page - show, hide and customize top sites]].
  19. What I meant was changing the browser.newtab.url setting,

    What I meant was changing the '''browser.newtab.url''' setting,
  20. I created a placeholder for a new Configuration Editor for Firefox article, if anyone wants to start adding content. It's currently in the Administration category so it won't show up in search results.

    I created a placeholder for a new [[Configuration Editor for Firefox]] article, if anyone wants to start adding content. It's currently in the Administration category so it won't show up in search results.