Commit 591e32cd authored by uid623's avatar uid623

Documentation patch for bug 338434: update newsgroup links in the documentation;…

Documentation patch for bug 338434: update newsgroup links in the documentation; patch by Emmanuel Seyman, r=vladd.
parent 90458269
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [ <!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!ENTITY conventions SYSTEM "conventions.xml"> ] > --> <!ENTITY conventions SYSTEM "conventions.xml"> ] > -->
<!-- $Id: about.xml,v 1.23 2008/04/04 06:48:15 jocuri%softhome.net Exp $ --> <!-- $Id: about.xml,v 1.24 2008/04/04 06:48:16 uid623 Exp $ -->
<chapter id="about"> <chapter id="about">
<title>About This Guide</title> <title>About This Guide</title>
...@@ -209,9 +209,10 @@ ...@@ -209,9 +209,10 @@
<para> <para>
Also, thanks are due to the members of the Also, thanks are due to the members of the
<ulink url="news://news.mozilla.org/netscape.public.mozilla.webtools"> <ulink url="news://news.mozilla.org/mozilla.support.bugzilla">
netscape.public.mozilla.webtools</ulink> mozilla.support.bugzilla</ulink>
newsgroup. Without your discussions, insight, suggestions, and patches, newsgroup (and its predecessor, netscape.public.mozilla.webtools).
Without your discussions, insight, suggestions, and patches,
this could never have happened. this could never have happened.
</para> </para>
</section> </section>
......
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"> --> <!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"> -->
<!-- $Id: troubleshooting.xml,v 1.3 2008/04/04 06:48:15 jake%bugzilla.org Exp $ --> <!-- $Id: troubleshooting.xml,v 1.10 2008/04/04 06:48:22 uid623 Exp $ -->
<appendix id="troubleshooting"> <appendix id="troubleshooting">
<title>Troubleshooting</title> <title>Troubleshooting</title>
...@@ -15,7 +15,7 @@ ...@@ -15,7 +15,7 @@
completion, it normally explains what's wrong and how to fix it. 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 If you can't work it out, or if it's being uncommunicative, post
the errors in the the errors in the
<ulink url="news://news.mozilla.org/netscape.public.mozilla.webtools">netscape.public.mozilla.webtools</ulink> <ulink url="news://news.mozilla.org/mozilla.support.bugzilla">mozilla.support.bugzilla</ulink>
newsgroup. newsgroup.
</para> </para>
...@@ -29,6 +29,19 @@ ...@@ -29,6 +29,19 @@
fix the problem. If not, see below for some commonly-encountered fix the problem. If not, see below for some commonly-encountered
errors. If that doesn't help, post the errors to the newsgroup. errors. If that doesn't help, post the errors to the newsgroup.
</para> </para>
<para>
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
<filename>errorlog</filename>, in the Bugzilla <filename>data</filename>
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
<filename>errorlog</filename> file.
</para>
</section> </section>
<section id="trbl-testserver"> <section id="trbl-testserver">
...@@ -257,13 +270,11 @@ at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.</programlisting> ...@@ -257,13 +270,11 @@ at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.</programlisting>
past and need to set it to something more restrictive past and need to set it to something more restrictive
(i.e. <quote>/bugzilla/</quote>), you can safely do this without (i.e. <quote>/bugzilla/</quote>), you can safely do this without
requiring users to delete their Bugzilla-related cookies in their requiring users to delete their Bugzilla-related cookies in their
browser (this is true starting with browser (this is true starting with Bugzilla 2.18 and Bugzilla 2.16.5).
<!-- Need OR logic here for bz-devel logic here -->
Bugzilla 2.18<![%bz-devel;[, Bugzilla 2.17.7,]]> and Bugzilla 2.16.5).
</para> </para>
</section> </section>
<section> <section id="trbl-relogin-some">
<title>Some users are constantly being forced to relogin</title> <title>Some users are constantly being forced to relogin</title>
<para>First, make sure cookies are enabled in the user's browser. <para>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.</programlisting> ...@@ -277,8 +288,7 @@ at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.</programlisting>
log in again. log in again.
</para> </para>
<para>If you are using 2.18 <para>If you are using 2.18 (or later), there is a
<![%bz-devel[(or 2.17.1 in the development series)]]>, there is a
parameter called <quote>loginnetmask</quote>, which you can use to set parameter called <quote>loginnetmask</quote>, which you can use to set
the number of bits of the user's IP address to require to be matched when 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, 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.</programlisting> ...@@ -308,6 +318,31 @@ at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.</programlisting>
</section> </section>
<section id="trbl-passwd-encryption">
<title>
checksetup.pl reports "Client does not support authentication protocol
requested by server..."
</title>
<para>
This error is occurring because you are using the new password
encryption that comes with MySQL 4.1, while your
<filename>DBD::mysql</filename> module was compiled against an
older version of MySQL. If you recompile <filename>DBD::mysql</filename>
against the current MySQL libraries (or just obtain a newer version
of this module) then the error may go away.
</para>
<para>
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:
<ulink url="http://dev.mysql.com/doc/mysql/en/Old_client.html"/>
</para>
</section>
</appendix> </appendix>
<!-- Keep this comment at the end of the file <!-- Keep this comment at the end of the file
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment