From 58593ba9d058e7fdd2fbac2d45dafefcbc6bbb4e Mon Sep 17 00:00:00 2001 From: "barnboy%trilobyte.net" <> Date: Thu, 30 Aug 2001 00:25:24 +0000 Subject: Buncha' release updates. Moved all images to ./images so we don't have multiple copies of the same image, fixed these doc bugs (in no particular order): 94949 97070 97071 97114 96498 95970 96677 94953 96501 96679 97068 97191 97192 --- docs/html/faq.html | 677 +++++++++++++++++++++++++++++++---------------------- 1 file changed, 401 insertions(+), 276 deletions(-) (limited to 'docs/html/faq.html') diff --git a/docs/html/faq.html b/docs/html/faq.html index 0765b564a..eea2d6b3d 100644 --- a/docs/html/faq.html +++ b/docs/html/faq.html @@ -10,8 +10,8 @@ REL="HOME" TITLE="The Bugzilla Guide" HREF="index.html">Prev
A.1.9. Terry Weissman answers,
Here's Terry Weissman's comment, for some historical context:
Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:
There is no GUI for adding fields to Bugzilla at this + time. You can follow development of this feature at + http://bugzilla.mozilla.org/show_bug.cgi?id=91037 +
This was a late-breaking question for the Guide, so I just have to - quote the relevant newsgroup thread on it. -
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 index.html + to index.shtml. +> AFAIK, most sites (even if they have SSI enabled) won't have #exec cmd
After you've done all that, you can add the following line to + index.shtml: +
-> 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:
->>
->>
->>
->> Just before the </BODY> </HTML> 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.
-+
<!--#exec cmd="/usr/bin/perl -e "require 'CGI.pl'; PutFooter();"" -->
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. +
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 api.cgi) + that basically looks like: +
+ and then put this line in index.shtml. +
#!/usr/bonsaitools/bin/perl -w + +require 'globals.pl'; + +if ($::FORM{sub} eq 'PutFooter') { + PutFooter(); +} else { + die 'api.cgi was incorrectly called'; +}+
<!--#include virtual="api.cgi?sub=PutFooter"-->
This still requires being able to use Server Side Includes, if + this simply will not work for you, see bug 80183 + for a third option. +
A.4.14. 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? -
Yes. -
A.4.15. Has anyone converted Bugzilla to another language to be used in other countries? Is it localizable?
A.4.16. A.4.15. Can a user create and save reports? Can they do this in Word format? Excel format?
A.4.17. A.4.16. Can a user re-run a report with a new project, same query?
A.4.18. A.4.17. Can a user modify an existing report and then save it into another name?
A.4.19. A.4.18. Does Bugzilla have the ability to search by word, phrase, compound search?
A.4.20. A.4.19. Can the admin person establish separate group and individual user privileges?
A.4.21. A.4.20. Does Bugzilla provide record locking when there is simultaneous access to the same bug? Does the second person get a notice that the bug is in use or how are they notified? @@ -2196,10 +2292,10 @@ CLASS="QANDAENTRY" CLASS="QUESTION" >
A.4.22. A.4.21. Are there any backup features provided?
A.4.23. A.4.22. Can users be on the system while a backup is in progress?
A.4.24. A.4.23. What type of human resources are needed to be on staff to install and maintain Bugzilla? Specifically, what type of skills does the person need to have? I need to find out if we were to go with Bugzilla, what types of @@ -2287,10 +2383,10 @@ CLASS="QANDAENTRY" CLASS="QUESTION" >
A.4.25. A.4.24. What time frame are we looking at if we decide to hire people to install and maintain the Bugzilla? Is this something that takes hours or weeks to install and a couple of hours per week to maintain and customize or is this @@ -2318,10 +2414,10 @@ CLASS="QANDAENTRY" CLASS="QUESTION" >
A.4.26. A.4.25. Is there any licensing fee or other fees for using Bugzilla? Any out-of-pocket cost other than the bodies needed as identified above?
A.7.4. You can call bug_email.pl directly from your aliases file, with an entry like this:
A.7.6. 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!) -
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.
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 "sendmailnow".
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 "sanity check" utility + (./sanitycheck.cgi in the + Bugzilla_home directory) from your web browser to see! If + it finishes without errors, you're + probably 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.
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 2.14 if you are + using the "shadow database" feature, and your + shadow database is out of sync. Try running + syncshadowdb + -syncall to make sure your shadow + database is in synch with your primary database.
Microsoft has some advice on this matter, as well:
A.11.1. Try this link to view current bugs or requests for enhancement for Bugzilla.
You can view bugs marked for 2.14 release +> You can view bugs marked for 2.16 release here. - This list includes bugs for the 2.14 release that have already + This list includes bugs for the 2.16 release that have already been fixed and checked into CVS. Please consult the
Enter a bug into bugzilla.mozilla.org for the "Webtools" product, - "Bugzilla" component. +> Enter a bug into bugzilla.mozilla.org for the "Bugzilla" + product.
- Prev