summaryrefslogtreecommitdiffstats
path: root/docs/sgml/faq.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'docs/sgml/faq.sgml')
-rw-r--r--docs/sgml/faq.sgml172
1 files changed, 93 insertions, 79 deletions
diff --git a/docs/sgml/faq.sgml b/docs/sgml/faq.sgml
index 34b952b01..79fa528c4 100644
--- a/docs/sgml/faq.sgml
+++ b/docs/sgml/faq.sgml
@@ -620,6 +620,12 @@
progression states, also require adjusting the program logic to
compensate for the change.
</para>
+ <para>
+ There is no GUI for adding fields to Bugzilla at this
+ time. You can follow development of this feature at
+ <ulink
+ url="http://bugzilla.mozilla.org/show_bug.cgi?id=91037">http://bugzilla.mozilla.org/show_bug.cgi?id=91037</ulink>
+ </para>
</answer>
</qandaentry>
@@ -633,42 +639,62 @@
</para>
</question>
<answer>
- <para>
- This was a late-breaking question for the Guide, so I just have to
- quote the relevant newsgroup thread on it.
- </para>
- <literallayout>
-> AFAIK, most sites (even if they have SSI enabled) won't have #exec cmd
-> enabled. Perhaps what would be better is a #include virtual and a
-> footer.cgi the basically has the "require 'CGI.pl' and PutFooter command.
->
-> Please note that under most configurations, this also requires naming
-> the file from index.html to index.shtml (and making sure that it will
-> still be reconized as an index). Personally, I think this is better on
-> a per-installation basis (perhaps add something to the FAQ that says how
-> to do this).
-
-Good point. Yeah, easy enough to do, that it shouldn't be a big deal for
-someone to take it on if they want it. FAQ is a good place for it.
-
-> Dave Miller wrote:
->
->> I did a little experimenting with getting the command menu and footer on
->> the end of the index page while leaving it as an HTML file...
->>
->> I was successful. :)
->>
->> I added this line:
->>
->> <!--#exec cmd="/usr/bin/perl -e &quot;require 'CGI.pl';
->>PutFooter();&quot;" -->
->>
->> Just before the &lt;/BODY&gt; &lt;/HTML&gt; at the end of the file. And it worked.
->>
->> Thought I'd toss that out there. Should I check this in? For those that
->> have SSI disabled, it'll act like a comment, so I wouldn't think it would
->> break anything.
- </literallayout>
+ <para>
+ It's possible to get the footer on the static index page using
+ Server Side Includes (SSI). The trick to doing this is making
+ sure that your web server is set up to allow SSI and specifically,
+ the #exec directive. You should also rename <filename>index.html</filename>
+ to <filename>index.shtml</filename>.
+ </para>
+ <para>
+ After you've done all that, you can add the following line to
+ <filename>index.shtml</filename>:
+<programlisting>
+<![CDATA[
+<!--#exec cmd="/usr/bin/perl -e &quot;require 'CGI.pl'; PutFooter();&quot;" -->
+]]>
+</programlisting>
+ </para>
+ <para><note>
+ <para>
+ This line will be replaced with the actual HTML for the footer
+ when the page is requested, so you should put this line where you
+ want the footer to appear.
+ </para>
+ </note></para>
+ <para>
+ Because this method depends on being able to use a #exec directive,
+ and most ISP's will not allow that, there is an alternative method.
+ You could have a small script (such as <filename>api.cgi</filename>)
+ that basically looks like:
+<programlisting>
+<![CDATA[
+#!/usr/bonsaitools/bin/perl -w
+
+require 'globals.pl';
+
+if ($::FORM{sub} eq 'PutFooter') {
+ PutFooter();
+} else {
+ die 'api.cgi was incorrectly called';
+}
+]]>
+</programlisting>
+ and then put this line in <filename>index.shtml</filename>.
+<programlisting>
+<![CDATA[
+<!--#include virtual="api.cgi?sub=PutFooter"-->
+]]>
+</programlisting>
+ </para>
+ <para> <note>
+ <para>
+ This still requires being able to use Server Side Includes, if
+ this simply will not work for you, see <ulink
+ url="http://bugzilla.mozilla.org/show_bug.cgi?id=80183">bug 80183</ulink>
+ for a third option.
+ </para>
+ </note></para>
</answer>
</qandaentry>
<qandaentry>
@@ -807,21 +833,6 @@ someone to take it on if they want it. FAQ is a good place for it.
<qandaentry>
<question>
<para>
- Does Bugzilla allow fields to be added, changed or deleted? If I want to
- customize the bug submission form to meet our needs, can I do that using our
- terminology?
- </para>
- </question>
- <answer>
- <para>
- Yes.
- </para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>
Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</para>
@@ -1221,20 +1232,11 @@ someone to take it on if they want it. FAQ is a good place for it.
<para>
If you are using an alternate Mail Transport Agent (MTA other than
sendmail), make sure the options given in the "processmail" script for all
- instances of "sendmail" are correct for your MTA. If you are using Sendmail,
- you may wish to delete the "-ODeliveryMode=deferred" option in the
- "processmail" script for every invocation of "sendmail". (Be sure and leave
- the "-t" option, though!)
- </para>
- <para>
- A better alternative is to change the "-O" option to
- "-ODeliveryMode=background". This prevents Sendmail from hanging your
- Bugzilla Perl processes if the domain to which it must send mail
- is unavailable.
+ instances of "sendmail" are correct for your MTA.
</para>
<para>
- This is now a configurable parameter called "sendmailnow", available
- from editparams.cgi.
+ If you are using Sendmail, try enabling "sendmailnow" in editparams.cgi.
+ If you are using Postfix, you will also need to enable <quote>sendmailnow</quote>.
</para>
</answer>
</qandaentry>
@@ -1315,12 +1317,21 @@ someone to take it on if they want it. FAQ is a good place for it.
</question>
<answer>
<para>
- Run the "sanity check" utility (./sanitycheck.cgi in the bugzilla_home
- directory) to see! If it all comes back, you're OK. If it doesn't come back
- OK (i.e. any red letters), there are certain things Bugzilla can recover
- from and certain things it can't. If it can't auto-recover, I hope you're
- familiar with mysqladmin commands or have installed another way to manage
- your database...
+ Run the <quote>sanity check</quote> utility
+ (<filename>./sanitycheck.cgi</filename> in the
+ Bugzilla_home directory) from your web browser to see! If
+ it finishes without errors, you're
+ <emphasis>probably</emphasis> OK. If it doesn't come back
+ OK (i.e. any red letters), there are certain things
+ Bugzilla can recover from and certain things it can't. If
+ it can't auto-recover, I hope you're familiar with
+ mysqladmin commands or have installed another way to
+ manage your database. Sanity Check, although it is a good
+ basic check on your database integrity, by no means is a
+ substitute for competent database administration and
+ avoiding deletion of data. It is not exhaustive, and was
+ created to do a basic check for the most common problems
+ in Bugzilla databases.
</para>
</answer>
</qandaentry>
@@ -1428,10 +1439,12 @@ someone to take it on if they want it. FAQ is a good place for it.
</question>
<answer>
<para>
- Delete everything from $BUZILLA_HOME/shadow. Bugzilla creates shadow
- files there, with each filename corresponding to a
- bug number. Also be sure to run syncshadowdb to make sure, if you are using
- a shadow database, that the shadow database is current.
+ This should only happen with Bugzilla &bz-ver; if you are
+ using the <quote>shadow database</quote> feature, and your
+ shadow database is out of sync. Try running
+ <filename>syncshadowdb</filename>
+ <option>-syncall</option> to make sure your shadow
+ database is in synch with your primary database.
</para>
</answer>
</qandaentry>
@@ -1752,14 +1765,14 @@ A: Sure! Here ya go!
</question>
<answer>
<para>
- Try <ulink url="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;product=Webtools&amp;component=Bugzilla">
+ Try <ulink url="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;product=Bugzilla">
this link</ulink> to view current bugs or requests for
enhancement for Bugzilla.
</para>
<para>
- You can view bugs marked for 2.14 release
- <ulink url="http://bugzilla.mozilla.org/buglist.cgi?product=Webtools&amp;component=Bugzilla&amp;target_milestone=Bugzilla+2.14">here</ulink>.
- This list includes bugs for the 2.14 release that have already
+ You can view bugs marked for 2.16 release
+ <ulink url="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&amp;target_milestone=Bugzilla+2.16">here</ulink>.
+ This list includes bugs for the 2.16 release that have already
been fixed and checked into CVS. Please consult the
<ulink url="http://www.mozilla.org/projects/bugzilla/">
Bugzilla Project Page</ulink> for details on how to
@@ -1800,8 +1813,9 @@ A: Sure! Here ya go!
<orderedlist>
<listitem>
<para>
- Enter a bug into bugzilla.mozilla.org for the "Webtools" product,
- "Bugzilla" component.
+ Enter a bug into bugzilla.mozilla.org for the <quote><ulink
+ url="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla">Bugzilla</ulink></quote>
+ product.
</para>
</listitem>
<listitem>