Menu
▾
▴
phpbt-dev — Developer's mailing list and cvs commits
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(34) |
Aug
(215) |
Sep
(180) |
Oct
(135) |
Nov
(105) |
Dec
(81) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(76) |
Feb
(22) |
Mar
(154) |
Apr
(149) |
May
(128) |
Jun
(94) |
Jul
(14) |
Aug
(24) |
Sep
(77) |
Oct
(52) |
Nov
(22) |
Dec
(6) |
| 2003 |
Jan
(4) |
Feb
(10) |
Mar
(6) |
Apr
(29) |
May
(10) |
Jun
(37) |
Jul
(39) |
Aug
(13) |
Sep
(23) |
Oct
(3) |
Nov
(7) |
Dec
(2) |
| 2004 |
Jan
|
Feb
(10) |
Mar
(4) |
Apr
|
May
(35) |
Jun
(4) |
Jul
(17) |
Aug
(6) |
Sep
(14) |
Oct
(18) |
Nov
(2) |
Dec
(14) |
| 2005 |
Jan
(9) |
Feb
(30) |
Mar
(6) |
Apr
|
May
(38) |
Jun
(23) |
Jul
(21) |
Aug
(76) |
Sep
(50) |
Oct
(51) |
Nov
(13) |
Dec
|
|
From: Benjamin C. <bc...@us...> - 2002-04-08 17:05:53
|
Update of /cvsroot/phpbt/phpbt
In directory usw-pr-cvs1:/tmp/cvs-serv28684
Modified Files:
include.php
Log Message:
Show a nice error message if smarty is not available
Index: include.php
===================================================================
RCS file: /cvsroot/phpbt/phpbt/include.php,v
retrieving revision 1.109
retrieving revision 1.110
diff -u -r1.109 -r1.110
--- include.php 8 Apr 2002 15:19:33 -0000 1.109
+++ include.php 8 Apr 2002 17:04:12 -0000 1.110
@@ -95,9 +95,13 @@
$default_db_fields = array('bug_id', 'title', 'reporter', 'owner',
'severity_name', 'priority', 'status_name', 'resolution_name');
-require(SMARTY_PATH . 'Smarty.class.php'); // Template class
// Template class
+if (!@include(SMARTY_PATH . 'Smarty.class.php')) {
+ include('templates/default/base/smartymissing.html');
+ exit;
+}
+
class extSmarty extends Smarty {
function fetch($_smarty_tpl_file, $_smarty_cache_id = null, $_smarty_compile_id = null, $_smarty_display = false) {
|
|
From: Benjamin C. <bc...@us...> - 2002-04-08 16:44:45
|
Update of /cvsroot/phpbt/phpbt In directory usw-pr-cvs1:/tmp/cvs-serv20273 Modified Files: CHANGELOG Log Message: Index: CHANGELOG =================================================================== RCS file: /cvsroot/phpbt/phpbt/CHANGELOG,v retrieving revision 1.52 retrieving revision 1.53 diff -u -r1.52 -r1.53 --- CHANGELOG 4 Apr 2002 13:59:38 -0000 1.52 +++ CHANGELOG 8 Apr 2002 12:54:54 -0000 1.53 @@ -14,6 +14,7 @@ : Fixed a bug with being able to go directly to a bug that should not be available because of project group restrictions. : Added the ability to delete components and versions not referenced by bugs. +: Made compatible with JpGraph 1.6.1 : Fixed other minor bugs. -- 0.7.2 -- 14 Mar 2002 |
|
From: Benjamin C. <bc...@us...> - 2002-04-08 16:43:46
|
Update of /cvsroot/phpbt/phpbt
In directory usw-pr-cvs1:/tmp/cvs-serv14822
Modified Files:
query.php
Log Message:
Initialize the query session variable _before_ assigning to it
Index: query.php
===================================================================
RCS file: /cvsroot/phpbt/phpbt/query.php,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -r1.68 -r1.69
--- query.php 8 Apr 2002 15:05:51 -0000 1.68
+++ query.php 8 Apr 2002 16:30:44 -0000 1.69
@@ -232,16 +232,16 @@
$sort = 'asc';
}
}
+ if (!session_is_registered('queryinfo')) {
+ session_register('queryinfo');
+ $HTTP_SESSION_VARS['queryinfo'] = array();
+ }
+
$HTTP_SESSION_VARS['queryinfo']['order'] = $order;
$HTTP_SESSION_VARS['queryinfo']['sort'] = $sort;
if (empty($HTTP_SESSION_VARS['queryinfo']['query']) or isset($op)) {
$HTTP_SESSION_VARS['queryinfo']['query'] = build_query($assignedto, $reportedby, $open);
- }
-
- if (!session_is_registered('queryinfo')) {
- session_register('queryinfo');
- $HTTP_SESSION_VARS['queryinfo'] = array();
}
$nr = $db->getOne($QUERY['query-list-bugs-count'].
|
|
From: Benjamin C. <bc...@us...> - 2002-04-08 16:39:46
|
Update of /cvsroot/phpbt/phpbt/docs/sgml In directory usw-pr-cvs1:/tmp/cvs-serv5694/sgml Modified Files: bugdetail.sgml bugsearch.sgml primer.sgml Log Message: Updated for 0.8.0 Index: bugdetail.sgml =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/sgml/bugdetail.sgml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- bugdetail.sgml 17 Oct 2001 13:44:10 -0000 1.1 +++ bugdetail.sgml 8 Apr 2002 15:05:11 -0000 1.2 @@ -8,9 +8,6 @@ <screeninfo>Bug Detail</screeninfo> <mediaobject> <imageobject> -<imagedata fileref="images/shots/user/bugdetail.png" format="PNG"> -</imageobject> -<imageobject> <imagedata fileref="images/shots/user/bugdetail.jpg" format="JPG"> </imageobject> <imageobject> @@ -26,9 +23,9 @@ </screenshot> <para>When changes are made to a bug, an email is sent to the person who reported it and to the person to whom the bug is assigned. However, email is not sent to the person who is making the changes to the bug. So, if a bug has been submitted and assigned to a developer, and then the developer adds comments to the bug, then those comments will be emailed to the reporter but not to the developer. Additional people can be added to receive these change emails by adding them to the CC list. To remove people from the CC list, simply select the people to be removed and submit the form.</para> - +<!-- <para>The set of radio buttons beneath the <guilabel>Update Bug Status</guilabel> label changes depending on the status of the bug. The bug in the screen shot is one that has been newly submitted, so it is unassigned at the moment. If a developer looking at this bug wanted to take ownership, she would click <guilabel>Accept bug</guilabel> and then submit the form. If a bug is resolved as a duplicate of another bug (e.g, bug #77), it will be closed and a comment will be added to this bug and to bug #77 noting that this bug is a duplicate of that one. If there is a developer assigned to be the owner of this component (in this case, "name test"), then the bug can be assigned to that individual by clicking the last radio button.</para> - +--> <para>Files can be added to a bug as attachments by clicking on the <guilabel role="hyperlink">Create Attachment</guilabel> link. This will bring up another form where you can supply a short description and browse for the file to be uploaded. Attachments can be viewed (and can be deleted by administrators) from the attachment list.</para> <para>Adding comments to a bug allows you to provide more detail about what caused the bug or what the expected behavior was, but also allow the developer and the user to communicate about a bug while keeping a history of those notes. Comments that are added to a bug will be emailed as described previously. HTML tags will be stripped from the comments, but there are two special character sequences that can be used to create links when the comments are displayed:</para> Index: bugsearch.sgml =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/sgml/bugsearch.sgml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- bugsearch.sgml 26 Mar 2002 17:27:59 -0000 1.2 +++ bugsearch.sgml 8 Apr 2002 15:05:11 -0000 1.3 @@ -2,14 +2,11 @@ <sect1 id="bugsearch"> <title>Searching the Bug Database</title> -<para>The query page presents a wide array of options for finding a specific set of bugs, and thus can be a little overwhelming at first sight. By submitting the default form, without selecting any options, a list of all the bugs in the database will be returned. Every option selected will filter out more bugs as you get more specific in your search.</para> +<para>There are two versions of the bug query page. The default version is the simple form, which allows you to restrict your search by project and bug status. The advanced query page presents a wide array of options for finding a specific set of bugs, and thus can be a little overwhelming at first sight. By submitting the default form, without selecting any options, a list of all the bugs in the database will be returned. Every option selected will filter out more bugs as you get more specific in your search.</para> <screenshot> <screeninfo>Bug Search</screeninfo> <mediaobject> -<imageobject> -<imagedata fileref="images/shots/user/query.png" format="PNG"> -</imageobject> <imageobject> <imagedata fileref="images/shots/user/query.jpg" format="JPG"> </imageobject> Index: primer.sgml =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/sgml/primer.sgml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- primer.sgml 17 Oct 2001 04:02:28 -0000 1.6 +++ primer.sgml 8 Apr 2002 15:05:11 -0000 1.7 @@ -5,22 +5,19 @@ <sect2 id="createaccount"> <title>Creating an account</title> -<para>You can create a new account by following the link labeled <emphasis role="bold">Open a new account</emphasis>. To create a new account you will need to enter at least a valid email address (so that your password can be mailed to you). Providing your name is optional, but if you submit it then your name will appear with bugs you submit and comments you make. If the system has been configured to use a login separate from the email address, you will also be prompted for a login. If you have chosen an email address (or login) that is already in use, you will be prompted to choose a different one. After completing this form, your password will be mailed to you. Once you have received your password you can then login with your email (or login) and password to be able to submit bugs.</para> +<para>You can create a new account by following the link labeled <emphasis role="bold">Create a new account</emphasis>. To create a new account you will need to enter at least a valid email address (so that your password can be mailed to you). Providing your name is optional, but if you submit it then your name will appear with bugs you submit and comments you make. If the system has been configured to use a login separate from the email address, you will also be prompted for a login. If you have chosen an email address (or login) that is already in use, you will be prompted to choose a different one. After completing this form, your password will be mailed to you. Once you have received your password you can then login with your email (or login) and password to be able to submit bugs.</para> </sect2> <sect2 id="enterbug"> <title>Entering a bug</title> -<para>Once you have logged in to the system you can follow the <emphasis role="bold">Enter Bug</emphasis> link from the top navigation bar to create a new bug. If there is more than one project for which you can submit a bug, you will be prompted to choose one.</para> +<para>Once you have logged in to the system you can follow the <emphasis role="bold">Add a New Bug</emphasis> link from the top navigation bar to create a new bug. If there is more than one project for which you can submit a bug, you will be prompted to choose one.</para> <screenshot> <screeninfo>Project selection</screeninfo> <mediaobject> <imageobject> -<imagedata fileref="images/shots/user/enterbug-chooseproject.png" format="PNG"> -</imageobject> -<imageobject> <imagedata fileref="images/shots/user/enterbug-chooseproject.jpg" format="JPG"> </imageobject> <imageobject> @@ -40,9 +37,6 @@ <screenshot> <screeninfo>Adding a bug</screeninfo> <mediaobject> -<imageobject> -<imagedata fileref="images/shots/user/enterbug-detail.png" format="PNG"> -</imageobject> <imageobject> <imagedata fileref="images/shots/user/enterbug-detail.jpg" format="JPG"> </imageobject> |
|
From: Benjamin C. <bc...@us...> - 2002-04-08 16:38:40
|
Update of /cvsroot/phpbt/phpbt/docs/html/images/shots/user In directory usw-pr-cvs1:/tmp/cvs-serv2964/shots/user Added Files: bugdetail.jpg enterbug-chooseproject.jpg enterbug-detail.jpg query.jpg Removed Files: bugdetail.png buglist.png enterbug-chooseproject.png enterbug-detail.png query.png Log Message: Updating screen shots for 0.8.0 --- bugdetail.png DELETED --- --- buglist.png DELETED --- --- enterbug-chooseproject.png DELETED --- --- enterbug-detail.png DELETED --- --- query.png DELETED --- |
|
From: Benjamin C. <bc...@us...> - 2002-04-08 16:38:14
|
Update of /cvsroot/phpbt/phpbt
In directory usw-pr-cvs1:/tmp/cvs-serv6012
Modified Files:
query.php
Log Message:
Take a user back to the advanced query page after deleting a saved query
Index: query.php
===================================================================
RCS file: /cvsroot/phpbt/phpbt/query.php,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -r1.67 -r1.68
--- query.php 3 Apr 2002 01:00:52 -0000 1.67
+++ query.php 8 Apr 2002 15:05:51 -0000 1.68
@@ -29,7 +29,7 @@
$db->query("delete from ".TBL_SAVED_QUERY." where user_id = $u
and saved_query_id = $queryid");
- header("Location: $me?op=query");
+ header("Location: $me?op=query&form=advanced");
}
function show_query() {
|
|
From: Benjamin C. <bc...@us...> - 2002-04-08 15:43:16
|
Update of /cvsroot/phpbt/phpbt
In directory usw-pr-cvs1:/tmp/cvs-serv20108
Modified Files:
index.php
Log Message:
Now compatible with jpgraph 1.6.1
Index: index.php
===================================================================
RCS file: /cvsroot/phpbt/phpbt/index.php,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- index.php 3 Apr 2002 01:00:52 -0000 1.29
+++ index.php 8 Apr 2002 12:54:25 -0000 1.30
@@ -71,10 +71,11 @@
$graph->legend->Pos(0.03, 0.5, 'right', 'center');
// Create
$p1 = new PiePlot($data);
+ $p1->value->SetFormat("%d%%");
+ $p1->value->Show();
$p1->SetLegends($legend);
$p1->SetCSIMTargets($targ,$alts);
$p1->SetCenter(0.25);
- $p1->SetPrecision(0);
$graph->Add($p1);
$graph->Stroke('jpgimages/'.GenImgName());
|
|
From: Benjamin C. <bc...@us...> - 2002-04-08 15:38:40
|
Update of /cvsroot/phpbt/phpbt/templates/default/admin In directory usw-pr-cvs1:/tmp/cvs-serv10850/admin Modified Files: header.html Log Message: Oops Index: header.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/templates/default/admin/header.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- header.html 3 Apr 2002 19:04:04 -0000 1.3 +++ header.html 8 Apr 2002 12:24:36 -0000 1.4 @@ -48,10 +48,8 @@ <div class="navbox" onMouseOver="this.className='navboxselected'" onMouseOut="this.className='navbox'" onClick="document.location.href='../docs/html/userguide.html'"> <a href="../docs/html/userguide.html" class="sidenavlink">Read Documentation</a> </div> - <!-- BEGIN adminnavblock --> <div class="navbox" onMouseOver="this.className='navboxselected'" onMouseOut="this.className='navbox'" onClick="document.location.href='../index.php'"> <a href="../index.php" class="sidenavlink">User Tools</a> </div> - <!-- END adminnavblock --> </td> <td class="maincontent"> |
Update of /cvsroot/phpbt/phpbt/docs/html In directory usw-pr-cvs1:/tmp/cvs-serv5694/html Modified Files: adminguide.html bugdetail.html bugsearch.html configuration.html devguide.html devstandards.html schema.html userguide.html Log Message: Updated for 0.8.0 Index: adminguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/adminguide.html,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- adminguide.html 5 Apr 2002 19:06:07 -0000 1.14 +++ adminguide.html 8 Apr 2002 15:05:09 -0000 1.15 @@ -102,7 +102,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN119"><P +NAME="AEN108"><P >One of the main design goals of phpBugTracker is to make installation and administration easy. In fact, the difficulty of installing bugzilla was a key motivator for phpBugTracker's existence.</P ></DIV ></BLOCKQUOTE Index: bugdetail.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/bugdetail.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- bugdetail.html 28 Feb 2002 18:55:43 -0000 1.3 +++ bugdetail.html 8 Apr 2002 15:05:09 -0000 1.4 @@ -83,7 +83,7 @@ CLASS="MEDIAOBJECT" ><P ><IMG -SRC="images/shots/user/bugdetail.png"><DIV +SRC="images/shots/user/bugdetail.jpg"><DIV CLASS="CAPTION" ><P >Editing a bug.</P @@ -92,14 +92,6 @@ ></DIV ><P >When changes are made to a bug, an email is sent to the person who reported it and to the person to whom the bug is assigned. However, email is not sent to the person who is making the changes to the bug. So, if a bug has been submitted and assigned to a developer, and then the developer adds comments to the bug, then those comments will be emailed to the reporter but not to the developer. Additional people can be added to receive these change emails by adding them to the CC list. To remove people from the CC list, simply select the people to be removed and submit the form.</P -><P ->The set of radio buttons beneath the <SPAN -CLASS="GUILABEL" ->Update Bug Status</SPAN -> label changes depending on the status of the bug. The bug in the screen shot is one that has been newly submitted, so it is unassigned at the moment. If a developer looking at this bug wanted to take ownership, she would click <SPAN -CLASS="GUILABEL" ->Accept bug</SPAN -> and then submit the form. If a bug is resolved as a duplicate of another bug (e.g, bug #77), it will be closed and a comment will be added to this bug and to bug #77 noting that this bug is a duplicate of that one. If there is a developer assigned to be the owner of this component (in this case, "name test"), then the bug can be assigned to that individual by clicking the last radio button.</P ><P >Files can be added to a bug as attachments by clicking on the <SPAN CLASS="GUILABEL" Index: bugsearch.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/bugsearch.html,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- bugsearch.html 5 Apr 2002 19:06:08 -0000 1.5 +++ bugsearch.html 8 Apr 2002 15:05:10 -0000 1.6 @@ -78,12 +78,12 @@ ><A NAME="BUGSEARCH">1.2. Searching the Bug Database</H1 ><P ->The query page presents a wide array of options for finding a specific set of bugs, and thus can be a little overwhelming at first sight. By submitting the default form, without selecting any options, a list of all the bugs in the database will be returned. Every option selected will filter out more bugs as you get more specific in your search.</P +>There are two versions of the bug query page. The default version is the simple form, which allows you to restrict your search by project and bug status. The advanced query page presents a wide array of options for finding a specific set of bugs, and thus can be a little overwhelming at first sight. By submitting the default form, without selecting any options, a list of all the bugs in the database will be returned. Every option selected will filter out more bugs as you get more specific in your search.</P ><DIV CLASS="MEDIAOBJECT" ><P ><IMG -SRC="images/shots/user/query.png"><DIV +SRC="images/shots/user/query.jpg"><DIV CLASS="CAPTION" ><P >Searching for bugs.</P Index: configuration.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/configuration.html,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- configuration.html 5 Apr 2002 19:06:08 -0000 1.14 +++ configuration.html 8 Apr 2002 15:05:10 -0000 1.15 @@ -82,7 +82,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN150"><P +NAME="AEN139"><P >Most of the options listed here can be configured via the Configuration page of the admin tools. The <TT CLASS="VARNAME" >DB_</TT Index: devguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/devguide.html,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- devguide.html 5 Apr 2002 19:06:08 -0000 1.20 +++ devguide.html 8 Apr 2002 15:05:10 -0000 1.21 @@ -116,7 +116,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN297"><P +NAME="AEN286"><P >Adding on to or extending phpBugTracker should be easy for those with a knowledge of PHP and SQL. New developers are always welcome to join the project at <A HREF="http://www.sourceforge.net/projects/phpbt/" TARGET="_top" Index: devstandards.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/devstandards.html,v retrieving revision 1.21 retrieving revision 1.22 diff -u -r1.21 -r1.22 --- devstandards.html 5 Apr 2002 19:06:08 -0000 1.21 +++ devstandards.html 8 Apr 2002 15:05:10 -0000 1.22 @@ -82,7 +82,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN377"><P +NAME="AEN366"><P > This section details the coding and process standards to be followed by the developers working on phpBugTracker. </P Index: schema.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/schema.html,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- schema.html 5 Apr 2002 19:06:08 -0000 1.6 +++ schema.html 8 Apr 2002 15:05:10 -0000 1.7 @@ -73,7 +73,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN435"><P +NAME="AEN424"><P ><B >Table 3-1. Schema for table attachment</B ></P @@ -251,7 +251,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN485"><P +NAME="AEN474"><P ><B >Table 3-2. Schema for table auth_group</B ></P @@ -413,7 +413,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN531"><P +NAME="AEN520"><P ><B >Table 3-3. Schema for table auth_perm</B ></P @@ -560,7 +560,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN573"><P +NAME="AEN562"><P ><B >Table 3-4. Schema for table auth_user</B ></P @@ -810,7 +810,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN643"><P +NAME="AEN632"><P ><B >Table 3-5. Schema for table bug</B ></P @@ -1195,7 +1195,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN751"><P +NAME="AEN740"><P ><B >Table 3-6. Schema for table bug_cc</B ></P @@ -1301,7 +1301,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN781"><P +NAME="AEN770"><P ><B >Table 3-7. Schema for table bug_dependency</B ></P @@ -1371,7 +1371,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN801"><P +NAME="AEN790"><P ><B >Table 3-8. Schema for table bug_group</B ></P @@ -1443,7 +1443,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN822"><P +NAME="AEN811"><P ><B >Table 3-9. Schema for table bug_vote</B ></P @@ -1531,7 +1531,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN847"><P +NAME="AEN836"><P ><B >Table 3-10. Schema for table bug_history</B ></P @@ -1673,7 +1673,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN887"><P +NAME="AEN876"><P ><B >Table 3-11. Schema for table comment</B ></P @@ -1797,7 +1797,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN922"><P +NAME="AEN911"><P ><B >Table 3-12. Schema for table component</B ></P @@ -2014,7 +2014,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN983"><P +NAME="AEN972"><P ><B >Table 3-13. Schema for table configuration</B ></P @@ -2122,7 +2122,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1014"><P +NAME="AEN1003"><P ><B >Table 3-14. Schema for table group_perm</B ></P @@ -2192,7 +2192,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1034"><P +NAME="AEN1023"><P ><B >Table 3-15. Schema for table os</B ></P @@ -2298,7 +2298,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1064"><P +NAME="AEN1053"><P ><B >Table 3-16. Schema for table project</B ></P @@ -2476,7 +2476,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1114"><P +NAME="AEN1103"><P ><B >Table 3-17. Schema for table project_group</B ></P @@ -2582,7 +2582,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1144"><P +NAME="AEN1133"><P ><B >Table 3-18. Schema for table resolution</B ></P @@ -2688,7 +2688,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1174"><P +NAME="AEN1163"><P ><B >Table 3-19. Schema for table saved_query</B ></P @@ -2799,7 +2799,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1206"><P +NAME="AEN1195"><P ><B >Table 3-20. Schema for table severity</B ></P @@ -2926,7 +2926,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1242"><P +NAME="AEN1231"><P ><B >Table 3-21. Schema for table status</B ></P @@ -3032,7 +3032,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1272"><P +NAME="AEN1261"><P ><B >Table 3-22. Schema for table user_group</B ></P @@ -3138,7 +3138,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1302"><P +NAME="AEN1291"><P ><B >Table 3-23. Schema for table user_perm</B ></P @@ -3208,7 +3208,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1322"><P +NAME="AEN1311"><P ><B >Table 3-24. Schema for table user_pref</B ></P @@ -3278,7 +3278,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1342"><P +NAME="AEN1331"><P ><B >Table 3-25. Schema for table version</B ></P Index: userguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/userguide.html,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- userguide.html 28 Feb 2002 18:55:44 -0000 1.11 +++ userguide.html 8 Apr 2002 15:05:10 -0000 1.12 @@ -137,7 +137,7 @@ CLASS="bold" ><B CLASS="EMPHASIS" ->Open a new account</B +>Create a new account</B ></SPAN >. To create a new account you will need to enter at least a valid email address (so that your password can be mailed to you). Providing your name is optional, but if you submit it then your name will appear with bugs you submit and comments you make. If the system has been configured to use a login separate from the email address, you will also be prompted for a login. If you have chosen an email address (or login) that is already in use, you will be prompted to choose a different one. After completing this form, your password will be mailed to you. Once you have received your password you can then login with your email (or login) and password to be able to submit bugs.</P ></DIV @@ -152,14 +152,14 @@ CLASS="bold" ><B CLASS="EMPHASIS" ->Enter Bug</B +>Add a New Bug</B ></SPAN > link from the top navigation bar to create a new bug. If there is more than one project for which you can submit a bug, you will be prompted to choose one.</P ><DIV CLASS="MEDIAOBJECT" ><P ><IMG -SRC="images/shots/user/enterbug-chooseproject.png"><DIV +SRC="images/shots/user/enterbug-chooseproject.jpg"><DIV CLASS="CAPTION" ><P >Selecting a project for a bug report.</P @@ -208,7 +208,7 @@ CLASS="MEDIAOBJECT" ><P ><IMG -SRC="images/shots/user/enterbug-detail.png"><DIV +SRC="images/shots/user/enterbug-detail.jpg"><DIV CLASS="CAPTION" ><P >Entering a bug report.</P |
|
From: Benjamin C. <bc...@us...> - 2002-04-08 15:19:40
|
Update of /cvsroot/phpbt/phpbt
In directory usw-pr-cvs1:/tmp/cvs-serv13106
Modified Files:
config-dist.php config.php include.php install.php
Log Message:
Make it easier to get smarty included
Index: config-dist.php
===================================================================
RCS file: /cvsroot/phpbt/phpbt/config-dist.php,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- config-dist.php 3 Apr 2002 01:01:38 -0000 1.12
+++ config-dist.php 8 Apr 2002 15:19:33 -0000 1.13
@@ -28,6 +28,9 @@
define ('DB_USER', '{db_user}'); // username for database connection
define ('DB_PASSWORD', '{db_pass}'); // password for database connection
+// Smarty templates location (leave blank if Smarty is in include path)
+define ('SMARTY_PATH', '{smarty_path}');
+
// Database Table Config
// you can change either the prefix of the table names or each table name individually
define ('TBL_PREFIX', '{tbl_prefix}'); // the prefix for all tables, leave empty to use the old style
Index: config.php
===================================================================
RCS file: /cvsroot/phpbt/phpbt/config.php,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- config.php 29 Mar 2002 18:25:37 -0000 1.27
+++ config.php 8 Apr 2002 15:19:33 -0000 1.28
@@ -31,6 +31,9 @@
define ('DB_USER', 'root');
define ('DB_PASSWORD', '');
+// Smarty templates location (leave blank if Smarty is in include path)
+define ('SMARTY_PATH', '');
+
// Database Table Config
// you can change either the prefix of the table names or each table name individually
define ('TBL_PREFIX', ''); // the prefix for all tables, leave empty to use the old style
Index: include.php
===================================================================
RCS file: /cvsroot/phpbt/phpbt/include.php,v
retrieving revision 1.108
retrieving revision 1.109
diff -u -r1.108 -r1.109
--- include.php 3 Apr 2002 18:54:08 -0000 1.108
+++ include.php 8 Apr 2002 15:19:33 -0000 1.109
@@ -95,7 +95,7 @@
$default_db_fields = array('bug_id', 'title', 'reporter', 'owner',
'severity_name', 'priority', 'status_name', 'resolution_name');
-require('Smarty.class.php'); // Template class
+require(SMARTY_PATH . 'Smarty.class.php'); // Template class
// Template class
class extSmarty extends Smarty {
Index: install.php
===================================================================
RCS file: /cvsroot/phpbt/phpbt/install.php,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- install.php 4 Apr 2002 23:30:42 -0000 1.22
+++ install.php 8 Apr 2002 15:19:33 -0000 1.23
@@ -26,9 +26,9 @@
define ('INSTALL_PATH', dirname(__FILE__));
// Location of smarty templates class
- define ('SMARTY_PATH','');
- // Example if smarty is installed within the phpBugTracker tree.
- //define ('SMARTY_PATH','./inc/smarty/');
+define ('SMARTY_PATH','');
+// Example if smarty is installed within the phpBugTracker tree.
+//define ('SMARTY_PATH','./inc/smarty/');
if (!@include(SMARTY_PATH . 'Smarty.class.php')) { // Template class
die('<br><br>
@@ -147,6 +147,10 @@
$patterns[] = '{'.$key.'}';
$replacements[] = $val;
}
+ // Smarty
+ $patterns[] = '{smarty_path}';
+ $replacements[] = SMARTY_PATH;
+
$contents = join('', file('config-dist.php'));
return str_replace($patterns, $replacements, $contents);
|
|
From: Ben C. <php...@be...> - 2002-04-08 12:35:38
|
I removed a few people who were listed as developers on the project in an effort to clean up the list a bit. I don't think I removed anyone who's active here on the list, but if I removed you by accident please let me know and I'll add you back. |
|
From: Ben C. <php...@be...> - 2002-04-08 11:47:05
|
Oh, and there was another vote for wrap instead of header/footer on the
sourceforge forum so let's say 1 for header/footer and 2 for wrap.
On Sun, Apr 07, 2002 at 09:09:56PM +0100, John Wilkins wrote:
> Hi all,
>
> I've been testing out the latest CVS code including the new smarty
> templates. They certainly make the php code files a lot simpler which
> is, I think, Ben's main aim of the change.
>
> A couple of weeks ago, I started to build a new template for my install
> at work. With the pre-Smarty code, this was straight forward: Design
> a new wrap.html in any html wysiwyg editor than put in the correct
> tags for {content} etc,. I didn't make any changed to the "content"
> files (user.html, newaccout.html) etc,,.
>
> Having looked at the new templates system, I was wondering if it would
> be possible to still use an overall design template file (ie wrap.html)
> with the new Smarty "content" files.
>
> I think I've found how to do this by making only very small changes
> to whats currently in cvs. The basic approach was to:
> * change the {content} tag in wrap.html to {include file=$content}
> * change the $t->display('index.html') line at the end of index.php
> to $t->display('wrap.html');
> * preceed the $t->display(..) line with
> $t->assign('body','index.html'); (or 'user.html' etc,,)
> * change index.html by removing the header and footer includes but
> leaving all the other smarty code in place;
> * copy back smarty display logic code from header.html and
> footer.html to wrap.html;
>
> The wrap.html basically becomes the overall "layout" template
> file whilst the others provide all the detail & display logic.
> Significantly distinct templates can be generated simply by
> modifying the wrap file, without having to change the others.
>
> Is this worth looking at? It seems to be a "middle way" to get
> the benefits of the old simple templates with the power of the
> Smarty template class. If so, I'll post my modified files here
> somewhere for closer inspection.
>
> _______________________________________________
> phpbt-dev mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpbt-dev
|
|
From: Ben C. <php...@be...> - 2002-04-08 11:45:50
|
This would certainly work, and I did consider it. The main reason I
didn't do it this way it because it leaves a little more of the display
stuff in the PHP. The main thing is the page titles. I know it's not a
really big deal, but it is nice to be able to do
$t->display('index.html'); rather than $t->assign(array('content' =>
'index.html', page_title => 'Home')); $t->display('wrap.html'); I know
this is getting down to the nit-picking level, but that's what I was
thinking. Now, I don't really have that big of a problem going that
route if others think it would be nicer to keep the wrap.html instead of
header.html and footer.html. It's not that big of a deal, really.
So let's say that there's one vote for header/footer and one vote for
wrap. Any other votes? :)
On Sun, Apr 07, 2002 at 09:09:56PM +0100, John Wilkins wrote:
> Hi all,
>
> I've been testing out the latest CVS code including the new smarty
> templates. They certainly make the php code files a lot simpler which
> is, I think, Ben's main aim of the change.
>
> A couple of weeks ago, I started to build a new template for my install
> at work. With the pre-Smarty code, this was straight forward: Design
> a new wrap.html in any html wysiwyg editor than put in the correct
> tags for {content} etc,. I didn't make any changed to the "content"
> files (user.html, newaccout.html) etc,,.
>
> Having looked at the new templates system, I was wondering if it would
> be possible to still use an overall design template file (ie wrap.html)
> with the new Smarty "content" files.
>
> I think I've found how to do this by making only very small changes
> to whats currently in cvs. The basic approach was to:
> * change the {content} tag in wrap.html to {include file=$content}
> * change the $t->display('index.html') line at the end of index.php
> to $t->display('wrap.html');
> * preceed the $t->display(..) line with
> $t->assign('body','index.html'); (or 'user.html' etc,,)
> * change index.html by removing the header and footer includes but
> leaving all the other smarty code in place;
> * copy back smarty display logic code from header.html and
> footer.html to wrap.html;
>
> The wrap.html basically becomes the overall "layout" template
> file whilst the others provide all the detail & display logic.
> Significantly distinct templates can be generated simply by
> modifying the wrap file, without having to change the others.
>
> Is this worth looking at? It seems to be a "middle way" to get
> the benefits of the old simple templates with the power of the
> Smarty template class. If so, I'll post my modified files here
> somewhere for closer inspection.
>
> _______________________________________________
> phpbt-dev mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpbt-dev
|
|
From: John W. <joh...@wi...> - 2002-04-07 20:08:22
|
Hi all,
I've been testing out the latest CVS code including the new smarty
templates. They certainly make the php code files a lot simpler which
is, I think, Ben's main aim of the change.
A couple of weeks ago, I started to build a new template for my install
at work. With the pre-Smarty code, this was straight forward: Design
a new wrap.html in any html wysiwyg editor than put in the correct
tags for {content} etc,. I didn't make any changed to the "content"
files (user.html, newaccout.html) etc,,.
Having looked at the new templates system, I was wondering if it would
be possible to still use an overall design template file (ie wrap.html)
with the new Smarty "content" files.
I think I've found how to do this by making only very small changes
to whats currently in cvs. The basic approach was to:
* change the {content} tag in wrap.html to {include file=$content}
* change the $t->display('index.html') line at the end of index.php
to $t->display('wrap.html');
* preceed the $t->display(..) line with
$t->assign('body','index.html'); (or 'user.html' etc,,)
* change index.html by removing the header and footer includes but
leaving all the other smarty code in place;
* copy back smarty display logic code from header.html and
footer.html to wrap.html;
The wrap.html basically becomes the overall "layout" template
file whilst the others provide all the detail & display logic.
Significantly distinct templates can be generated simply by
modifying the wrap file, without having to change the others.
Is this worth looking at? It seems to be a "middle way" to get
the benefits of the old simple templates with the power of the
Smarty template class. If so, I'll post my modified files here
somewhere for closer inspection.
|
|
From: Benjamin C. <bc...@us...> - 2002-04-07 08:33:56
|
Update of /cvsroot/phpbt/phpbt/templates/default
In directory usw-pr-cvs1:/tmp/cvs-serv21843/templates/default
Modified Files:
bugdisplay.html
Log Message:
Changed resolution and status changes to select boxes. How do we (if we should) bring back the "dupe of" assignment when closing as a duplicate. Also, how do we know when a bug is "closed" if the Closed status gets translated?
Index: bugdisplay.html
===================================================================
RCS file: /cvsroot/phpbt/phpbt/templates/default/bugdisplay.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- bugdisplay.html 3 Apr 2002 00:57:51 -0000 1.22
+++ bugdisplay.html 6 Apr 2002 23:47:29 -0000 1.23
@@ -26,11 +26,11 @@
</script>
<form action="bug.php" method="post">
<input type="hidden" name="op" value="update">
-<input type="hidden" name="bug_id" value="{$bug_id}">
+<input type="hidden" name="bugid" value="{$bug_id}">
<input type="hidden" name="projectid" value="{$project_id}">
-<input type="hidden" name="last_modified_date" value="{$lastmodifieddate}">
+<input type="hidden" name="last_modified_date" value="{$last_modified_date}">
<input type="hidden" name="pos" value="{$smarty.request.pos}">
-<table border="0" width="640">
+<table border="0" width="100%">
<tr>
<td>Bug <b>#{$bug_id}</b> - Return to <a href="query.php">bug list</a></td>
<td align="right">
@@ -45,15 +45,16 @@
{/if}
</td>
</tr>
+ {if $error.status}
+ <tr><td class="error">{$error.status}</td></tr>
+ {/if}
</table>
-<table border="0" width="640">
+<table border="0" width="100%" cellspacing="0" cellpadding="2">
<tr>
- <td width="420" colspan="4">
- Reporter: <b>{$reporter|maskemail}</b>
- </td>
- <td width="210" colspan="2">
- Created: <b>{$created_date|date:DATE_FORMAT}</b>
- </td>
+ <td>Reporter:</td>
+ <td><b>{$reporter|maskemail}</b></td>
+ <td>Created:</td>
+ <td><b>{$created_date|date:DATE_FORMAT}</b></td>
</tr>
<tr>
<td>
@@ -63,30 +64,32 @@
<select name="project_id" onChange="updateMenus(this.form)">{build_select box=project selected=$project_id}</select>
</td>
<td>
- Component:
+ Priority:
</td>
<td>
- <select name="component_id">{build_select box=component selected=$component_id project=$project_id}</select>
+ <select name="priority">{build_select box=priority selected=$priority}</select>
</td>
+ </tr>
+ <tr>
<td>
- Version:
+ Component:
</td>
<td>
- <select name="version_id">{build_select box=version selected=$version_id project=$project_id}</select>
+ <select name="component_id">{build_select box=component selected=$component_id project=$project_id}</select>
</td>
- </tr>
- <tr>
<td>
Severity:
</td>
<td>
<select name="severity_id">{build_select box=severity selected=$severity_id}</select>
</td>
+ </tr>
+ <tr>
<td>
- Priority:
+ Version:
</td>
<td>
- <select name="priority">{build_select box=priority selected=$priority}</select>
+ <select name="version_id">{build_select box=version selected=$version_id project=$project_id}</select>
</td>
<td>
OS:
@@ -96,95 +99,25 @@
</td>
</tr>
<tr>
- <td colspan="6">
- <hr size="1">
- </td>
- </tr>
-</table>
-<table border="0" cellpadding="2" cellspacing="0" width="640">
- <tr>
- <td>Assigned To:</td>
- <td><b>{$owner|maskemail}</td>
- <td colspan="2">
-
- </td>
- </tr>
- <tr>
- <td>Status:</td>
- <td><b>{$status_name}</b></td>
<td>Summary:</td>
<td><input type="text" size="30" maxlength="100" name="title" value="{$title|stripslashes|htmlentities}"></td>
+ <td>Status:</td>
+ <td><select name="status_id">{build_select box=status selected=$status_id}</select></td>
</tr>
<tr>
- <td>Resolution:</td>
- <td><b>{$resolution_name}</b></td>
<td>{if $url}<a href="{$url}">URL</a>{else}URL{/if}:</td>
<td><input type="text" size="30" maxlength="255" name="url" value="{$url}"></td>
+ <td>Resolution:</td>
+ <td><select name="resolution_id"><option value="0">None</option>{build_select box=resolution selected=$resolution_id}</select></td>
</tr>
<tr>
- <td colspan="4">
-
- </td>
- </tr>
- <tr>
- <td valign="top" colspan="2">
- Update Bug Status:
- <br>
- <br>
- {if !empty($error.status)}<div class="error">{$error.status}</div>{/if}
- <input type="radio" name="outcome" value="unchanged" checked>
- Leave as <b>{$status_name} {$resolution_name}</b><br>
- {if in_array($status_name, array('Unconfirmed', 'New', 'Reopened'))}
- <input type="radio" name="outcome" value="assign">
- Accept bug (change status to <b>Assigned</b>)<br>
- {/if}
- {if $status_name == 'Assigned'}
- <input type="radio" name="outcome" value="resolve">
- Resolve bug, changing resolution to <select name="resolution_id">{build_select box=resolution}</select><br>
- <input type="radio" name="outcome" value="dupe">
- Resolve bug, mark it as a duplicate of bug #<input type="text" name="dupenum" size="5"><br>
- <input type="radio" name="outcome" value="reassign">
- Reassign bug to
- <!--
- Uncomment the text box and remove the select box if you want users
- to type in the login for assignment (e.g., to hide developer email addresses)
- <input type="text" name="reassignto">
- -->
- <select name="reassignto"><option value="0">Choose one</option>{build_select box=owner}</select>
- <br>
- <input type="radio" name="outcome" value="reassigntocomponent">
- Reassign bug to owner of selected component<br>
- {/if}
- {if in_array($status_name, array('Resolved', 'Verified', 'Closed'))}
- <input type="radio" name="outcome" value="reopen">
- Reopen bug<br>
- {/if}
- {if $status_name == 'Verified'}
- <input type="radio" name="outcome" value="verify">
- Mark bug as verified<br>
- {/if}
- {if in_array($status_name, array('Resolved', 'Verified'))}
- <input type="radio" name="outcome" value="close">
- Mark bug as closed<br>
- {/if}
- </td>
- <td valign="top" colspan="2">
- Add CC:
- <br>
- <br>
- <input type="text" name="add_cc">
- <br>
- <br>
- Remove selected CCs:
- <br>
- <br>
- <select name="remove_cc[]" size="5" multiple>{build_select box=cclist selected=$bug_id}</select>
- </td>
+ <td>Assigned To:</td>
+ <td><select name="assigned_to"><option value="0">None</option>{build_select box=owner selected=$assigned_to}</select></td>
+ <td>Add CC:</td>
+ <td><input type="text" name="add_cc"></td>
</tr>
-</table>
-<table border="0" cellpadding="2" cellspacing="0" width="640">
<tr>
- <td>
+ <td colspan="2" valign="top">
{if !empty($error.add_dep)}<div class="error">{$error.add_dep}</div>{/if}
Bug Dependencies: {$bug_dependencies}
<br>
@@ -194,7 +127,14 @@
<br>
<br>
</td>
+ <td colspan="2" valign="top">
+ Remove selected CCs:
+ <br>
+ <select name="remove_cc[]" size="5" style="width: 15em" multiple>{build_select box=cclist selected=$bug_id}</select>
+ </td>
</tr>
+</table>
+<table border="0" cellpadding="2" cellspacing="0" width="640">
<tr>
<td valign="top">
Additional Comments:
@@ -272,44 +212,46 @@
</tr>
</table>
</form>
+<div align="center">
{if !empty($error.vote)}<div class="error">{$error.vote}</div>{/if}
<b><a href="{$SCRIPT_NAME}?op=vote&bugid={$bug_id}" onClick="if ({$already_voted}) {literal}{ alert ('{/literal}{$STRING.already_voted}{literal}'); return false; }{/literal}">Vote for this bug</a></b> |
<b><a href="{$SCRIPT_NAME}?op=viewvotes&bugid={$bug_id}">View votes ({$num_votes}) for this bug</a></b> |
<b><a href="{$SCRIPT_NAME}?op=history&bugid={$bug_id}">View bug activity</a></b> |
<b><a href="{$SCRIPT_NAME}?op=print&bugid={$bug_id}">Printable view</a></b>
-
+</div>
<br>
<br>
<table border="0" cellpadding="2" cellspacing="0" width="640">
<tr>
<td>
Comments:
- <hr size="1">
+ </td>
+ </tr>
+ <tr class="alt">
+ <td>
+ Posted by: {$reporter|maskemail}
+ <br>
+ Date: {$created_date|date:TIME_FORMAT} on {$created_date|date:DATE_FORMAT}
</td>
</tr>
<tr>
<td>
- <div align="center">
- <i>----- Posted by {$reporter|maskemail} at {$created_date|date:TIME_FORMAT} on {$created_date|date:DATE_FORMAT} -----</i>
- <br>
- <br>
- </div>
{$description|stripslashes|format_comments|nl2br}
<br>
<br>
- <br>
</td>
</tr>
{section name=comment loop=$comments}
- <tr>
+ <tr class="alt">
<td>
- <div align="center">
- <i>----- Posted by {$comments[comment].rreporter|maskemail} at {$comments[comment].created_date|date:TIME_FORMAT} on {$comments[comment].created_date|date:DATE_FORMAT}-----</i>
- <br>
- <br>
- </div>
- {$comments[comment].rdescription|stripslashes|format_comments|nl2br}
+ Posted by: {$comments[comment].login|maskemail}
<br>
+ Date: {$comments[comment].created_date|date:TIME_FORMAT} on {$comments[comment].created_date|date:DATE_FORMAT}
+ </td>
+ </tr>
+ <tr>
+ <td>
+ {$comments[comment].comment_text|stripslashes|format_comments|nl2br}
<br>
<br>
</td>
|
|
From: Benjamin C. <bc...@us...> - 2002-04-07 08:14:18
|
Update of /cvsroot/phpbt/phpbt
In directory usw-pr-cvs1:/tmp/cvs-serv21843
Modified Files:
bug.php
Log Message:
Changed resolution and status changes to select boxes. How do we (if we should) bring back the "dupe of" assignment when closing as a duplicate. Also, how do we know when a bug is "closed" if the Closed status gets translated?
Index: bug.php
===================================================================
RCS file: /cvsroot/phpbt/phpbt/bug.php,v
retrieving revision 1.94
retrieving revision 1.95
diff -u -r1.94 -r1.95
--- bug.php 4 Apr 2002 13:54:03 -0000 1.94
+++ bug.php 6 Apr 2002 23:47:29 -0000 1.95
@@ -124,8 +124,7 @@
// It's a new bug if the changedfields array is empty and there are no comments
$newbug = (!count($cf) and !$comments);
- $t->set_file('emailout', ($newbug ? 'bugemail-newbug.txt' : 'bugemail.txt'));
- $t->set_block('emailout','commentblock', 'cblock');
+ $template = $newbug ? 'bugemail-newbug.txt' : 'bugemail.txt';
foreach(array('title','url') as $field) {
if (isset($cf[$field])) {
$db->query('insert into '.TBL_BUG_HISTORY
@@ -133,12 +132,12 @@
." values (". join(', ', array($buginfo['bug_id'], $db->quote($field),
$db->quote(stripslashes($buginfo[$field])),
$db->quote(stripslashes($cf[$field])), $u, $now)).")");
- $t->set_var(array(
+ $t->assign(array(
$field => stripslashes($cf[$field]),
$field.'_stat' => '!'
));
} else {
- $t->set_var(array(
+ $t->assign(array(
$field => stripslashes($buginfo[$field]),
$field.'_stat' => ' '
));
@@ -167,12 +166,12 @@
." values (". join(', ', array($buginfo['bug_id'], $db->quote($field),
$db->quote(stripslashes($oldvalue)),
$db->quote(stripslashes($newvalue)), $u, $now)).")");
- $t->set_var(array(
+ $t->assign(array(
$field.'_id' => stripslashes($newvalue),
$field.'_id_stat' => '!'
));
} else {
- $t->set_var(array(
+ $t->assign(array(
$field.'_id' => stripslashes($oldvalue),
$field.'_id_stat' => ' '
));
@@ -197,7 +196,7 @@
." where bug_id = {$buginfo['bug_id']} and c.created_by = u.user_id"
.' order by created_date desc', 0, 2);
$rs->fetchInto($row);
- $t->set_var(array(
+ $t->assign(array(
'newpostedby' => $row['login'],
'newpostedon' => date(TIME_FORMAT, $row['created_date']).' on '.
date(DATE_FORMAT, $row['created_date']),
@@ -210,7 +209,7 @@
.' from '.TBL_BUG.' b, '.TBL_AUTH_USER.' u'
." where b.created_by = u.user_id and bug_id = {$buginfo['bug_id']}",
null, DB_FETCHMODE_ORDERED);
- $t->set_var(array(
+ $t->assign(array(
'oldpostedby' => $by,
'oldpostedon' => date(TIME_FORMAT,$on).' on '.date(DATE_FORMAT,$on),
'oldcomments' => textwrap(format_comments($comments),72)
@@ -224,9 +223,9 @@
'oldcomments' => textwrap(format_comments($row['comment_text']),72)
));
}
- $t->parse('cblock', 'commentblock', true);
+ $t->assign('showcomments', true);
} else {
- $t->set_var('cblock', '');
+ $t->assign('showcomments', false);
}
$maillist = array();
@@ -247,7 +246,7 @@
if (count($maillist)) {
if ($toemail = delimit_list(', ',$maillist)) {
- $t->set_var(array(
+ $t->assign(array(
'bugid' => $buginfo['bug_id'],
'bugurl' => INSTALL_URL."/bug.php?op=show&bugid={$buginfo['bug_id']}",
'priority' => $select['priority'][(!empty($cf['priority']) ? $cf['priority'] : $buginfo['priority'])],
@@ -260,7 +259,7 @@
mail($toemail,"[Bug {$buginfo['bug_id']}] ".($newbug ? 'New' : 'Changed').
' - '.(!empty($cf['title']) ? $cf['title'] : $buginfo['title']),
- $t->parse('main','emailout'),
+ $t->fetch($template),
sprintf("From: %s\nReply-To: %s\nErrors-To: %s\nContent-Type: text/plain; charset=%s\nContent-Transfer-Encoding: 8bit\n", ADMIN_EMAIL, ADMIN_EMAIL,
ADMIN_EMAIL, $STRING['lang_charset']));
}
@@ -282,32 +281,20 @@
elseif ($v and substr($v,0,7) != 'http://') $v = 'http://'.$v;
$url = $v;
}
- if (isset($buginfo[$k]) && stripslashes($buginfo[$k]) != stripslashes($v)
- && $k != 'resolution_id') {
+ if (isset($buginfo[$k]) && stripslashes($buginfo[$k]) != stripslashes($v)) {
$changedfields[$k] = $v;
}
}
}
+ // Should we allow changes to be made to this bug by this user?
if (STRICT_UPDATING and !($u == $buginfo['assigned_to'] or
$u == $buginfo['created_by'] or $perm->have_perm('Manager'))) {
show_bug($bugid,array('status' => $STRING['bugbadperm']));
return;
}
- if ($outcome == 'reassign') {
- if (is_numeric($reassignto)) { // select box
- $assign_user_query = " where user_id = $reassignto";
- } else { // text box
- $assign_user_query = " where login = '$reassignto'";
- }
- if (!$assignedto = $db->getOne("select user_id from ".TBL_AUTH_USER.
- $assign_user_query)) {
- show_bug($bugid,array('status' => $STRING['nouser']));
- return;
- }
- }
-
+ // Check for more than one person modifying the bug at the same time
if ($last_modified_date != $buginfo['last_modified_date']) {
show_bug($bugid, array('status' => $STRING['datecollision']));
return;
@@ -368,64 +355,6 @@
}
}
-
- $changeresolution = false;
- switch($outcome) {
- case 'unchanged' : break;
- case 'assign' : $assignedto = $u; $statusfield = 'Assigned'; break;
- case 'reassign' :
- if (!$assignedto = $db->getOne("select user_id from ".TBL_AUTH_USER.
- $assign_user_query)) {
- show_bug($bugid,array('status' => $STRING['nouser']));
- return;
- } else {
- $statusfield = 'Assigned';
- $changedfields['assigned_to'] = $assignedto;
- break;
- }
- case 'reassigntocomponent' :
- $assignedto = $db->getOne("select owner from ".TBL_COMPONENT." where component_id = $component_id");
- $statusfield = 'Assigned'; break;
- case 'dupe' :
- $changeresolution = true;
- if ($dupenum == $bugid) {
- show_bug($bugid,array('status' => $STRING['dupeofself']));
- return;
- } elseif (!$db->getOne("select bug_id from ".TBL_BUG." where bug_id = $dupenum")) {
- show_bug($bugid,array('status' => $STRING['nobug']));
- return;
- }
- $db->query("insert into ".TBL_COMMENT." (comment_id, bug_id, comment_text, created_by, created_date)"
- ." values (".$db->nextId(TBL_COMMENT).", $dupenum, 'Bug #$bugid has been marked a duplicate of this bug', $u, $now)");
- $db->query("insert into ".TBL_COMMENT." (comment_id, bug_id, comment_text, created_by, created_date)"
- ." values (".$db->nextId(TBL_COMMENT).", $bugid, 'This bug is a duplicate of bug #$dupenum', $u, $now)");
- $statusfield = 'Duplicate';
- $resolution_id = $db->getOne("select resolution_id from ".TBL_RESOLUTION." where resolution_name = 'Duplicate'");
- $statusfield = 'Resolved';
- break;
- case 'resolve' :
- $changeresolution = true;
- $statusfield = 'Resolved';
- break;
- case 'reopen' :
- $changeresolution = true;
- $statusfield = 'Reopened';
- $resolution_id = 0;
- break;
- case 'verify' :
- $statusfield = 'Verified';
- break;
- case 'close' :
- $statusfield = 'Closed';
- break;
- }
- if (isset($statusfield)) {
- $status_id = $db->getOne("select status_id from ".TBL_STATUS." where status_name = '$statusfield'");
- $changedfields['status_id'] = $status_id;
- }
- if ($changeresolution) {
- $changedfields['resolution_id'] = $resolution_id;
- }
if ($comments) {
//$comments = strip_tags($comments); -- Uncomment this if you want no <> content in the comments
$db->query("insert into ".TBL_COMMENT." (comment_id, bug_id, comment_text, created_by, created_date)"
@@ -440,10 +369,8 @@
$db->query("update ".TBL_BUG." set title = ".$db->quote(stripslashes($title)).
', url = '.$db->quote(stripslashes($url)).", severity_id = $severity_id, ".
- "priority = $priority, ".
- (isset($status_id) ? "status_id = $status_id, " : '').
- ($changeresolution ? "resolution_id = $resolution_id, " : '').
- (isset($assignedto) ? "assigned_to = $assignedto, " : ' ').
+ "priority = $priority, status_id = $status_id, ".
+ "resolution_id = $resolution_id, assigned_to = $assigned_to, ".
"project_id = $project_id, version_id = $version_id, ".
"component_id = $component_id, os_id = $os_id, last_modified_by = $u, ".
"last_modified_date = $now where bug_id = $bugid");
@@ -612,6 +539,7 @@
prev_next_links($bugid, isset($_gv['pos']) ? $_gv['pos'] : 0);
$t->assign($row);
$t->assign(array(
+ 'error' => $error,
'already_voted' => $db->getOne("select count(*) from ".TBL_BUG_VOTE.
" where bug_id = $bugid and user_id = $u"),
'num_votes' => $db->getOne("select count(*) from ".TBL_BUG_VOTE.
|
|
From: Benjamin C. <bc...@us...> - 2002-04-07 08:13:55
|
Update of /cvsroot/phpbt/phpbt/templates/default
In directory usw-pr-cvs1:/tmp/cvs-serv21968/templates/default
Modified Files:
bugdisplay-printable.html bugemail-newbug.txt bugemail.txt
Log Message:
Fixed some outstanding issues with the smarty transition
Index: bugdisplay-printable.html
===================================================================
RCS file: /cvsroot/phpbt/phpbt/templates/default/bugdisplay-printable.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- bugdisplay-printable.html 3 Apr 2002 00:57:50 -0000 1.4
+++ bugdisplay-printable.html 6 Apr 2002 23:47:59 -0000 1.5
@@ -116,11 +116,11 @@
<tr>
<td>
<div align="center">
- <i>----- Posted by {$comments[comment].rreporter|maskemail} at {$comments[comment].created_date|date:TIME_FORMAT} on {$comments[comment].created_date|date:DATE_FORMAT}-----</i>
+ <i>----- Posted by {$comments[comment].login|maskemail} at {$comments[comment].created_date|date:TIME_FORMAT} on {$comments[comment].created_date|date:DATE_FORMAT}-----</i>
<br>
<br>
</div>
- {$comments[comment].rdescription|stripslashes|format_comments|nl2br}
+ {$comments[comment].comment_text|stripslashes|format_comments|nl2br}
<br>
<br>
<br>
Index: bugemail-newbug.txt
===================================================================
RCS file: /cvsroot/phpbt/phpbt/templates/default/bugemail-newbug.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- bugemail-newbug.txt 12 Dec 2001 14:42:58 -0000 1.1
+++ bugemail-newbug.txt 6 Apr 2002 23:47:59 -0000 1.2
@@ -3,25 +3,25 @@
INSTEAD FOLLOW BUG'S URL BELOW IN ORDER TO DETAIL BUG:
============================================================================
- Bug #: {bugid} ({bugurl})
- Reported By: {reporter}
+ Bug #: {$bugid} ({$bugurl})
+ Reported By: {$reporter}
----------------------------------------------------------------------------
- Summary: {title}
- URL: {url}
- Product: {project_id}
- Version: {version_id}
- Component: {component_id}
- Status: {status_id}
- Resolution: {resolution_id}
- Severity: {severity_id}
- OS/Version: {os_id}
- Priority: {priority}
- Assigned To: {assignedto}
+ Summary: {$title}
+ URL: {$url}
+ Product: {$project_id}
+ Version: {$version_id}
+ Component: {$component_id}
+ Status: {$status_id}
+ Resolution: {$resolution_id}
+ Severity: {$severity_id}
+ OS/Version: {$os_id}
+ Priority: {$priority}
+ Assigned To: {$assignedto}
============================================================================
-<!-- BEGIN commentblock -->
+{if $showcomments}
COMMENTS
------ Posted by {oldpostedby} at {oldpostedon} -----
-{oldcomments}
+----- Posted by {$oldpostedby} at {$oldpostedon} -----
+{$oldcomments}
-<!-- END commentblock -->
+{/if}
Index: bugemail.txt
===================================================================
RCS file: /cvsroot/phpbt/phpbt/templates/default/bugemail.txt,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- bugemail.txt 9 Oct 2001 08:30:37 -0000 1.3
+++ bugemail.txt 6 Apr 2002 23:47:59 -0000 1.4
@@ -3,28 +3,28 @@
INSTEAD FOLLOW BUG'S URL BELOW IN ORDER TO DETAIL BUG:
============================================================================
- Bug #: {bugid} ({bugurl})
-{reporter_stat} Reported By: {reporter}
+ Bug #: {$bugid} ({$bugurl})
+{$reporter_stat} Reported By: {$reporter}
----------------------------------------------------------------------------
-{title_stat} Summary: {title}
-{url_stat} URL: {url}
-{project_id_stat} Product: {project_id}
-{version_id_stat} Version: {version_id}
-{component_id_stat} Component: {component_id}
-{status_id_stat} Status: {status_id}
-{resolution_id_stat} Resolution: {resolution_id}
-{severity_id_stat} Severity: {severity_id}
-{os_id_stat} OS/Version: {os_id}
-{priority_stat} Priority: {priority}
-{assignedto_stat} Assigned To: {assignedto}
+{$title_stat} Summary: {$title}
+{$url_stat} URL: {$url}
+{$project_id_stat} Product: {$project_id}
+{$version_id_stat} Version: {$version_id}
+{$component_id_stat} Component: {$component_id}
+{$status_id_stat} Status: {$status_id}
+{$resolution_id_stat} Resolution: {$resolution_id}
+{$severity_id_stat} Severity: {$severity_id}
+{$os_id_stat} OS/Version: {$os_id}
+{$priority_stat} Priority: {$priority}
+{$assignedto_stat} Assigned To: {$assignedto}
============================================================================
-<!-- BEGIN commentblock -->
+{if $showcomments}
COMMENTS
------ Posted by {oldpostedby} at {oldpostedon} -----
-{oldcomments}
+----- Posted by {$oldpostedby} at {$oldpostedon} -----
+{$oldcomments}
------ Posted by {newpostedby} at {newpostedon} -----
-{newcomments}
+----- Posted by {$newpostedby} at {$newpostedon} -----
+{$newcomments}
-<!-- END commentblock -->
+{/if}
|
|
From: Ben C. <php...@be...> - 2002-04-06 23:36:40
|
My concern is this... an admin can configure the resolutions, so Duplicate may not even be an option. Even if it is, it may be in a different language, so I really can't do much checking on the client- or server-side to make sure someone who is entering a number in the "dupe of" box is also choosing duplicate for the resolution. Perhaps I should just add to the form next the comments box or somewhere in the documentation a recommendation to the user to enter a comment specifying the "dupe of" bug number when marking a bug as duplicate. Would this be more accomodating to different types of work flow? On Sat, Apr 06, 2002 at 09:24:32PM +0200, Patrick Mairif wrote: > > Or should I have > > a text box to the side of the resolution select box just for that one > > resolution? > > I think this is the best solution. A text box with a short comment. > > _______________________________________________ > phpbt-dev mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpbt-dev |
|
From: Patrick M. <mo...@su...> - 2002-04-06 19:24:39
|
> Or should I have > a text box to the side of the resolution select box just for that one > resolution? I think this is the best solution. A text box with a short comment. |
Update of /cvsroot/phpbt/phpbt/docs/html In directory usw-pr-cvs1:/tmp/cvs-serv28734/html Modified Files: adminguide.html bugsearch.html configuration.html devguide.html devstandards.html index.html schema.html Added Files: installation.html Log Message: Updating for 0.8.0 --- NEW FILE: installation.html --- <HTML ><HEAD ><TITLE >Installation Instructions</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ "><LINK REL="HOME" TITLE="phpBugTracker" HREF="index.html"><LINK REL="UP" TITLE="Administrator's Guide" HREF="adminguide.html"><LINK REL="PREVIOUS" TITLE="Administrator's Guide" HREF="adminguide.html"><LINK REL="NEXT" TITLE="Configuration Options" HREF="configuration.html"><LINK REL="STYLESHEET" TYPE="text/css" HREF="docs.css"></HEAD ><BODY CLASS="SECT1" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#800080" ALINK="#FF0000" ><DIV CLASS="NAVHEADER" ><TABLE SUMMARY="Header navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TH COLSPAN="3" ALIGN="center" >phpBugTracker</TH ></TR ><TR ><TD WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A HREF="adminguide.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="80%" ALIGN="center" VALIGN="bottom" >Chapter 2. Administrator's Guide</TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A HREF="configuration.html" ACCESSKEY="N" >Next</A ></TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A NAME="INSTALLATION">2.2. Installation Instructions</H1 ><DIV CLASS="PROCEDURE" ><A NAME="INSTALL-PROCEDURE" ></A ><OL TYPE="1" ><LI ><P >Copy the directory tree from the tarball (or zip archive) to a location suitable for serving web pages.</P ></LI ><LI ><P >With your web browser, go the location where you installed the package. You will be presented with a web page that will help you configure and install the application.</P ></LI ><LI ><P >After completing the installation, login and start reporting bugs.</P ><DIV CLASS="NOTE" ><TABLE CLASS="NOTE" WIDTH="100%" BORDER="0" ><TR ><TD WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG SRC="images/note.gif" HSPACE="5" ALT="Note"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P >Optional: Install JpGraph (<A HREF="http://www.aditus.nu/jpgraph/" TARGET="_top" >http://www.aditus.nu/jpgraph</A >) if you wish to use it for the summary bug display on the home page.</P ></TD ></TR ></TABLE ></DIV ></LI ></OL ></DIV ></DIV ><DIV CLASS="NAVFOOTER" ><HR ALIGN="LEFT" WIDTH="100%"><TABLE SUMMARY="Footer navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ><A HREF="adminguide.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="index.html" ACCESSKEY="H" >Home</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" ><A HREF="configuration.html" ACCESSKEY="N" >Next</A ></TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" >Administrator's Guide</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="adminguide.html" ACCESSKEY="U" >Up</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" >Configuration Options</TD ></TR ></TABLE ></DIV ></BODY ></HTML > Index: adminguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/adminguide.html,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- adminguide.html 28 Feb 2002 18:55:43 -0000 1.13 +++ adminguide.html 5 Apr 2002 19:06:07 -0000 1.14 @@ -13,8 +13,8 @@ TITLE="Working with Bugs" HREF="bugdetail.html"><LINK REL="NEXT" -TITLE="Configuration Options" -HREF="configuration.html"><LINK +TITLE="Installation Instructions" +HREF="installation.html"><LINK REL="STYLESHEET" TYPE="text/css" HREF="docs.css"></HEAD @@ -59,7 +59,7 @@ ALIGN="right" VALIGN="bottom" ><A -HREF="configuration.html" +HREF="installation.html" ACCESSKEY="N" >Next</A ></TD @@ -82,11 +82,16 @@ ></DT ><DT >2.1. <A -HREF="adminguide.html#INSTALLATION" ->Installation Instructions</A +HREF="adminguide.html#REQUIREMENTS" +>Requirements</A ></DT ><DT >2.2. <A +HREF="installation.html" +>Installation Instructions</A +></DT +><DT +>2.3. <A HREF="configuration.html" >Configuration Options</A ></DT @@ -106,93 +111,35 @@ ><H1 CLASS="SECT1" ><A -NAME="INSTALLATION">2.1. Installation Instructions</H1 -><DIV -CLASS="PROCEDURE" -><A -NAME="INSTALL-PROCEDURE" -></A -><OL -TYPE="1" +NAME="REQUIREMENTS">2.1. Requirements</H1 +><P +>Here is a list of things you need to have installed before you can install phpBugTracker:</P +><UL ><LI ><P ->Copy the directory tree from the tarball (or zip archive) to a location suitable for serving web pages.</P +>A web server (Apache, IIS, etc.) configured to run PHP scripts. The PHP version must be later than 4.0.6.</P ></LI ><LI ><P ->With your web browser, go the location where you installed the package. You will be presented with a web page that will help you configure and install the application.</P +>PEAR::DB. This is the database abstraction layer that comes with PEAR, which is included with recent distributions of PHP.</P ></LI ><LI ><P ->After completing the installation, login and start reporting bugs.</P -><DIV -CLASS="IMPORTANT" -><TABLE -CLASS="IMPORTANT" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="images/important.gif" -HSPACE="5" -ALT="Important"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" +>A database server. phpBugTracker has been tested with MySQL, PostgreSQL (>= 7.1 required) and Oracle 8. If you wish to run this package on another type of database, I am more than willing to support more types of databases if you are willing to help with testing.</P +></LI +><LI ><P ->You must have <TT -CLASS="VARNAME" ->magic_quotes_gpc</TT -> set to On either in <TT -CLASS="FILENAME" ->php.ini</TT -> or in <TT -CLASS="FILENAME" ->.htaccess</TT -> (see <A -HREF="http://www.php.net/manual/en/configuration.php" -TARGET="_top" ->http://www.php.net/manual/en/configuration.php</A -> for more info).</P -></TD -></TR -></TABLE -></DIV -><DIV -CLASS="NOTE" -><TABLE -CLASS="NOTE" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" +>A database created on your database server for use with phpBugTracker. You will need to supply this database name during the installation process.</P +></LI +><LI ><P ->Optional: Install JpGraph (<A -HREF="http://www.aditus.nu/jpgraph/" +>Smarty templates (<A +HREF="http://smarty.php.net/" TARGET="_top" ->http://www.aditus.nu/jpgraph</A ->) if you wish to use it for the summary bug display on the home page.</P -></TD -></TR -></TABLE -></DIV +>http://smarty.php.net/</A +>). If you do not have smarty templates already installed, a package of phpBugTracker is distributed that has smarty included and ready to go.</P ></LI -></OL -></DIV +></UL ></DIV ></DIV ><DIV @@ -229,7 +176,7 @@ ALIGN="right" VALIGN="top" ><A -HREF="configuration.html" +HREF="installation.html" ACCESSKEY="N" >Next</A ></TD @@ -249,7 +196,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ->Configuration Options</TD +>Installation Instructions</TD ></TR ></TABLE ></DIV Index: bugsearch.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/bugsearch.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- bugsearch.html 28 Feb 2002 18:55:43 -0000 1.4 +++ bugsearch.html 5 Apr 2002 19:06:08 -0000 1.5 @@ -97,7 +97,7 @@ > and <SPAN CLASS="GUILABEL" >Unconfirmed</SPAN ->from the <SPAN +> from the <SPAN CLASS="GUILABEL" >Status</SPAN > box and <SPAN Index: configuration.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/configuration.html,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- configuration.html 28 Feb 2002 18:55:43 -0000 1.13 +++ configuration.html 5 Apr 2002 19:06:08 -0000 1.14 @@ -13,8 +13,8 @@ TITLE="Administrator's Guide" HREF="adminguide.html"><LINK REL="PREVIOUS" -TITLE="Administrator's Guide" -HREF="adminguide.html"><LINK +TITLE="Installation Instructions" +HREF="installation.html"><LINK REL="NEXT" TITLE="Developer's Guide" HREF="devguide.html"><LINK @@ -48,7 +48,7 @@ ALIGN="left" VALIGN="bottom" ><A -HREF="adminguide.html" +HREF="installation.html" ACCESSKEY="P" >Prev</A ></TD @@ -76,20 +76,20 @@ ><H1 CLASS="SECT1" ><A -NAME="CONFIGURATION">2.2. Configuration Options</H1 +NAME="CONFIGURATION">2.3. Configuration Options</H1 ><BLOCKQUOTE CLASS="ABSTRACT" ><DIV CLASS="ABSTRACT" ><A -NAME="AEN141"><P +NAME="AEN150"><P >Most of the options listed here can be configured via the Configuration page of the admin tools. The <TT CLASS="VARNAME" >DB_</TT > options can be found in <TT CLASS="FILENAME" >config.php</TT ->.</P +> and are specified during the installation process via the installation web page.</P ></DIV ></BLOCKQUOTE ><DIV @@ -123,7 +123,7 @@ >DB_TYPE</DT ><DD ><P ->The type of database server you are using, according to PHPlib's naming convention. Possible choices are msql, mssql, mysql, oci8, odbc, oracle, pgsql, and sybase. Note that only MySQL and PostgreSQL have been tested with phpBugTracker</P +>The type of database server you are using, according to PEAR's naming convention. Possible choices are fbsql, ibase, ifx, msql, mssql, mysql, oci8, odbc, pgsql, and sybase. Note that only MySQL, PostgreSQL and Oracle 8 have been tested with phpBugTracker</P ></DD ><DT >DB_HOST</DT @@ -182,6 +182,15 @@ > template files are located. This makes it easy to wrap the bug tracker in a completely different look.</P ></DD ><DT +>STYLE</DT +><DD +><P +>The CSS file to be used from the <TT +CLASS="FILENAME" +>styles</TT +> directory. This makes it easy to change the color scheme and other CSS properties.</P +></DD +><DT >USE_JPGRAPH</DT ><DD ><P @@ -292,6 +301,42 @@ >languages</TT > sub-directory to use for error and warning messages.</P ></DD +><DT +>STRICT_UPDATING</DT +><DD +><P +>If false, any logged-in user can make changes to a bug. If true, only the reporter, the person to whom the bug is currently assigned, and members of the Manager or Admin group can make changes to a bug.</P +></DD +><DT +>PROMOTE_VOTES</DT +><DD +><P +>The number of votes required to automatically promote a bug from the Unconfirmed to the New status. A value of 0 disables auto-promotion.</P +></DD +><DT +>MAX_USER_VOTES</DT +><DD +><P +>The total number of votes a user may file on bugs. A value of 0 disables the limit.</P +></DD +><DT +>RECALL_LOGIN</DT +><DD +><P +>Whether to show the "Remember Me" checkbox in the login form. When checked, that box will cause a cookie to be set that stores the user's login name or email address and will prefill the login area with that value the next time the user attempts to log in.</P +></DD +><DT +>SHOW_PROJECT_SUMMARIES</DT +><DD +><P +>Whether to show the detailed project stats on the home page.</P +></DD +><DT +>FORCE_LOGIN</DT +><DD +><P +>Whether users must log in before being able to browse the bugs or reports.</P +></DD ></DL ></DIV ></DIV @@ -311,7 +356,7 @@ ALIGN="left" VALIGN="top" ><A -HREF="adminguide.html" +HREF="installation.html" ACCESSKEY="P" >Prev</A ></TD @@ -339,7 +384,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ->Administrator's Guide</TD +>Installation Instructions</TD ><TD WIDTH="34%" ALIGN="center" Index: devguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/devguide.html,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- devguide.html 28 Feb 2002 18:55:43 -0000 1.19 +++ devguide.html 5 Apr 2002 19:06:08 -0000 1.20 @@ -82,23 +82,9 @@ ></DT ><DT >3.1. <A -HREF="devguide.html#DEPENDENCIES" ->Dependencies</A +HREF="devguide.html#MANIFEST" +>What's where?</A ></DT -><DD -><DL -><DT ->3.1.1. <A -HREF="devguide.html#DEP-PHPLIB" ->PHPlib</A -></DT -><DT ->3.1.2. <A -HREF="devguide.html#DEP-JPGRAPH" ->JpGraph</A -></DT -></DL -></DD ><DT >3.2. <A HREF="devstandards.html" @@ -130,7 +116,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN259"><P +NAME="AEN297"><P >Adding on to or extending phpBugTracker should be easy for those with a knowledge of PHP and SQL. New developers are always welcome to join the project at <A HREF="http://www.sourceforge.net/projects/phpbt/" TARGET="_top" @@ -143,254 +129,173 @@ ><H1 CLASS="SECT1" ><A -NAME="DEPENDENCIES">3.1. Dependencies</H1 -><BLOCKQUOTE -CLASS="ABSTRACT" -><DIV -CLASS="ABSTRACT" -><A -NAME="AEN264"><P ->phpBugTracker requires one external package, PHPlib, and can optionally use JpGraph. Of course a web server running a version of PHP later than 4.0 and a database server are also necessary.</P -></DIV -></BLOCKQUOTE -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="DEP-PHPLIB">3.1.1. PHPlib</H2 +NAME="MANIFEST">3.1. What's where?</H1 +><P +>Following is a list of the PHP files that make up phpBugTracker and the functionality contained within them:</P +><UL +><LI ><P ->As of version 0.6.0, phpBugTracker includes the required portions of the PHPlib package in the <TT +><TT CLASS="FILENAME" ->inc</TT -> sub-directory. The PHPlib code provides the database abstraction layer, html templates, and session and authentication management.</P -><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="AEN270">3.1.1.1. Database Abstraction</H3 +>attachment.php</TT +></P ><P ->Instead of using PHP's database functions directly, interactions are done via database objects, which extend PHPlib's <TT -CLASS="CLASSNAME" ->DB_Sql</TT -> class.</P -><P ->The global variable <TT -CLASS="VARNAME" ->$q</TT -> is available as an instance of the class <TT -CLASS="CLASSNAME" ->dbclass</TT ->. This class adds two functions to the <TT -CLASS="CLASSNAME" ->DB_Sql</TT -> class, <TT -CLASS="FUNCTION" ->grab()</TT -> and <TT -CLASS="FUNCTION" ->grab_field()</TT ->. If they are called with an argument, the argument is passed as a query to the database and the results are returned from that query. If no argument is passed, they return results from the previous call to <TT -CLASS="FUNCTION" ->query()</TT ->. Here are some examples:</P -><DIV -CLASS="EXAMPLE" -><A -NAME="AEN281"><P -><B ->Example 3-1. Using the database class</B -></P -><TABLE -BORDER="0" -BGCOLOR="#EEEEEE" -WIDTH="100%" -><TR -><TD -><PRE -CLASS="PROGRAMLISTING" -> // Grab one field from one record in the database - $user_email = $q->grab_field("select email from ".TBL_AUTH_USER." where user_id = 1"); - echo $user_email; - - // Stuff all the fields from a user record into an array - $user_info = $q->grab("select * from ".TBL_AUTH_USER." where user_id = 1"); - echo $user_info['email']; - - // Work with a set of records - $q->query("select * from ".TBL_AUTH_USER); - while ($row = $q->grab()) { - echo $row['email'].'<br>'; - } - </PRE -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="AEN284">3.1.1.2. Templates</H3 +>Adding, deleting, and viewing attachment information.</P +></LI +><LI ><P ->Instead of outputting HTML from the scripts, templates are used to separate the code from the HTML. The templates contain tokens that are replaced by the scripts with values. The general process for using templates is as follows:</P -><DIV -CLASS="EXAMPLE" -><A -NAME="AEN287"><P -><B ->Example 3-2. Using the template class</B -></P -><TABLE -BORDER="0" -BGCOLOR="#EEEEEE" -WIDTH="100%" -><TR -><TD -><PRE -CLASS="PROGRAMLISTING" -> // Set up the file to be used - $t->set_file('content', 'bugdisplay.html'); - - // Substitute the tokens with data - $t->set_var(array( - 'title' => $buginfo['title'], - 'description' => $buginfo['description'], - .... - )); - - // Parse the template and print it out (inside a wrap template) - $t->pparse('main', array('content', 'wrap', 'main')); - </PRE -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="AEN290">3.1.1.3. Session and Authentication</H3 +><TT +CLASS="FILENAME" +>bug.php</TT +></P +><P +>Adding, displaying, and editing bugs. This includes the detailed view of a bug, printable view, bug history, a view of the votes for a bug, and the code that emails users about bug changes.</P +></LI +><LI ><P ->The session start and authentication code is included in <TT +><TT +CLASS="FILENAME" +>config-dist.php</TT +></P +><P +>This file is used as a template for generating the configuration file during installation.</P +></LI +><LI +><P +><TT +CLASS="FILENAME" +>config.php</TT +></P +><P +>This file is empty in the distribution package. When phpBugTracker has been installed this is the main configuration file that contains the table name definitions and includes the required packages.</P +></LI +><LI +><P +><TT CLASS="FILENAME" >include.php</TT ->. The session is started by a call to <TT -CLASS="FUNCTION" ->page_open()</TT ->, with the arguments specifying which session elements should be created. phpBugTracker uses the <TT -CLASS="CLASSNAME" ->Auth</TT -> and <TT -CLASS="CLASSNAME" ->Perm</TT -> classes from PHPlib in addition to the base <TT -CLASS="CLASSNAME" ->Session</TT -> class. </P -><DIV -CLASS="FORMALPARA" +></P +><P +>This file is included by every other script at page load, and contains page set-up such as creating the database connection, initializing the template object, and doing authentication checks.</P +></LI +><LI +><P +><TT +CLASS="FILENAME" +>install.php</TT +></P +><P +>This file is used during the installation process to gather configuration information from the user and to set up the database.</P +></LI +><LI ><P -><B ->Session. </B ->Session variables, or variables that should be retained from page to page, are set via the <TT -CLASS="VARNAME" ->$sess</TT -> variable, which is an instantiation of the <TT -CLASS="CLASSNAME" ->usess</TT -> class. You can register a session variable with <TT +><TT +CLASS="FILENAME" +>logout.php</TT +></P +><P +>This is used to end the user's session.</P +></LI +><LI +><P +><TT +CLASS="FILENAME" +>newaccount.php</TT +></P +><P +>The code for creating new accounts and emailing accout information to new sers is located here.</P +></LI +><LI +><P +><TT +CLASS="FILENAME" +>query.php</TT +></P +><P +>The bug search form is rendered and handled by this script, along with the resulting list of bugs from a query.</P +></LI +><LI +><P +><TT +CLASS="FILENAME" +>report.php</TT +></P +><P +>Various summary reports.</P +></LI +><LI +><P +><TT +CLASS="FILENAME" +>upgrade.php</TT +></P +><P +>Used when upgrading to a new verison of phpBugTracker. This file is changed with every release to include (mainly) the database queries required to upgrade the installation to the latest version.</P +></LI +><LI +><P +><TT +CLASS="FILENAME" +>user.php</TT +></P +><P +>User preferences and password changes are handled via this script.</P +></LI +><LI +><P +><TT +CLASS="FILENAME" +>admin/*.php</TT +></P +><P +>Each of these files handles a segment of the adminsitration. That is, <TT +CLASS="FILENAME" +>group.php</TT +> handles all the group adminstration, <TT +CLASS="FILENAME" +>project.php</TT +> is used for the project administration, etc.</P +></LI +><LI +><P +><TT +CLASS="FILENAME" +>inc/auth.php</TT +></P +><P +>Authentication class.</P +></LI +><LI +><P +><TT +CLASS="FILENAME" +>inc/functions.php</TT +></P +><P +>Supporting functions such as <TT CLASS="FUNCTION" ->$sess->register('<TT -CLASS="REPLACEABLE" -><I ->varname</I -></TT ->')</TT ->. When registering, make sure you don't include the $ with <TT -CLASS="REPLACEABLE" -><I ->varname</I -></TT ->. This variable will now be available in the global scope until the session is destroyed by the user closing the browser.</P -></DIV -><DIV -CLASS="FORMALPARA" +>build_select()</TT +>, etc.</P +></LI +><LI ><P -><B ->Auth. </B ->The login handler is located near the end of <TT +><TT CLASS="FILENAME" ->include.php</TT ->. Via the <TT -CLASS="CLASSNAME" ->uath</TT -> class, the global variable <TT -CLASS="VARNAME" ->$u</TT -> is set to the user id of the user if logged in, or to 'nobody' if not logged in. This variable should be used as the CreatedBy or LastModifiedBy value for database inserts and updates.</P -></DIV -><DIV -CLASS="FORMALPARA" +>inc/db/*.php</TT +></P ><P -><B ->Perm. </B ->There are two types of checks that are made in phpBugTracker: permission and group membership. These checks can be made two different ways -- one that exits and displays an access denied message (useful for protecting an entire page) or one that returns whether the user passed the check (useful for determining whether to display a piece of information).</P -></DIV -><DIV -CLASS="EXAMPLE" -><A -NAME="AEN315"><P -><B ->Example 3-3. Permission and Group Checking</B -></P -><TABLE -BORDER="0" -BGCOLOR="#EEEEEE" -WIDTH="100%" -><TR -><TD -><PRE -CLASS="PROGRAMLISTING" -> // Non-failing checks - if ($perm->have_perm('EditBug')) { - echo 'You can edit a bug!'; - } - if ($perm->in_group('User')) { - echo 'You are logged in and belong to the User group'; - } - - // Failing checks -- the script exits at this point if the check fails - $perm->check('Admin'); - $perm->check_group('Developer'); - </PRE -></TD -></TR -></TABLE -></DIV -></DIV -></DIV -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="DEP-JPGRAPH">3.1.2. JpGraph</H2 +>These files, named by database type, contain queries (such as left joins) that have different syntaxes among various database types.</P +></LI +><LI ><P ->This section will not cover the usage of JpGraph in any detail, since it is not an integral part of phpBugTracker. Developers who are interested in using this class for generating bug reports or charting activity can see <TT +><TT CLASS="FILENAME" ->index.php</TT -> for an example and are encouraged to visit JpGraph's web site at <A -HREF="http://www.aditus.nu/jpgraph/" -TARGET="_top" ->http://www.aditus.nu/jpgraph</A ->.</P -></DIV +>languages/*.php</TT +></P +><P +>Named by language code, these files contain the localization of the text used throughout phpBugTracker.</P +></LI +></UL ></DIV ></DIV ><DIV Index: devstandards.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/devstandards.html,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- devstandards.html 28 Feb 2002 18:55:43 -0000 1.20 +++ devstandards.html 5 Apr 2002 19:06:08 -0000 1.21 @@ -82,7 +82,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN325"><P +NAME="AEN377"><P > This section details the coding and process standards to be followed by the developers working on phpBugTracker. </P Index: index.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/index.html,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- index.html 28 Feb 2002 18:55:44 -0000 1.17 +++ index.html 5 Apr 2002 19:06:08 -0000 1.18 @@ -77,11 +77,16 @@ ><DL ><DT >2.1. <A -HREF="adminguide.html#INSTALLATION" ->Installation Instructions</A +HREF="adminguide.html#REQUIREMENTS" +>Requirements</A ></DT ><DT >2.2. <A +HREF="installation.html" +>Installation Instructions</A +></DT +><DT +>2.3. <A HREF="configuration.html" >Configuration Options</A ></DT @@ -96,8 +101,8 @@ ><DL ><DT >3.1. <A -HREF="devguide.html#DEPENDENCIES" ->Dependencies</A +HREF="devguide.html#MANIFEST" +>What's where?</A ></DT ><DT >3.2. <A @@ -111,31 +116,6 @@ ></DT ></DL ></DD -></DL -></DIV -><DIV -CLASS="LOT" -><DL -CLASS="LOT" -><DT -><B ->List of Examples</B -></DT -><DT ->3-1. <A -HREF="devguide.html#AEN281" ->Using the database class</A -></DT -><DT ->3-2. <A -HREF="devguide.html#AEN287" ->Using the template class</A -></DT -><DT ->3-3. <A -HREF="devguide.html#AEN315" ->Permission and Group Checking</A -></DT ></DL ></DIV ></DIV Index: schema.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/schema.html,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- schema.html 28 Feb 2002 18:55:44 -0000 1.5 +++ schema.html 5 Apr 2002 19:06:08 -0000 1.6 @@ -73,120 +73,9 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN383"><P +NAME="AEN435"><P ><B ->Table 3-1. Schema for table active_sessions</B -></P -><TABLE -BORDER="1" -CLASS="CALSTABLE" -><THEAD -><TR -><TH -ALIGN="LEFT" -VALIGN="TOP" ->Field</TH -><TH -ALIGN="LEFT" -VALIGN="TOP" ->Type</TH -><TH -ALIGN="LEFT" -VALIGN="TOP" ->Key</TH -><TH -ALIGN="LEFT" -VALIGN="TOP" ->Description</TH -></TR -></THEAD -><TBODY -><TR -><TD -ALIGN="LEFT" -VALIGN="TOP" ->sid</TD -><TD -ALIGN="LEFT" -VALIGN="TOP" ->varchar(32)</TD -><TD -ALIGN="LEFT" -VALIGN="TOP" ->Primary</TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -> </TD -></TR -><TR -><TD -ALIGN="LEFT" -VALIGN="TOP" ->name</TD -><TD -ALIGN="LEFT" -VALIGN="TOP" ->varchar(32)</TD -><TD -ALIGN="LEFT" -VALIGN="TOP" ->Primary</TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -> </TD -></TR -><TR -><TD -ALIGN="LEFT" -VALIGN="TOP" ->val</TD -><TD -ALIGN="LEFT" -VALIGN="TOP" ->text</TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -> </TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -> </TD -></TR -><TR -><TD -ALIGN="LEFT" -VALIGN="TOP" ->changed</TD -><TD -ALIGN="LEFT" -VALIGN="TOP" ->varchar(14)</TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -> </TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -> </TD -></TR -></TBODY -></TABLE -></DIV -><P ->This table is used by PHPlib to store session information. It is updated with every call to <TT -CLASS="FUNCTION" ->page_close()</TT ->.</P -><DIV -CLASS="TABLE" -><A -NAME="AEN415"><P -><B ->Table 3-2. Schema for table attachment</B +>Table 3-1. Schema for table attachment</B ></P ><TABLE BORDER="1" @@ -362,9 +251,9 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN465"><P +NAME="AEN485"><P ><B ->Table 3-3. Schema for table auth_group</B +>Table 3-2. Schema for table auth_group</B ></P ><TABLE BORDER="1" @@ -524,9 +413,9 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN511"><P +NAME="AEN531"><P ><B ->Table 3-4. Schema for table auth_perm</B +>Table 3-3. Schema for table auth_perm</B ></P ><TABLE BORDER="1" @@ -671,9 +560,9 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN553"><P +NAME="AEN573"><P ><B ->Table 3-5. Schema for table auth_user</B +>Table 3-4. Schema for table auth_user</B ></P ><TABLE BORDER="1" @@ -921,9 +810,9 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN623"><P +NAME="AEN643"><P ><B ->Table 3-6. Schema for table bug</B +>Table 3-5. Schema for table bug</B ></P ><TABLE BORDER="1" @@ -1306,9 +1195,9 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN731"><P +NAME="AEN751"><P ><B ->Table 3-7. Schema for table bug_cc</B +>Table 3-6. Schema for table bug_cc</B ></P ><TABLE BORDER="1" @@ -1412,7 +1301,77 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN761"><P +NAME="AEN781"><P +><B +>Table 3-7. Schema for table bug_dependency</B +></P +><TABLE +BORDER="1" +CLASS="CALSTABLE" +><THEAD +><TR +><TH +ALIGN="LEFT" +VALIGN="TOP" +>Field</TH +><TH +ALIGN="LEFT" +VALIGN="TOP" +>Type</TH +><TH +ALIGN="LEFT" +VALIGN="TOP" +>Key</TH +><TH +ALIGN="LEFT" +VALIGN="TOP" +>Description</TH +></TR +></THEAD +><TBODY +><TR +><TD +ALIGN="LEFT" +VALIGN="TOP" +>bug_id</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +>int(10) unsigned</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +>Primary</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +> </TD +></TR +><TR +><TD +ALIGN="LEFT" +VALIGN="TOP" +>depends_on</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +>int(10) unsigned</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +>Primary</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +> </TD +></TR +></TBODY +></TABLE +></DIV +><DIV +CLASS="TABLE" +><A +NAME="AEN801"><P ><B >Table 3-8. Schema for table bug_group</B ></P @@ -1456,7 +1415,7 @@ ><TD ALIGN="LEFT" VALIGN="TOP" ->Foreign</TD +> </TD ></TR ><TR ><TD @@ -1474,7 +1433,7 @@ ><TD ALIGN="LEFT" VALIGN="TOP" ->Foreign</TD +> </TD ></TR ></TBODY ></TABLE @@ -1484,9 +1443,97 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN782"><P +NAME="AEN822"><P ><B ->Table 3-9. Schema for table bug_history</B +>Table 3-9. Schema for table bug_vote</B +></P +><TABLE +BORDER="1" +CLASS="CALSTABLE" +><THEAD +><TR +><TH +ALIGN="LEFT" +VALIGN="TOP" +>Field</TH +><TH +ALIGN="LEFT" +VALIGN="TOP" +>Type</TH +><TH +ALIGN="LEFT" +VALIGN="TOP" +>Key</TH +><TH +ALIGN="LEFT" +VALIGN="TOP" +>Description</TH +></TR +></THEAD +><TBODY +><TR +><TD +ALIGN="LEFT" +VALIGN="TOP" +>user_id</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +>int(10) unsigned</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +>Primary</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +> </TD +></TR +><TR +><TD +ALIGN="LEFT" +VALIGN="TOP" +>bug_id</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +>int(10) unsigned</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +>Primary</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +> </TD +></TR +><TR +><TD +ALIGN="LEFT" +VALIGN="TOP" +>created_date</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +>bigint(20) unsigned</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +> </TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +> </TD +></TR +></TBODY +></TABLE +></DIV +><DIV +CLASS="TABLE" +><A +NAME="AEN847"><P +><B +>Table 3-10. Schema for table bug_history</B ></P ><TABLE BORDER="1" @@ -1626,9 +1673,9 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN822"><P +NAME="AEN887"><P ><B ->Table 3-10. Schema for table comment</B +>Table 3-11. Schema for table comment</B ></P ><TABLE BORDER="1" @@ -1750,9 +1797,9 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN857"><P +NAME="AEN922"><P ><B ->Table 3-11. Schema for table component</B +>Table 3-12. Schema for table component</B ></P ><TABLE BORDER="1" @@ -1967,9 +2014,9 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN918"><P +NAME="AEN983"><P ><B ->Table 3-12. Schema for table configuration</B +>Table 3-13. Schema for table configuration</B ></P ><TABLE BORDER="1" @@ -2075,79 +2122,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN949"><P -><B ->Table 3-13. Schema for table db_sequence</B -></P -><TABLE -BORDER="1" -CLASS="CALSTABLE" -><THEAD -><TR -><TH -ALIGN="LEFT" -VALIGN="TOP" ->Field</TH -><TH -ALIGN="LEFT" -VALIGN="TOP" ->Type</TH -><TH -ALIGN="LEFT" -VALIGN="TOP" ->Key</TH -><TH -ALIGN="LEFT" -VALIGN="TOP" ->Description</TH -></TR -></THEAD -><TBODY -><TR -><TD -ALIGN="LEFT" -VALIGN="TOP" ->seq_name</TD -><TD -ALIGN="LEFT" -VALIGN="TOP" ->varchar(127)</TD -><TD -ALIGN="LEFT" -VALIGN="TOP" ->Primary</TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -> </TD -></TR -><TR -><TD -ALIGN="LEFT" -VALIGN="TOP" ->nextid</TD -><TD -ALIGN="LEFT" -VALIGN="TOP" ->int(10) unsigned</TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -> </TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -> </TD -></TR -></TBODY -></TABLE -></DIV -><P ->PHPlib uses this table in generating the incrementing primary key sequences for the other tables.</P -><DIV -CLASS="TABLE" -><A -NAME="AEN970"><P +NAME="AEN1014"><P ><B >Table 3-14. Schema for table group_perm</B ></P @@ -2217,7 +2192,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN990"><P +NAME="AEN1034"><P ><B >Table 3-15. Schema for table os</B ></P @@ -2323,7 +2298,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1020"><P +NAME="AEN1064"><P ><B >Table 3-16. Schema for table project</B ></P @@ -2501,7 +2476,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1070"><P +NAME="AEN1114"><P ><B >Table 3-17. Schema for table project_group</B ></P @@ -2607,7 +2582,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1100"><P +NAME="AEN1144"><P ><B >Table 3-18. Schema for table resolution</B ></P @@ -2713,7 +2688,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1130"><P +NAME="AEN1174"><P ><B >Table 3-19. Schema for table saved_query</B ></P @@ -2824,7 +2799,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1162"><P +NAME="AEN1206"><P ><B >Table 3-20. Schema for table severity</B ></P @@ -2951,7 +2926,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1198"><P +NAME="AEN1242"><P ><B >Table 3-21. Schema for table status</B ></P @@ -3057,7 +3032,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1228"><P +NAME="AEN1272"><P ><B >Table 3-22. Schema for table user_group</B ></P @@ -3163,7 +3138,7 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1258"><P +NAME="AEN1302"><P ><B >Table 3-23. Schema for table user_perm</B ></P @@ -3233,9 +3208,79 @@ ><DIV CLASS="TABLE" ><A -NAME="AEN1278"><P +NAME="AEN1322"><P +><B +>Table 3-24. Schema for table user_pref</B +></P +><TABLE +BORDER="1" +CLASS="CALSTABLE" +><THEAD +><TR +><TH +ALIGN="LEFT" +VALIGN="TOP" +>Field</TH +><TH +ALIGN="LEFT" +VALIGN="TOP" +>Type</TH +><TH +ALIGN="LEFT" +VALIGN="TOP" +>Key</TH +><TH +ALIGN="LEFT" +VALIGN="TOP" +>Description</TH +></TR +></THEAD +><TBODY +><TR +><TD +ALIGN="LEFT" +VALIGN="TOP" +>user_id</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +>int(10) unsigned</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +>Primary</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +> </TD +></TR +><TR +><TD +ALIGN="LEFT" +VALIGN="TOP" +>email_notices</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +>tinyint(1)</TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +> </TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +>Whether the user wants to receive email notices from phpBugTracker. Values are 1 for yes (default) or 0 for no.</TD +></TR +></TBODY +></TABLE +></DIV +><DIV +CLASS="TABLE" +><A +NAME="AEN1342"><P ><B ->Table 3-24. Schema for table version</B +>Table 3-25. Schema for table version</B ></P ><TABLE BORDER="1" |
|
From: Benjamin C. <bc...@us...> - 2002-04-05 19:06:12
|
Update of /cvsroot/phpbt/phpbt/docs/sgml In directory usw-pr-cvs1:/tmp/cvs-serv28734/sgml Modified Files: configuration.sgml installation.sgml phpbt.sgml schema.sgml Added Files: manifest.sgml requirements.sgml Removed Files: dependencies.sgml Log Message: Updating for 0.8.0 --- NEW FILE: manifest.sgml --- <!-- -*- sgml -*- --> <sect1 id="manifest"> <title>What's where?</title> <para>Following is a list of the PHP files that make up &phpbt; and the functionality contained within them:</para> <itemizedlist> <listitem> <para><filename>attachment.php</filename></para> <para>Adding, deleting, and viewing attachment information.</para> </listitem> <listitem> <para><filename>bug.php</filename></para> <para>Adding, displaying, and editing bugs. This includes the detailed view of a bug, printable view, bug history, a view of the votes for a bug, and the code that emails users about bug changes.</para> </listitem> <listitem> <para><filename>config-dist.php</filename></para> <para>This file is used as a template for generating the configuration file during installation.</para> </listitem> <listitem> <para><filename>config.php</filename></para> <para>This file is empty in the distribution package. When &phpbt; has been installed this is the main configuration file that contains the table name definitions and includes the required packages.</para> </listitem> <listitem> <para><filename>include.php</filename></para> <para>This file is included by every other script at page load, and contains page set-up such as creating the database connection, initializing the template object, and doing authentication checks.</para> </listitem> <listitem> <para><filename>install.php</filename></para> <para>This file is used during the installation process to gather configuration information from the user and to set up the database.</para> </listitem> <listitem> <para><filename>logout.php</filename></para> <para>This is used to end the user's session.</para> </listitem> <listitem> <para><filename>newaccount.php</filename></para> <para>The code for creating new accounts and emailing accout information to new sers is located here.</para> </listitem> <listitem> <para><filename>query.php</filename></para> <para>The bug search form is rendered and handled by this script, along with the resulting list of bugs from a query.</para> </listitem> <listitem> <para><filename>report.php</filename></para> <para>Various summary reports.</para> </listitem> <listitem> <para><filename>upgrade.php</filename></para> <para>Used when upgrading to a new verison of &phpbt;. This file is changed with every release to include (mainly) the database queries required to upgrade the installation to the latest version.</para> </listitem> <listitem> <para><filename>user.php</filename></para> <para>User preferences and password changes are handled via this script.</para> </listitem> <listitem> <para><filename>admin/*.php</filename></para> <para>Each of these files handles a segment of the adminsitration. That is, <filename>group.php</filename> handles all the group adminstration, <filename>project.php</filename> is used for the project administration, etc.</para> </listitem> <listitem> <para><filename>inc/auth.php</filename></para> <para>Authentication class.</para> </listitem> <listitem> <para><filename>inc/functions.php</filename></para> <para>Supporting functions such as <function>build_select()</function>, etc.</para> </listitem> <listitem> <para><filename>inc/db/*.php</filename></para> <para>These files, named by database type, contain queries (such as left joins) that have different syntaxes among various database types.</para> </listitem> <listitem> <para><filename>languages/*.php</filename></para> <para>Named by language code, these files contain the localization of the text used throughout &phpbt;.</para> </listitem> </itemizedlist> </sect1> <!-- Local Variables: --> <!-- sgml-parent-document: "phpbt.sgml" --> <!-- End: --> --- NEW FILE: requirements.sgml --- <!-- -*- sgml -*- --> <sect1 id="requirements"> <title>Requirements</title> <para>Here is a list of things you need to have installed before you can install &phpbt;:</para> <itemizedlist> <listitem> <para>A web server (Apache, IIS, etc.) configured to run PHP scripts. The PHP version must be later than 4.0.6.</para> </listitem> <listitem> <para>PEAR::DB. This is the database abstraction layer that comes with PEAR, which is included with recent distributions of PHP.</para> </listitem> <listitem> <para>A database server. &phpbt; has been tested with MySQL, PostgreSQL (>= 7.1 required) and Oracle 8. If you wish to run this package on another type of database, I am more than willing to support more types of databases if you are willing to help with testing.</para> </listitem> <listitem> <para>A database created on your database server for use with &phpbt;. You will need to supply this database name during the installation process.</para> </listitem> <listitem> <para>Smarty templates (<ulink url="http://smarty.php.net/">http://smarty.php.net/</ulink>). If you do not have smarty templates already installed, a package of &phpbt; is distributed that has smarty included and ready to go.</para> </listitem> </itemizedlist> </sect1> <!-- Local Variables: --> <!-- sgml-parent-document: "phpbt.sgml" --> <!-- End: --> Index: configuration.sgml =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/sgml/configuration.sgml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- configuration.sgml 15 Dec 2001 18:58:15 -0000 1.6 +++ configuration.sgml 5 Apr 2002 19:06:08 -0000 1.7 @@ -3,7 +3,7 @@ <title>Configuration Options</title> <abstract> -<para>Most of the options listed here can be configured via the Configuration page of the admin tools. The <varname>DB_</varname> options can be found in <filename>config.php</filename>.</para> +<para>Most of the options listed here can be configured via the Configuration page of the admin tools. The <varname>DB_</varname> options can be found in <filename>config.php</filename> and are specified during the installation process via the installation web page.</para> </abstract> <variablelist> @@ -28,7 +28,7 @@ <varlistentry> <term>DB_TYPE</term> <listitem> -<para>The type of database server you are using, according to PHPlib's naming convention. Possible choices are msql, mssql, mysql, oci8, odbc, oracle, pgsql, and sybase. Note that only MySQL and PostgreSQL have been tested with &phpbt;</para> +<para>The type of database server you are using, according to PEAR's naming convention. Possible choices are fbsql, ibase, ifx, msql, mssql, mysql, oci8, odbc, pgsql, and sybase. Note that only MySQL, PostgreSQL and Oracle 8 have been tested with &phpbt;</para> </listitem> </varlistentry> <varlistentry> @@ -75,6 +75,12 @@ </listitem> </varlistentry> <varlistentry> +<term>STYLE</term> +<listitem> +<para>The CSS file to be used from the <filename class="directory">styles</filename> directory. This makes it easy to change the color scheme and other CSS properties.</para> +</listitem> +</varlistentry> +<varlistentry> <term>USE_JPGRAPH</term> <listitem> <para>Whether to use the <ulink url="http://www.aditus.nu/jpgraph/">JpGraph</ulink> graphing class for some reports.</para> @@ -144,6 +150,42 @@ <term>LANGUAGE</term> <listitem> <para>The language file (found in the <filename class="directory">languages</filename> sub-directory to use for error and warning messages.</para> +</listitem> +</varlistentry> +<varlistentry> +<term>STRICT_UPDATING</term> +<listitem> +<para>If false, any logged-in user can make changes to a bug. If true, only the reporter, the person to whom the bug is currently assigned, and members of the Manager or Admin group can make changes to a bug.</para> +</listitem> +</varlistentry> +<varlistentry> +<term>PROMOTE_VOTES</term> +<listitem> +<para>The number of votes required to automatically promote a bug from the Unconfirmed to the New status. A value of 0 disables auto-promotion.</para> +</listitem> +</varlistentry> +<varlistentry> +<term>MAX_USER_VOTES</term> +<listitem> +<para>The total number of votes a user may file on bugs. A value of 0 disables the limit.</para> +</listitem> +</varlistentry> +<varlistentry> +<term>RECALL_LOGIN</term> +<listitem> +<para>Whether to show the "Remember Me" checkbox in the login form. When checked, that box will cause a cookie to be set that stores the user's login name or email address and will prefill the login area with that value the next time the user attempts to log in.</para> +</listitem> +</varlistentry> +<varlistentry> +<term>SHOW_PROJECT_SUMMARIES</term> +<listitem> +<para>Whether to show the detailed project stats on the home page.</para> +</listitem> +</varlistentry> +<varlistentry> +<term>FORCE_LOGIN</term> +<listitem> +<para>Whether users must log in before being able to browse the bugs or reports.</para> </listitem> </varlistentry> </variablelist> Index: installation.sgml =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/sgml/installation.sgml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- installation.sgml 28 Feb 2002 18:55:44 -0000 1.5 +++ installation.sgml 5 Apr 2002 19:06:08 -0000 1.6 @@ -13,9 +13,7 @@ <step> <para>After completing the installation, login and start reporting bugs.</para> -<important> -<para>You must have <varname>magic_quotes_gpc</varname> set to On either in <filename>php.ini</filename> or in <filename>.htaccess</filename> (see <ulink url="http://www.php.net/manual/en/configuration.php">http://www.php.net/manual/en/configuration.php</ulink> for more info).</para> -</important> + <note> <para>Optional: Install JpGraph (<ulink url="http://www.aditus.nu/jpgraph/">http://www.aditus.nu/jpgraph</ulink>) if you wish to use it for the summary bug display on the home page.</para> </note> Index: phpbt.sgml =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/sgml/phpbt.sgml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- phpbt.sgml 25 Oct 2001 13:00:21 -0000 1.9 +++ phpbt.sgml 5 Apr 2002 19:06:08 -0000 1.10 @@ -11,12 +11,13 @@ <!ENTITY bugdetail SYSTEM "bugdetail.sgml"> <!-- Administrator's Guide --> +<!ENTITY requirements SYSTEM "requirements.sgml"> <!ENTITY installation SYSTEM "installation.sgml"> <!ENTITY configuration SYSTEM "configuration.sgml"> <!-- Developer's Guide --> <!ENTITY devstandards SYSTEM "devstandards.sgml"> -<!ENTITY dependencies SYSTEM "dependencies.sgml"> +<!ENTITY manifest SYSTEM "manifest.sgml"> <!ENTITY schema SYSTEM "schema.sgml"> ]> @@ -47,6 +48,7 @@ <para>One of the main design goals of &phpbt; is to make installation and administration easy. In fact, the difficulty of installing bugzilla was a key motivator for &phpbt;'s existence.</para> </abstract> +&requirements; &installation; &configuration; @@ -58,7 +60,7 @@ <para>Adding on to or extending &phpbt; should be easy for those with a knowledge of PHP and SQL. New developers are always welcome to join the project at <ulink url="http://www.sourceforge.net/projects/phpbt/">http://www.sourceforge.net/projects/phpbt</ulink>, or to simply submit patches, bug reports, or feature requests.</para> </abstract> -&dependencies; +&manifest; &devstandards; &schema; Index: schema.sgml =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/sgml/schema.sgml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- schema.sgml 15 Dec 2001 18:58:15 -0000 1.2 +++ schema.sgml 5 Apr 2002 19:06:08 -0000 1.3 @@ -3,48 +3,6 @@ <title>Database Schema</title> <table> -<title>Schema for table active_sessions</title> -<tgroup cols="4"> -<thead> -<row> -<entry>Field</entry> -<entry>Type</entry> -<entry>Key</entry> -<entry>Description</entry> -</row> -</thead> -<tbody> -<row> -<entry>sid</entry> -<entry>varchar(32)</entry> -<entry>Primary</entry> -<entry></entry> -</row> -<row> -<entry>name</entry> -<entry>varchar(32)</entry> -<entry>Primary</entry> -<entry></entry> -</row> -<row> -<entry>val</entry> -<entry>text</entry> -<entry></entry> -<entry></entry> -</row> -<row> -<entry>changed</entry> -<entry>varchar(14)</entry> -<entry></entry> -<entry></entry> -</row> -</tbody> -</tgroup> -</table> - -<para>This table is used by PHPlib to store session information. It is updated with every call to <function>page_close()</function>.</para> - -<table> <title>Schema for table attachment</title> <tgroup cols="4"> <thead> @@ -479,6 +437,34 @@ </table> <table> +<title>Schema for table bug_dependency</title> +<tgroup cols="4"> +<thead> +<row> +<entry>Field</entry> +<entry>Type</entry> +<entry>Key</entry> +<entry>Description</entry> +</row> +</thead> +<tbody> +<row> +<entry>bug_id</entry> +<entry>int(10) unsigned</entry> +<entry>Primary</entry> +<entry></entry> +</row> +<row> +<entry>depends_on</entry> +<entry>int(10) unsigned</entry> +<entry>Primary</entry> +<entry></entry> +</row> +</tbody> +</tgroup> +</table> + +<table> <title>Schema for table bug_group</title> <tgroup cols="4"> <thead> @@ -494,13 +480,13 @@ <entry>bug_id</entry> <entry>int(10) unsigned</entry> <entry>Primary</entry> -<entry>Foreign</entry> +<entry></entry> </row> <row> <entry>group_id</entry> <entry>int(10) unsigned</entry> <entry>Primary</entry> -<entry>Foreign</entry> +<entry></entry> </row> </tbody> </tgroup> @@ -508,6 +494,40 @@ <para>This table isn't currently used.</para> <table> +<title>Schema for table bug_vote</title> +<tgroup cols="4"> +<thead> +<row> +<entry>Field</entry> +<entry>Type</entry> +<entry>Key</entry> +<entry>Description</entry> +</row> +</thead> +<tbody> +<row> +<entry>user_id</entry> +<entry>int(10) unsigned</entry> +<entry>Primary</entry> +<entry></entry> +</row> +<row> +<entry>bug_id</entry> +<entry>int(10) unsigned</entry> +<entry>Primary</entry> +<entry></entry> +</row> +<row> +<entry>created_date</entry> +<entry>bigint(20) unsigned</entry> +<entry></entry> +<entry></entry> +</row> +</tbody> +</tgroup> +</table> + +<table> <title>Schema for table bug_history</title> <tgroup cols="4"> <thead> @@ -723,35 +743,6 @@ <para>This table stores the configuration for &phpbt;</para> <table> -<title>Schema for table db_sequence</title> -<tgroup cols="4"> -<thead> -<row> -<entry>Field</entry> -<entry>Type</entry> -<entry>Key</entry> -<entry>Description</entry> -</row> -</thead> -<tbody> -<row> -<entry>seq_name</entry> -<entry>varchar(127)</entry> -<entry>Primary</entry> -<entry></entry> -</row> -<row> -<entry>nextid</entry> -<entry>int(10) unsigned</entry> -<entry></entry> -<entry></entry> -</row> -</tbody> -</tgroup> -</table> -<para>PHPlib uses this table in generating the incrementing primary key sequences for the other tables.</para> - -<table> <title>Schema for table group_perm</title> <tgroup cols="4"> <thead> @@ -1153,6 +1144,34 @@ <entry>int(10) unsigned</entry> <entry>Primary</entry> <entry></entry> +</row> +</tbody> +</tgroup> +</table> + +<table> +<title>Schema for table user_pref</title> +<tgroup cols="4"> +<thead> +<row> +<entry>Field</entry> +<entry>Type</entry> +<entry>Key</entry> +<entry>Description</entry> +</row> +</thead> +<tbody> +<row> +<entry>user_id</entry> +<entry>int(10) unsigned</entry> +<entry>Primary</entry> +<entry></entry> +</row> +<row> +<entry>email_notices</entry> +<entry>tinyint(1)</entry> +<entry></entry> +<entry>Whether the user wants to receive email notices from &phpbt;. Values are 1 for yes (default) or 0 for no.</entry> </row> </tbody> </tgroup> --- dependencies.sgml DELETED --- |
|
From: John W. <jp...@us...> - 2002-04-04 23:38:05
|
Update of /cvsroot/phpbt/phpbt
In directory usw-pr-cvs1:/tmp/cvs-serv25430
Modified Files:
install.php
Log Message:
Allow Smarty to be used in install.php from locations other than include path (define)
Basic error checking on initial connection to database
Index: install.php
===================================================================
RCS file: /cvsroot/phpbt/phpbt/install.php,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- install.php 3 Apr 2002 23:21:30 -0000 1.21
+++ install.php 4 Apr 2002 23:30:42 -0000 1.22
@@ -25,7 +25,12 @@
define ('INSTALL_PATH', dirname(__FILE__));
-if (!@include('Smarty.class.php')) { // Template class
+// Location of smarty templates class
+ define ('SMARTY_PATH','');
+ // Example if smarty is installed within the phpBugTracker tree.
+ //define ('SMARTY_PATH','./inc/smarty/');
+
+if (!@include(SMARTY_PATH . 'Smarty.class.php')) { // Template class
die('<br><br>
<div align="center">The Smarty templates class is not in your include path.
Without this class being available, phpBugTracker will not be able to work.
@@ -160,6 +165,18 @@
'password' => $_pv['db_pass']
);
$db = DB::Connect($dsn);
+ // Simple error checking on returned DB object to check connection to db
+ if(get_class($db)=='db_error') {
+ die('<br><br>
+ <div align="center">The installation script could not connect to the database (' . $_pv['db_database'] .
+ ') on the host (' . $_pv['db_host'] . ') using the specified username and password.
+ <br>
+ Please check these details are correct and that the database already exists then retry.
+ </div>
+ ');
+ }
+
+
$db->setOption('optimize', 'portability');
$q_temp_ary = file('schemas/'.$_pv['db_type'].'.in');
@@ -255,7 +272,5 @@
} else {
show_front();
}
-
+// Any whitespace below the end tag will disrupt config.php
?>
-
-
|
|
From: Ben C. <php...@be...> - 2002-04-04 21:15:46
|
I'm working on changing how the bug resolution is changed. Currently it'd done with dynamic radio buttons, but I want to switch it to using a select box, as requested in the feature requests. This presents one problem -- marking a bug as duplicate. With the select box it becomes awkward to add a text box for specifying the other bug (the first of the orignal - dupe pair). See http://phpbt.sourceforge.net/bug.jpg. I'm thinking of just dropping the "this is a dupe of bug #x" auto-comment. Would this be a satisfactory solution? Or should I have a text box to the side of the resolution select box just for that one resolution? Of course there is a javascript option, or a second page with just that field in a form, but I want to do neither of those. What do you think? |
|
From: Benjamin C. <bc...@us...> - 2002-04-04 18:35:33
|
Update of /cvsroot/phpbt/phpbt/inc
In directory usw-pr-cvs1:/tmp/cvs-serv24522/inc
Modified Files:
functions.php
Log Message:
Only show active versions and components -- duh
Index: functions.php
===================================================================
RCS file: /cvsroot/phpbt/phpbt/inc/functions.php,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- functions.php 3 Apr 2002 18:18:02 -0000 1.17
+++ functions.php 4 Apr 2002 18:35:30 -0000 1.18
@@ -73,8 +73,8 @@
? $querystart." where active > 0 order by {$box}_name"
: $querystart." where project_id not in ($restricted_projects)".
" and active > 0 order by {$box}_name",
- 'component' => $querystart." where project_id = $project order by {$box}_name",
- 'version' => $querystart." where project_id = $project order by {$box}_id desc"
+ 'component' => $querystart." where project_id = $project and active = 1 order by {$box}_name",
+ 'version' => $querystart." where project_id = $project and active = 1 order by {$box}_id desc"
);
}
|
|
From: Benjamin C. <bc...@us...> - 2002-04-04 15:55:35
|
Update of /cvsroot/phpbt/phpbt/inc/db In directory usw-pr-cvs1:/tmp/cvs-serv29408/inc/db Modified Files: mysql.php oci8.php pgsql.php Log Message: Added deleting of unused versions and components Index: mysql.php =================================================================== RCS file: /cvsroot/phpbt/phpbt/inc/db/mysql.php,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- mysql.php 3 Apr 2002 19:08:48 -0000 1.4 +++ mysql.php 4 Apr 2002 13:30:17 -0000 1.5 @@ -141,6 +141,16 @@ 'left join '.TBL_AUTH_USER.' u on assigned_to = user_id %s '. 'group by assigned_to, u.email', 'join-where' => 'where', + 'admin-list-components' => 'select c.component_id, component_name, '. + 'c.created_date, active, count(bug_id) as bug_count '. + 'from '.TBL_COMPONENT.' c left join '.TBL_BUG.' b using(component_id) '. + 'where c.project_id = %s '. + 'group by c.component_id, c.component_name, c.created_date, c.active', + 'admin-list-versions' => 'select v.version_id, version_name, '. + 'v.created_date, active, count(bug_id) as bug_count '. + 'from '.TBL_VERSION.' v left join '.TBL_BUG.' b using(version_id) '. + 'where v.project_id = %s '. + 'group by v.version_id, v.version_name, v.created_date, v.active', ); ?> Index: oci8.php =================================================================== RCS file: /cvsroot/phpbt/phpbt/inc/db/oci8.php,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- oci8.php 3 Apr 2002 19:08:48 -0000 1.3 +++ oci8.php 4 Apr 2002 13:30:17 -0000 1.4 @@ -145,6 +145,16 @@ 'where b.assigned_to = u.user_id(+) %s '. 'group by assigned_to, u.email', 'join-where' => 'and', + 'admin-list-components' => 'select c.component_id, component_name, '. + 'c.created_date, active, count(bug_id) as bug_count '. + 'from '.TBL_COMPONENT.' c, '.TBL_BUG.' b '. + 'where c.project_id = %s and c.component_id = b.component_id(+) '. + 'group by c.component_id, c.component_name, c.created_date, c.active', + 'admin-list-versions' => 'select v.version_id, version_name, '. + 'v.created_date, active, count(bug_id) as bug_count '. + 'from '.TBL_VERSION.' v, '.TBL_BUG.' b '. + 'where v.project_id = %s and v.version_id = b.version_id(+) '. + 'group by v.version_id, v.version_name, v.created_date, v.active', ); ?> Index: pgsql.php =================================================================== RCS file: /cvsroot/phpbt/phpbt/inc/db/pgsql.php,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- pgsql.php 3 Apr 2002 19:08:48 -0000 1.5 +++ pgsql.php 4 Apr 2002 13:30:17 -0000 1.6 @@ -141,6 +141,16 @@ 'left join '.TBL_AUTH_USER.' u on assigned_to = user_id %s '. 'group by assigned_to, u.email', 'join-where' => 'where', + 'admin-list-components' => 'select c.component_id, component_name, '. + 'c.created_date, active, count(bug_id) as bug_count '. + 'from '.TBL_COMPONENT.' c left join '.TBL_BUG.' b using(component_id) '. + 'where c.project_id = %s '. + 'group by c.component_id, c.component_name, c.created_date, c.active', + 'admin-list-versions' => 'select v.version_id, version_name, '. + 'v.created_date, active, count(bug_id) as bug_count '. + 'from '.TBL_VERSION.' v left join '.TBL_BUG.' b using(version_id) '. + 'where v.project_id = %s '. + 'group by v.version_id, v.version_name, v.created_date, v.active', ); ?> |
2 messages has been excluded from this view by a project administrator.
