From 591e32cd2985957473cd7fd1c33d21b596ae205d Mon Sep 17 00:00:00 2001 From: uid623 <> Date: Fri, 4 Apr 2008 11:48:16 +0000 Subject: Documentation patch for bug 338434: update newsgroup links in the documentation; patch by Emmanuel Seyman, r=vladd. --- docs/en/xml/about.xml | 9 ++++---- docs/en/xml/troubleshooting.xml | 51 ++++++++++++++++++++++++++++++++++------- 2 files changed, 48 insertions(+), 12 deletions(-) diff --git a/docs/en/xml/about.xml b/docs/en/xml/about.xml index ff19b0e43..14310d2af 100644 --- a/docs/en/xml/about.xml +++ b/docs/en/xml/about.xml @@ -1,6 +1,6 @@ - + About This Guide @@ -209,9 +209,10 @@ Also, thanks are due to the members of the - - netscape.public.mozilla.webtools - newsgroup. Without your discussions, insight, suggestions, and patches, + + mozilla.support.bugzilla + newsgroup (and its predecessor, netscape.public.mozilla.webtools). + Without your discussions, insight, suggestions, and patches, this could never have happened. diff --git a/docs/en/xml/troubleshooting.xml b/docs/en/xml/troubleshooting.xml index c65c073c4..a2e1acb04 100644 --- a/docs/en/xml/troubleshooting.xml +++ b/docs/en/xml/troubleshooting.xml @@ -1,5 +1,5 @@ - + Troubleshooting @@ -15,7 +15,7 @@ completion, it normally explains what's wrong and how to fix it. If you can't work it out, or if it's being uncommunicative, post the errors in the - netscape.public.mozilla.webtools + mozilla.support.bugzilla newsgroup. @@ -29,6 +29,19 @@ fix the problem. If not, see below for some commonly-encountered errors. If that doesn't help, post the errors to the newsgroup. + + + Bugzilla can also log all user-based errors (and many code-based errors) + that occur, without polluting the web server error log. To enable + Bugzilla error logging, create a file that Bugzilla can write to, named + errorlog, in the Bugzilla data + directory. Errors will be logged as they occur, and will include the type + of the error, the IP address and username (if available) of the user who + triggered the error, and the values of all environment variables; if a + form was being submitted, the data in the form will also be included. + To disable error logging, delete or rename the + errorlog file. +
@@ -257,13 +270,11 @@ at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233. past and need to set it to something more restrictive (i.e. /bugzilla/), you can safely do this without requiring users to delete their Bugzilla-related cookies in their - browser (this is true starting with - - Bugzilla 2.18 and Bugzilla 2.16.5). + browser (this is true starting with Bugzilla 2.18 and Bugzilla 2.16.5).
-
+
Some users are constantly being forced to relogin First, make sure cookies are enabled in the user's browser. @@ -277,8 +288,7 @@ at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233. log in again. - If you are using 2.18 - , there is a + If you are using 2.18 (or later), there is a parameter called loginnetmask, which you can use to set the number of bits of the user's IP address to require to be matched when authenticating the cookies. If you set this to something less than 32, @@ -308,6 +318,31 @@ at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.
+
+ + checksetup.pl reports "Client does not support authentication protocol + requested by server..." + + + + This error is occurring because you are using the new password + encryption that comes with MySQL 4.1, while your + DBD::mysql module was compiled against an + older version of MySQL. If you recompile DBD::mysql + against the current MySQL libraries (or just obtain a newer version + of this module) then the error may go away. + + + + If that does not fix the problem, or if you cannot recompile the + existing module (e.g. you're running Windows) and/or don't want to + replace it (e.g. you want to keep using a packaged version), then a + workaround is available from the MySQL docs: + + + +
+