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...> - 2001-10-02 04:06:37
|
Update of /cvsroot/phpbt/phpbt/docs/html In directory usw-pr-cvs1:/tmp/cvs-serv7712 Added Files: devstandards.html Log Message: Poor orphan! |
|
From: Benjamin C. <bc...@us...> - 2001-10-02 04:03:54
|
Update of /cvsroot/phpbt/phpbt/docs/html/images
In directory usw-pr-cvs1:/tmp/cvs-serv7101/images
Added Files:
caution.gif home.gif important.gif next.gif note.gif prev.gif
tip.gif toc-blank.gif toc-minus.gif toc-plus.gif up.gif
warning.gif
Log Message:
Screenshots and doc images
--- NEW FILE: caution.gif ---
GIF87a
$N$ø¢Á
4>pиña
(e|¸QGE(YÀ
--- NEW FILE: home.gif ---
GIF87a#
--- NEW FILE: important.gif ---
GIF87a
|ÜÜ°s 5WR
8Pܼ"i'c9,Ù""ÈØLdÇOW¾
--- NEW FILE: next.gif ---
GIF87a#
%pQ "8T@À(¦<X`%C$¨±ÂL8
hÐðc
--- NEW FILE: note.gif ---
GIF87a
!!!"""###$$$%%%&&&'''((()))***+++,,,---...///000111222333444555666777888999:::;;;<<<===>>>???@@@AAABBBCCCDDDEEEFFFGGGHHHIIIJJJKKKLLLMMMNNNOOOPPPQQQRRRSSSTTTUUUVVVWWWXXXYYYZZZ[[[\\\]]]^^^___```aaabbbcccdddeeefffggghhhiiijjjkkklllmmmnnnooopppqqqrrrssstttuuuvvvwwwxxxyyyzzz{{{|||}}}~~~
¡¡¡¢¢¢£££¤¤¤¥¥¥¦¦¦§§§¨¨¨©©©ªªª«««¬¬¬®®®¯¯¯°°°±±±²²²³³³´´´µµµ¶¶¶···¸¸¸¹¹¹ººº»»»¼¼¼½½½¾¾¾¿¿¿ÀÀÀÁÁÁÂÂÂÃÃÃÄÄÄÅÅÅÆÆÆÇÇÇÈÈÈÉÉÉÊÊÊËËËÌÌÌÍÍÍÎÎÎÏÏÏÐÐÐÑÑÑÒÒÒÓÓÓÔÔÔÕÕÕÖÖÖ×××ØØØÙÙÙÚÚÚÛÛÛÜÜÜÝÝÝÞÞÞßßßàààáááâââãããäääåååæææçççèèèéééêêêëëëìììíííîîîïïïðððñññòòòóóóôôôõõõööö÷÷÷øøøùùùúúúûûûüüüýýýþþþÿÿÿ,
<Ò³9M½u
élF²ßQ£E=5k-5ö¤·»SîázÒ¿wÖ=ëQb½sTö¸$eJ{Jq\³Ç«±=@ýWËÀZ!×l3ƦÂR±Æ<-%3!c[B*òÓã'{ÙÆxèÎá¯yýǨøÀ^ Süj l¿ÃÄQî9o;µ6 $HÜÚ
--- NEW FILE: prev.gif ---
GIF87a#
¤
--- NEW FILE: tip.gif ---
GIF87a
!!!"""###$$$%%%&&&'''((()))***+++,,,---...///000111222333444555666777888999:::;;;<<<===>>>???@@@AAABBBCCCDDDEEEFFFGGGHHHIIIJJJKKKLLLMMMNNNOOOPPPQQQRRRSSSTTTUUUVVVWWWXXXYYYZZZ[[[\\\]]]^^^___```aaabbbcccdddeeefffggghhhiiijjjkkklllmmmnnnooopppqqqrrrssstttuuuvvvwwwxxxyyyzzz{{{|||}}}~~~
¡¡¡¢¢¢£££¤¤¤¥¥¥¦¦¦§§§¨¨¨©©©ªªª«««¬¬¬®®®¯¯¯°°°±±±²²²³³³´´´µµµ¶¶¶···¸¸¸¹¹¹ººº»»»¼¼¼½½½¾¾¾¿¿¿ÀÀÀÁÁÁÂÂÂÃÃÃÄÄÄÅÅÅÆÆÆÇÇÇÈÈÈÉÉÉÊÊÊËËËÌÌÌÍÍÍÎÎÎÏÏÏÐÐÐÑÑÑÒÒÒÓÓÓÔÔÔÕÕÕÖÖÖ×××ØØØÙÙÙÚÚÚÛÛÛÜÜÜÝÝÝÞÞÞßßßàààáááâââãããäääåååæææçççèèèéééêêêëëëìììíííîîîïïïðððñññòòòóóóôôôõõõööö÷÷÷øøøùùùúúúûûûüüüýýýþþþÿÿÿ,
W&tVªåÀ{{B¬ÁY°TI¥¼7¥yF¹ÐÑ
*^UÈhÏ ª
k
é`
--- NEW FILE: toc-blank.gif ---
GIF89a
--- NEW FILE: toc-minus.gif ---
GIF89a
--- NEW FILE: toc-plus.gif ---
GIF89a
--- NEW FILE: up.gif ---
GIF87a#
--- NEW FILE: warning.gif ---
GIF87a
|
|
From: Benjamin C. <bc...@us...> - 2001-10-02 04:03:54
|
Update of /cvsroot/phpbt/phpbt/docs/html/images/callouts In directory usw-pr-cvs1:/tmp/cvs-serv7101/images/callouts Added Files: 1.gif 10.gif 2.gif 3.gif 4.gif 5.gif 6.gif 7.gif 8.gif 9.gif Log Message: Screenshots and doc images --- NEW FILE: 1.gif --- GIF89a üX @ --- NEW FILE: 10.gif --- GIF89a *0 --- NEW FILE: 2.gif --- GIF89a hàÂÀ*\À@A i ç 5 --- NEW FILE: 3.gif --- GIF89a VVÈè B , --- NEW FILE: 4.gif --- GIF89a Ä Jph`èG --- NEW FILE: 5.gif --- GIF89a --- NEW FILE: 6.gif --- GIF89a Ü --- NEW FILE: 7.gif --- GIF89a ) ù´âB(PT`@ --- NEW FILE: 8.gif --- GIF89a Ä 5@H@ --- NEW FILE: 9.gif --- GIF89a I>@à r:Ì @ ÀD@ >È <, °°P*0 |
|
From: Benjamin C. <bc...@us...> - 2001-10-02 03:59:52
|
Update of /cvsroot/phpbt/phpbt/docs/html/images/shots/user In directory usw-pr-cvs1:/tmp/cvs-serv6385/images/shots/user Log Message: Directory /cvsroot/phpbt/phpbt/docs/html/images/shots/user added to the repository |
|
From: Benjamin C. <bc...@us...> - 2001-10-02 03:59:45
|
Update of /cvsroot/phpbt/phpbt/docs/html/images/shots In directory usw-pr-cvs1:/tmp/cvs-serv6359/images/shots Log Message: Directory /cvsroot/phpbt/phpbt/docs/html/images/shots added to the repository |
|
From: Benjamin C. <bc...@us...> - 2001-10-02 03:59:29
|
Update of /cvsroot/phpbt/phpbt/docs/html/images/callouts In directory usw-pr-cvs1:/tmp/cvs-serv6308/images/callouts Log Message: Directory /cvsroot/phpbt/phpbt/docs/html/images/callouts added to the repository |
|
From: Benjamin C. <bc...@us...> - 2001-10-02 03:59:10
|
Update of /cvsroot/phpbt/phpbt/docs/html/images In directory usw-pr-cvs1:/tmp/cvs-serv6267/images Log Message: Directory /cvsroot/phpbt/phpbt/docs/html/images added to the repository |
|
From: Benjamin C. <bc...@us...> - 2001-10-02 03:41:22
|
Update of /cvsroot/phpbt/phpbt/admin
In directory usw-pr-cvs1:/tmp/cvs-serv2709/admin
Modified Files:
project.php
Log Message:
Fixed bug when updating a project
Index: project.php
===================================================================
RCS file: /cvsroot/phpbt/phpbt/admin/project.php,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- project.php 2001/09/18 03:26:15 1.18
+++ project.php 2001/10/02 03:41:19 1.19
@@ -187,7 +187,7 @@
}
if ($error) { show_project($projectid, $error); return; }
- if (!$_pv['projectid']) {
+ if (!$projectid) {
if (!$_pv['vf_version'] = htmlspecialchars(trim($_pv['vf_version']))) {
$error['version'] = $STRING['giveversion'];
} elseif (!$_pv['cf_name'] = trim($_pv['cf_name'])) {
|
|
From: Ben C. <php...@be...> - 2001-10-01 13:06:26
|
One thing I've been thinking about for a little while that we need is a development road map. I'd like to get your input on what you would like to see in the next few versions. Specifically, what should we put into versions 0.4 and 0.5 if we were to release them in the months of October and November, repsectively? Also, I'd like to be ready for a 1.0 that we can call non-beta either in late December or early January. Thoughts? |
|
From: Benjamin C. <bc...@us...> - 2001-10-01 01:12:40
|
Update of /cvsroot/phpbt/phpbt/docs/sgml
In directory usw-pr-cvs1:/tmp/cvs-serv30583/sgml
Modified Files:
configuration.sgml dependencies.sgml docs.dsl phpbt.sgml
Log Message:
Filled in the configuration options, added more to the dependencies section, changed the TOC generation
Index: configuration.sgml
===================================================================
RCS file: /cvsroot/phpbt/phpbt/docs/sgml/configuration.sgml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- configuration.sgml 2001/09/29 18:35:54 1.1
+++ configuration.sgml 2001/10/01 01:12:38 1.2
@@ -25,6 +25,109 @@
<para>Location of your cvs web interface (see <function>format_comments()</function> in <filename>bug.php</filename>). This is for links to files in CVS generated from the comments attached to bugs.</para>
</listitem>
</varlistentry>
+ <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>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>DB_HOST</term>
+ <listitem>
+ <para>The hostname of the database server.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>DB_DATABASE</term>
+ <listitem>
+ <para>The name of the database to be used.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>DB_USER</term>
+ <listitem>
+ <para>Username to use for connecting to the database.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>DB_PASSWORD</term>
+ <listitem>
+ <para>The password to use for connecting to the database.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>ADMINEMAIL</term>
+ <listitem>
+ <para>The email address that will be used for all correspondence to and from the bug tracker.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>ENCRYPTPASS</term>
+ <listitem>
+ <para>When true, passwords will be stored as an <function>md5()</function> hash in the database. When false, they will be stored as plaintext.</para>
+ <para>If this is set to true, a new password will be generated for users if they request their password to be emailed to them, as the encryption is not reversible.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>THEME</term>
+ <listitem>
+ <para>The directory below the <filename>templates</filename> directory (both in the top directory and the <filename>admin</filename> directory) where the <acronym>HTML</acronym> template files are located. This makes it easy to wrap the bug tracker in a completely different look.</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>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>MASK_EMAIL</term>
+ <listitem>
+ <para>If true, then email addresses will be shown as <computeroutput>example at example dot com</computeroutput>. Otherwise, email addresses will be shown as <computeroutput>ex...@ex...</computeroutput>.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>HIDE_EMAIL</term>
+ <listitem>
+ <para>If true, email addresses will be shown as <computeroutput>******</computeroutput> to users who are not logged in (to help avoid spam bots on public bug trackers). If false, email addresses will be shown according the setting of <varname>MASK_EMAIL</varname>, above.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>USE_SEVERITY_COLOR</term>
+ <listitem>
+ <para>Whether to color the rows of the bug list according to the severity of the bugs. The severity colors can be set via the admin interface. If this is false, the bugs will be listed with alternating background colors of white and gray.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>EMAIL_IS_LOGIN</term>
+ <listitem>
+ <para>If true, then users login with their email address, and the email address is shown for fields such as Assigned To and Reported By. If false, the login is not tied to the user's email address.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>ATTACHMENT_PATH</term>
+ <listitem>
+ <para>The subdirectory in which to store bug attachments. This directory needs to writeable by the web server.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>ATTACHMENT_MAX_SIZE</term>
+ <listitem>
+ <para>Maximum size (in bytes) of an attachment. This will not override the settings in <filename>php.ini</filename> if <filename>php.ini</filename> has a lower limit.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>DATEFORMAT</term>
+ <listitem>
+ <para>The format for displaying the date, according to PHP's <ulink url="http://www.php.net/manual/function.date.php"><function>date()</function></ulink> function.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>TIMEFORMAT</term>
+ <listitem>
+ <para>The format for displaying the date, according to PHP's <ulink url="http://www.php.net/manual/function.date.php"><function>date()</function></ulink> function.</para>
+ </listitem>
+ </varlistentry>
</variablelist>
</sect1>
Index: dependencies.sgml
===================================================================
RCS file: /cvsroot/phpbt/phpbt/docs/sgml/dependencies.sgml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- dependencies.sgml 2001/09/27 13:40:20 1.1
+++ dependencies.sgml 2001/10/01 01:12:38 1.2
@@ -3,13 +3,51 @@
<title>Dependencies</title>
<abstract>
- <para>&phpbt; requires one external package, PHPlib, and can optionally use JpGraph.</para>
+ <para>&phpbt; requires one external package, PHPlib, and can optionally use JpGraph. Of course a web server and a database are also necessary.</para>
</abstract>
<sect2 id="dep-phplib">
<title>PHPlib</title>
<para>PHPlib can be found at <ulink url="http://phplib.sourceforge.net/">http://phplib.sourceforge.net</ulink>. It provides the database abstraction layer, html templates, and session and authentication management.</para>
+ <sect3>
+ <title>Database Abstraction</title>
+ <para>Instead of using PHP's database functions directly, interactions are done via database objects, which extend PHPlib's <classname>DB_Sql</classname> class.</para>
+ <para>The global variable <varname>$q</varname> is available as an instance of the class <classname>dbclass</classname>. This class adds two functions to the <classname>DB_Sql</classname> class, <function>grab()</function> and <function>grab_field()</function>. 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 <function>query()</function>. Here are some examples:</para>
+ <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>';
+ }
+ </programlisting>
+ </sect3>
+ <sect3>
+ <title>Templates</title>
+ <para>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:</para>
+ <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');
+ </programlisting>
+ </sect3>
</sect2>
</sect1>
Index: docs.dsl
===================================================================
RCS file: /cvsroot/phpbt/phpbt/docs/sgml/docs.dsl,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- docs.dsl 2001/09/29 18:35:34 1.2
+++ docs.dsl 2001/10/01 01:12:38 1.3
@@ -22,7 +22,7 @@
(define (toc-depth nd)
(if (string=? (gi nd) (normalize "book"))
- 3
+ 2
2))
Index: phpbt.sgml
===================================================================
RCS file: /cvsroot/phpbt/phpbt/docs/sgml/phpbt.sgml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- phpbt.sgml 2001/09/29 18:35:54 1.3
+++ phpbt.sgml 2001/10/01 01:12:38 1.4
@@ -19,7 +19,7 @@
<bookinfo>
<title>&phpbt;</title>
<abstract>
- <para>&phpbt; is a web-based bug reporting and tracking system. It allows development teams to manage the testing and debugging segments of the development cycle.</para>
+ <para>&phpbt; is a web-based bug reporting and tracking system. It helps development teams to manage the testing and debugging segments of the development cycle.</para>
</abstract>
</bookinfo>
@@ -47,8 +47,8 @@
<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>
- &devstandards;
&dependencies;
+ &devstandards;
</chapter>
</book>
|
|
From: Benjamin C. <bc...@us...> - 2001-10-01 01:12:40
|
Update of /cvsroot/phpbt/phpbt/docs/html In directory usw-pr-cvs1:/tmp/cvs-serv30583/html Modified Files: configuration.html dependencies.html devguide.html index.html Log Message: Filled in the configuration options, added more to the dependencies section, changed the TOC generation Index: configuration.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/configuration.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- configuration.html 2001/09/29 18:35:54 1.1 +++ configuration.html 2001/10/01 01:12:38 1.2 @@ -123,6 +123,158 @@ >bug.php</TT >). This is for links to files in CVS generated from the comments attached to bugs.</P ></DD +><DT +>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 +></DD +><DT +>DB_HOST</DT +><DD +><P +>The hostname of the database server.</P +></DD +><DT +>DB_DATABASE</DT +><DD +><P +>The name of the database to be used.</P +></DD +><DT +>DB_USER</DT +><DD +><P +>Username to use for connecting to the database.</P +></DD +><DT +>DB_PASSWORD</DT +><DD +><P +>The password to use for connecting to the database.</P +></DD +><DT +>ADMINEMAIL</DT +><DD +><P +>The email address that will be used for all correspondence to and from the bug tracker.</P +></DD +><DT +>ENCRYPTPASS</DT +><DD +><P +>When true, passwords will be stored as an <TT +CLASS="FUNCTION" +>md5()</TT +> hash in the database. When false, they will be stored as plaintext.</P +><P +>If this is set to true, a new password will be generated for users if they request their password to be emailed to them, as the encryption is not reversible.</P +></DD +><DT +>THEME</DT +><DD +><P +>The directory below the <TT +CLASS="FILENAME" +>templates</TT +> directory (both in the top directory and the <TT +CLASS="FILENAME" +>admin</TT +> directory) where the <SPAN +CLASS="ACRONYM" +>HTML</SPAN +> template files are located. This makes it easy to wrap the bug tracker in a completely different look.</P +></DD +><DT +>USE_JPGRAPH</DT +><DD +><P +>Whether to use the <A +HREF="http://www.aditus.nu/jpgraph/" +TARGET="_top" +>JpGraph</A +> graphing class for some reports.</P +></DD +><DT +>MASK_EMAIL</DT +><DD +><P +>If true, then email addresses will be shown as <TT +CLASS="COMPUTEROUTPUT" +>example at example dot com</TT +>. Otherwise, email addresses will be shown as <TT +CLASS="COMPUTEROUTPUT" +>ex...@ex...</TT +>.</P +></DD +><DT +>HIDE_EMAIL</DT +><DD +><P +>If true, email addresses will be shown as <TT +CLASS="COMPUTEROUTPUT" +>******</TT +> to users who are not logged in (to help avoid spam bots on public bug trackers). If false, email addresses will be shown according the setting of <TT +CLASS="VARNAME" +>MASK_EMAIL</TT +>, above.</P +></DD +><DT +>USE_SEVERITY_COLOR</DT +><DD +><P +>Whether to color the rows of the bug list according to the severity of the bugs. The severity colors can be set via the admin interface. If this is false, the bugs will be listed with alternating background colors of white and gray.</P +></DD +><DT +>EMAIL_IS_LOGIN</DT +><DD +><P +>If true, then users login with their email address, and the email address is shown for fields such as Assigned To and Reported By. If false, the login is not tied to the user's email address.</P +></DD +><DT +>ATTACHMENT_PATH</DT +><DD +><P +>The subdirectory in which to store bug attachments. This directory needs to writeable by the web server.</P +></DD +><DT +>ATTACHMENT_MAX_SIZE</DT +><DD +><P +>Maximum size (in bytes) of an attachment. This will not override the settings in <TT +CLASS="FILENAME" +>php.ini</TT +> if <TT +CLASS="FILENAME" +>php.ini</TT +> has a lower limit.</P +></DD +><DT +>DATEFORMAT</DT +><DD +><P +>The format for displaying the date, according to PHP's <A +HREF="http://www.php.net/manual/function.date.php" +TARGET="_top" +><TT +CLASS="FUNCTION" +>date()</TT +></A +> function.</P +></DD +><DT +>TIMEFORMAT</DT +><DD +><P +>The format for displaying the date, according to PHP's <A +HREF="http://www.php.net/manual/function.date.php" +TARGET="_top" +><TT +CLASS="FUNCTION" +>date()</TT +></A +> function.</P +></DD ></DL ></DIV ></DIV Index: dependencies.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/dependencies.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- dependencies.html 2001/09/29 18:35:54 1.3 +++ dependencies.html 2001/10/01 01:12:38 1.4 @@ -77,10 +77,10 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN148" +NAME="AEN232" ></A ><P ->phpBugTracker requires one external package, PHPlib, and can optionally use JpGraph.</P +>phpBugTracker requires one external package, PHPlib, and can optionally use JpGraph. Of course a web server and a database are also necessary.</P ></DIV ></BLOCKQUOTE ><DIV @@ -97,6 +97,100 @@ TARGET="_top" >http://phplib.sourceforge.net</A >. It provides the database abstraction layer, html templates, and session and authentication management.</P +><DIV +CLASS="SECT3" +><H3 +CLASS="SECT3" +><A +NAME="AEN238" +>3.2.1.1. Database Abstraction</A +></H3 +><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 +><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 +CLASS="SECT3" +><H3 +CLASS="SECT3" +><A +NAME="AEN250" +>3.2.1.2. Templates</A +></H3 +><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 +><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 ><DIV Index: devguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/devguide.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- devguide.html 2001/09/29 18:35:54 1.3 +++ devguide.html 2001/10/01 01:12:38 1.4 @@ -13,8 +13,8 @@ TITLE="Configuration Options" HREF="configuration.html"><LINK REL="NEXT" -TITLE="Dependencies" -HREF="dependencies.html"><LINK +TITLE="Development Standards" +HREF="devstandards.html"><LINK REL="STYLESHEET" TYPE="text/css" HREF="docs.css"></HEAD @@ -59,7 +59,7 @@ ALIGN="right" VALIGN="bottom" ><A -HREF="dependencies.html" +HREF="devstandards.html" ACCESSKEY="N" >Next</A ></TD @@ -84,28 +84,28 @@ ></DT ><DT >3.1. <A -HREF="devguide.html#DEVSTANDARDS" +HREF="devguide.html#DEPENDENCIES" +>Dependencies</A +></DT +><DT +>3.2. <A +HREF="devstandards.html" >Development Standards</A ></DT ><DD ><DL ><DT ->3.1.1. <A -HREF="devguide.html#DEVSTANDARDS-CODE" +>3.2.1. <A +HREF="devstandards.html#DEVSTANDARDS-CODE" >Coding Standards</A ></DT ><DT ->3.1.2. <A -HREF="devguide.html#OTHERCONVENTIONS" +>3.2.2. <A +HREF="devstandards.html#OTHERCONVENTIONS" >Other Conventions</A ></DT ></DL ></DD -><DT ->3.2. <A -HREF="dependencies.html" ->Dependencies</A -></DT ></DL ></DIV ><BLOCKQUOTE @@ -113,7 +113,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN85" +NAME="AEN169" ></A ><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 @@ -128,20 +128,18 @@ ><H1 CLASS="SECT1" ><A -NAME="DEVSTANDARDS" ->3.1. Development Standards</A +NAME="DEPENDENCIES" +>3.1. Dependencies</A ></H1 ><BLOCKQUOTE CLASS="ABSTRACT" ><DIV CLASS="ABSTRACT" ><A -NAME="AEN90" +NAME="AEN174" ></A ><P -> This section details the coding and process standards to be - followed by the developers working on phpBugTracker. - </P +>phpBugTracker requires one external package, PHPlib, and can optionally use JpGraph. Of course a web server and a database are also necessary.</P ></DIV ></BLOCKQUOTE ><DIV @@ -149,33 +147,48 @@ ><H2 CLASS="SECT2" ><A -NAME="DEVSTANDARDS-CODE" ->3.1.1. Coding Standards</A +NAME="DEP-PHPLIB" +>3.1.1. PHPlib</A ></H2 -><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="DEVSTANDARDS-INDENTING" ->3.1.1.1. Indenting</A -></H3 ><P -> Use an indent of one tab per indent. - </P -></DIV +>PHPlib can be found at <A +HREF="http://phplib.sourceforge.net/" +TARGET="_top" +>http://phplib.sourceforge.net</A +>. It provides the database abstraction layer, html templates, and session and authentication management.</P ><DIV CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="DEVSTANDARDS-CONTROL" ->3.1.1.2. Control Structures</A +NAME="AEN180" +>3.1.1.1. Database Abstraction</A ></H3 ><P -> These include if, for, while, switch, etc. Here is an example if - statement, since it is the most complicated of them: - </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 ><TABLE BORDER="0" BGCOLOR="#EEEEEE" @@ -184,42 +197,34 @@ ><TD ><PRE CLASS="PROGRAMLISTING" -> if ((condition1) || (condition2)) { - action1; - } elseif ((condition3) && (condition4)) { - action2; - } else { - defaultaction; +> // 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 + </PRE ></TD ></TR ></TABLE -><P -> Control statements should have one space between the control keyword - and opening parenthesis, to distinguish them from function calls. - </P -><P -> You are strongly encouraged to always use curly braces even in - situations where they are technically optional. Having them increases - readability and decreases the likelihood of logic errors being - introduced when new lines are added. - </P ></DIV ><DIV CLASS="SECT3" ><H3 CLASS="SECT3" ><A -NAME="DEVSTANDARDS-FUNCCALLS" ->3.1.1.3. Function Calls</A +NAME="AEN192" +>3.1.1.2. Templates</A ></H3 ><P -> Functions should be called with no spaces between the function name, - the opening parenthesis, and the first parameter; spaces between - commas and each parameter, and no space between the last parameter, - the closing parenthesis, and the semicolon. Here's an example: - </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 ><TABLE BORDER="0" BGCOLOR="#EEEEEE" @@ -228,222 +233,22 @@ ><TD ><PRE CLASS="PROGRAMLISTING" -> $var = foo($bar, $baz, $quux); - </PRE -></TD -></TR -></TABLE -><P -> As displayed above, there should be one space on either side of an - equals sign used to assign the return value of a function to a variable. - </P -></DIV -><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="DEVSTANDARDS-FUNCDEFS" ->3.1.1.4. Function Definitions</A -></H3 -><P -> Function definitions follow the format of function calls, with the - opening brace at the end of the line of the function declaration. The - global variable list (if used) should be placed on the line immediately - following the opening brace, with a blank line between the variable - list and the first line of function code. If the global variable list - is not neccessary, include a blank line between the opening brace and - the first line of function code. - </P -><TABLE -BORDER="0" -BGCOLOR="#EEEEEE" -WIDTH="100%" -><TR -><TD -><PRE -CLASS="PROGRAMLISTING" -> function fooFunction($arg1, $arg2 = '') { - global $foo1, $foo2; +> // Set up the file to be used + $t->set_file('content', 'bugdisplay.html'); - if (condition) { - statement; - } - return $val; - } - </PRE + // 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 -><P -> Arguments with default values go at the end of the argument list. - Always attempt to return a meaningful value from a function if one is - appropriate. Here is a slightly longer example: - </P -><TABLE -BORDER="0" -BGCOLOR="#EEEEEE" -WIDTH="100%" -><TR -><TD -><PRE -CLASS="PROGRAMLISTING" -> function connect(&$dsn, $persistent = false) { - - if (is_array($dsn)) { - $dsninfo = &$dsn; - } else { - $dsninfo = DB::parseDSN($dsn); - } - - if (!$dsninfo || !$dsninfo['phptype']) { - return $this->raiseError(); - } - - return true; - } - </PRE -></TD -></TR -></TABLE -></DIV -><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="DEVSTANDARDS-COMMENTS" ->3.1.1.5. Comments</A -></H3 -><P -> Non-documentation comments are strongly encouraged. A general rule of - thumb is that if you look at a section of code and think "Wow, I don't - want to try and describe that", you need to comment it before you - forget how it works. - </P -></DIV -><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="DEVSTANDARDS-INCLUDING" ->3.1.1.6. Including Code</A -></H3 -><P -> Anywhere you are unconditionally including a class file, use - <A -HREF="http://php.net/manual/en/html/function.require-once.html" -TARGET="_top" -> <TT -CLASS="FUNCTION" ->require_once()</TT -></A ->. Anywhere you are - conditionally including a class file (for example, factory methods), - use <A -HREF="http://php.net/manual/en/html/function.include-once.html" -TARGET="_top" -> <TT -CLASS="FUNCTION" ->include_once()</TT -></A ->. Either of these will - ensure that class files are included only once. They share the same file - list, so you don't need to worry about mixing them - a file included - with <TT -CLASS="FUNCTION" ->require_once()</TT -> will not be included again by - <TT -CLASS="FUNCTION" ->include_once()</TT ->. - </P -></DIV -><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="DEVSTANDARDS-PHPTAGS" ->3.1.1.7. PHP Tags</A -></H3 -><P -> Always use <TT -CLASS="COMPUTEROUTPUT" -><?php ?></TT -> - to delimit PHP code, not the <TT -CLASS="COMPUTEROUTPUT" -><? ?></TT -> - shorthand. - </P -></DIV -><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="DEVSTANDARDS-CONSTANTS" ->3.1.1.8. Naming Constants</A -></H3 -><P -> Constants should always be uppercase, with underscores to separate - words. - </P -></DIV -></DIV -><DIV -CLASS="SECT2" -><H2 -CLASS="SECT2" -><A -NAME="OTHERCONVENTIONS" ->3.1.2. Other Conventions</A -></H2 -><DIV -CLASS="SECT3" -><H3 -CLASS="SECT3" -><A -NAME="DEVSTANDARDS-FILENAMING" ->3.1.2.1. File Naming</A -></H3 -><P -> File names should be all lowercase and contain no spaces. HTML files - should have <TT -CLASS="FILENAME" ->.html</TT -> as the extension, and PHP files - should have <TT -CLASS="FILENAME" ->.php</TT -> as the extension. Where possible, - template files should match the name of the PHP file that will be using - it, e. g., <TT -CLASS="FILENAME" ->index.html</TT -> would be the template file - for <TT -CLASS="FILENAME" ->index.php</TT ->. Where one PHP file uses more than one - template, the templates should be similarly named: - <TT -CLASS="FILENAME" ->user.php</TT -> could use - <TT -CLASS="FILENAME" ->userlist.html</TT -> and <TT -CLASS="FILENAME" ->userform.html</TT -> - for a list of users and editing a user, respectively. - </P ></DIV ></DIV ></DIV @@ -482,7 +287,7 @@ ALIGN="right" VALIGN="top" ><A -HREF="dependencies.html" +HREF="devstandards.html" ACCESSKEY="N" >Next</A ></TD @@ -502,7 +307,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ->Dependencies</TD +>Development Standards</TD ></TR ></TABLE ></DIV Index: index.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/index.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- index.html 2001/09/29 18:35:54 1.3 +++ index.html 2001/10/01 01:12:38 1.4 @@ -39,7 +39,7 @@ NAME="AEN4" ></A ><P ->phpBugTracker is a web-based bug reporting and tracking system. It allows development teams to manage the testing and debugging segments of the development cycle.</P +>phpBugTracker is a web-based bug reporting and tracking system. It helps development teams to manage the testing and debugging segments of the development cycle.</P ></DIV ></DIV ><HR></DIV @@ -83,37 +83,14 @@ ><DL ><DT >3.1. <A -HREF="devguide.html#DEVSTANDARDS" ->Development Standards</A -></DT -><DD -><DL -><DT ->3.1.1. <A -HREF="devguide.html#DEVSTANDARDS-CODE" ->Coding Standards</A -></DT -><DT ->3.1.2. <A -HREF="devguide.html#OTHERCONVENTIONS" ->Other Conventions</A -></DT -></DL -></DD -><DT ->3.2. <A -HREF="dependencies.html" +HREF="devguide.html#DEPENDENCIES" >Dependencies</A ></DT -><DD -><DL ><DT ->3.2.1. <A -HREF="dependencies.html#DEP-PHPLIB" ->PHPlib</A +>3.2. <A +HREF="devstandards.html" +>Development Standards</A ></DT -></DL -></DD ></DL ></DD ></DL |
|
From: Benjamin C. <bc...@us...> - 2001-09-29 18:35:57
|
Update of /cvsroot/phpbt/phpbt/docs/html In directory usw-pr-cvs1:/tmp/cvs-serv20908/html Modified Files: adminguide.html dependencies.html devguide.html index.html userguide.html Added Files: configuration.html Log Message: Started on configuration options --- NEW FILE: configuration.html --- <HTML ><HEAD ><TITLE >Configuration Options</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.72 "><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="Developer's Guide" HREF="devguide.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="devguide.html" ACCESSKEY="N" >Next</A ></TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A NAME="CONFIGURATION" >2.2. Configuration Options</A ></H1 ><BLOCKQUOTE CLASS="ABSTRACT" ><DIV CLASS="ABSTRACT" ><A NAME="AEN64" ></A ><P >The options listed in this section can be configured by the <TT CLASS="FILENAME" >configure</TT > script and can be found in <TT CLASS="FILENAME" >config.php</TT >.</P ></DIV ></BLOCKQUOTE ><DIV CLASS="VARIABLELIST" ><DL ><DT >INSTALLPATH</DT ><DD ><P >Location on disk of the phpBugTracker installation.</P ></DD ><DT >INSTALLURL</DT ><DD ><P >URL that is the home of the installation.</P ></DD ><DT >CVS_WEB</DT ><DD ><P >Location of your cvs web interface (see <TT CLASS="FUNCTION" >format_comments()</TT > in <TT CLASS="FILENAME" >bug.php</TT >). This is for links to files in CVS generated from the comments attached to bugs.</P ></DD ></DL ></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="devguide.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" >Developer's Guide</TD ></TR ></TABLE ></DIV ></BODY ></HTML > Index: adminguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/adminguide.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- adminguide.html 2001/09/29 04:02:38 1.2 +++ adminguide.html 2001/09/29 18:35:54 1.3 @@ -13,8 +13,8 @@ TITLE="User's Guide" HREF="userguide.html"><LINK REL="NEXT" -TITLE="Developer's Guide" -HREF="devguide.html"><LINK +TITLE="Configuration Options" +HREF="configuration.html"><LINK REL="STYLESHEET" TYPE="text/css" HREF="docs.css"></HEAD @@ -59,7 +59,7 @@ ALIGN="right" VALIGN="bottom" ><A -HREF="devguide.html" +HREF="configuration.html" ACCESSKEY="N" >Next</A ></TD @@ -75,6 +75,25 @@ NAME="ADMINGUIDE" >Chapter 2. Administrator's Guide</A ></H1 +><DIV +CLASS="TOC" +><DL +><DT +><B +>Table of Contents</B +></DT +><DT +>2.1. <A +HREF="adminguide.html#INSTALLATION" +>Installation Instructions</A +></DT +><DT +>2.2. <A +HREF="configuration.html" +>Configuration Options</A +></DT +></DL +></DIV ><BLOCKQUOTE CLASS="ABSTRACT" ><DIV @@ -83,11 +102,7 @@ NAME="AEN12" ></A ><P -></P -><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 -><P -></P ></DIV ></BLOCKQUOTE ><DIV @@ -98,8 +113,6 @@ NAME="INSTALLATION" >2.1. Installation Instructions</A ></H1 -><P -></P ><OL TYPE="1" ><LI @@ -167,9 +180,7 @@ ></P ><P >Configure manually: - <P -></P -><OL + <OL TYPE="a" ><LI ><P @@ -278,7 +289,7 @@ ALIGN="right" VALIGN="top" ><A -HREF="devguide.html" +HREF="configuration.html" ACCESSKEY="N" >Next</A ></TD @@ -298,7 +309,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ->Developer's Guide</TD +>Configuration Options</TD ></TR ></TABLE ></DIV Index: dependencies.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/dependencies.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- dependencies.html 2001/09/29 04:02:38 1.2 +++ dependencies.html 2001/09/29 18:35:54 1.3 @@ -77,14 +77,10 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN127" +NAME="AEN148" ></A ><P -></P -><P >phpBugTracker requires one external package, PHPlib, and can optionally use JpGraph.</P -><P -></P ></DIV ></BLOCKQUOTE ><DIV Index: devguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/devguide.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- devguide.html 2001/09/29 04:02:38 1.2 +++ devguide.html 2001/09/29 18:35:54 1.3 @@ -10,8 +10,8 @@ TITLE="phpBugTracker" HREF="index.html"><LINK REL="PREVIOUS" -TITLE="Administrator's Guide" -HREF="adminguide.html"><LINK +TITLE="Configuration Options" +HREF="configuration.html"><LINK REL="NEXT" TITLE="Dependencies" HREF="dependencies.html"><LINK @@ -45,7 +45,7 @@ ALIGN="left" VALIGN="bottom" ><A -HREF="adminguide.html" +HREF="configuration.html" ACCESSKEY="P" >Prev</A ></TD @@ -113,18 +113,14 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN64" +NAME="AEN85" ></A ><P -></P -><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" >http://www.sourceforge.net/projects/phpbt</A >, or to simply submit patches, bug reports, or feature requests.</P -><P -></P ></DIV ></BLOCKQUOTE ><DIV @@ -140,16 +136,12 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN69" +NAME="AEN90" ></A ><P -></P -><P > This section details the coding and process standards to be followed by the developers working on phpBugTracker. </P -><P -></P ></DIV ></BLOCKQUOTE ><DIV @@ -472,7 +464,7 @@ ALIGN="left" VALIGN="top" ><A -HREF="adminguide.html" +HREF="configuration.html" ACCESSKEY="P" >Prev</A ></TD @@ -500,7 +492,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ->Administrator's Guide</TD +>Configuration Options</TD ><TD WIDTH="34%" ALIGN="center" Index: index.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/index.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- index.html 2001/09/29 04:02:38 1.2 +++ index.html 2001/09/29 18:35:54 1.3 @@ -39,11 +39,7 @@ NAME="AEN4" ></A ><P -></P -><P >phpBugTracker is a web-based bug reporting and tracking system. It allows development teams to manage the testing and debugging segments of the development cycle.</P -><P -></P ></DIV ></DIV ><HR></DIV @@ -70,6 +66,11 @@ >2.1. <A HREF="adminguide.html#INSTALLATION" >Installation Instructions</A +></DT +><DT +>2.2. <A +HREF="configuration.html" +>Configuration Options</A ></DT ></DL ></DD Index: userguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/userguide.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- userguide.html 2001/09/27 13:40:20 1.1 +++ userguide.html 2001/09/29 18:35:54 1.2 @@ -83,11 +83,7 @@ NAME="AEN8" ></A ><P -></P -><P >Currently all interactions with phpBugTracker are done via the web interface. Users can submit bugs, communicate with developers and testers about bugs, and search through the bug database.</P -><P -></P ></DIV ></BLOCKQUOTE ></DIV |
|
From: Benjamin C. <bc...@us...> - 2001-09-29 18:35:57
|
Update of /cvsroot/phpbt/phpbt/docs/sgml
In directory usw-pr-cvs1:/tmp/cvs-serv20908/sgml
Modified Files:
phpbt.sgml
Added Files:
configuration.sgml
Log Message:
Started on configuration options
--- NEW FILE: configuration.sgml ---
<!-- -*- sgml -*- -->
<sect1 id="configuration">
<title>Configuration Options</title>
<abstract>
<para>The options listed in this section can be configured by the <filename>configure</filename> script and can be found in <filename>config.php</filename>.</para>
</abstract>
<variablelist>
<varlistentry>
<term>INSTALLPATH</term>
<listitem>
<para>Location on disk of the &phpbt; installation.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>INSTALLURL</term>
<listitem>
<para>URL that is the home of the installation.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>CVS_WEB</term>
<listitem>
<para>Location of your cvs web interface (see <function>format_comments()</function> in <filename>bug.php</filename>). This is for links to files in CVS generated from the comments attached to bugs.</para>
</listitem>
</varlistentry>
</variablelist>
</sect1>
<!-- Local Variables: -->
<!-- sgml-indent-step: 2 -->
<!-- sgml-indent-data: 2 -->
<!-- sgml-parent-document: "phpbt.sgml" -->
<!-- End: -->
Index: phpbt.sgml
===================================================================
RCS file: /cvsroot/phpbt/phpbt/docs/sgml/phpbt.sgml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- phpbt.sgml 2001/09/29 04:02:38 1.2
+++ phpbt.sgml 2001/09/29 18:35:54 1.3
@@ -7,6 +7,7 @@
<!-- Administrator's Guide -->
<!ENTITY installation SYSTEM "installation.sgml">
+<!ENTITY configuration SYSTEM "configuration.sgml">
<!-- Developer's Guide -->
<!ENTITY devstandards SYSTEM "devstandards.sgml">
@@ -36,6 +37,7 @@
</abstract>
&installation;
+ &configuration;
</chapter>
|
|
From: Benjamin C. <bc...@us...> - 2001-09-29 18:35:38
|
Update of /cvsroot/phpbt/phpbt/docs/sgml In directory usw-pr-cvs1:/tmp/cvs-serv20836/sgml Modified Files: docs.dsl Log Message: Paring down Index: docs.dsl =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/sgml/docs.dsl,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- docs.dsl 2001/09/27 13:40:20 1.1 +++ docs.dsl 2001/09/29 18:35:34 1.2 @@ -9,52 +9,24 @@ <style-specification use="docbook"> <style-specification-body> -;; Copyright (c) 2001 Jesse Goerz, NewbieDoc project. -;; http://sourceforge.net/projects/newbiedoc +;; Copyright (c) 2001 phpBugTracker Group ;; Permission is granted to copy, distribute and/or modify this ;; document under the terms of the GNU Free Documentation License, ;; Version 1.1 or any later version published by the Free Software ;; Foundation; with no Invariant Sections, with no Front-Cover ;; Texts, and with no Back-Cover Texts. A copy of the license can ;; be found at http://www.fsf.org/copyleft/fdl.html. - - -;; -;; $Log$ -;; Revision 1.1 2001/09/27 13:40:20 bcurtis -;; Starting the documentation book -;; -;; Revision 1.1 2001/05/05 08:37:08 jgoerz -;; stable: stylesheet for single html file -;; -;; Revision 1.2 2001/05/04 04:24:02 jesse -;; Added callouts, changed bgcolor for body and -;; verbatim environments. -;; -;; Revision 1.1 2001/04/24 09:09:54 jesse -;; Initial revision ;; +;; $Id$ - -(define %generate-article-toc% - ;; Should a Table of Contents be produced for Articles? - #t) - - (define (toc-depth nd) (if (string=? (gi nd) (normalize "book")) - ;; - ;; Docbook default is 1 level deep - ;; I don't understand "normalize book" but - ;; it doesn't seem to affect if we use - ;; articles. I changed it to 2 deep. - ;; 3 2)) -(define %generate-article-titlepage% +(define %generate-book-titlepage% ;; Should an article title page be produced? #t) @@ -70,26 +42,13 @@ (define %admon-graphics-path% - ;; Path to admonition graphics - ;; Sets the path, probably relative to the directory - ;; where the HTML files are created, to the admonition - ;; graphics. - ;; - ;; This needs to be "./images/" for tar distributed articles - ;; This needs to be "../images/" for tar distributed Newbiedoc book - ;; This needs to be "../images/" for individual articles on our website - "../images/") + "images/") (define %callout-graphics% - ;; If true, callouts are presented with graphics (e.g., reverse-video - ;; circled numbers instead of "(1)", "(2)", etc.). - ;; Default graphics are provided in the distribution. #t) (define %callout-graphics-path% - ;; Sets the path, probably relative to the directory where the HTML - ;; files are created, to the callout graphics. - "../images/callouts/") + "images/callouts/") (define %callout-graphics-number-limit% ;; If '%callout-graphics%' is true, graphics are used to represent @@ -186,6 +145,10 @@ ;;Default extension for filenames? (define %html-ext% ".html") + +(define %spacing-paras% + ;; Block-element spacing hack + #f) </style-specification-body> </style-specification> |
|
From: Benjamin C. <bc...@us...> - 2001-09-29 14:50:29
|
Update of /cvsroot/phpbt/phpbt
In directory usw-pr-cvs1:/tmp/cvs-serv10689
Modified Files:
CHANGELOG bug.php config.php
Log Message:
Added the ability to enter cvs:filename.ext or cvs:path/filename.ext:v.vv into the bug comments and have that linked to a CVS web interface.
Index: CHANGELOG
===================================================================
RCS file: /cvsroot/phpbt/phpbt/CHANGELOG,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- CHANGELOG 2001/09/28 13:33:09 1.16
+++ CHANGELOG 2001/09/29 14:50:26 1.17
@@ -1,3 +1,7 @@
+-- 0.4.0 --
+: Added the ability to enter cvs:filename.ext or cvs:path/filename.ext:v.vv
+ into the bug comments and have that linked to a CVS web interface.
+
-- 0.3.2 -- 28 Sep 2001
: Added patch and patch instructions for page.inc (in PHPlib).
: Tried to make the configure script a little more portable.
Index: bug.php
===================================================================
RCS file: /cvsroot/phpbt/phpbt/bug.php,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- bug.php 2001/09/24 12:57:03 1.46
+++ bug.php 2001/09/29 14:50:26 1.47
@@ -25,6 +25,24 @@
include 'include.php';
///
+/// Beautify the bug comments
+function format_comments($comments) {
+
+ // Set up the regex replacements
+ $patterns = array(
+ '/(bug)[[:space:]]*(#?)([0-9]+)/i', // matches bug #nn
+ '/cvs:([^\.\s:,\?!]+(\.[^\.\s:,\?!]+)*)(:)?(\d\.[\d\.]+)?([\W\s])?/i' // matches cvs:filename.php or cvs:filename.php:n.nn
+ );
+ $replacements = array(
+ "\1 <a href='$me?op=show&bugid=\3'>\2\3<\/a>", // internal link to bug
+ '<a href="'.CVS_WEB.'\1#rev\4" target="_new">\1</a>\5' // external link to cvs web interface
+ );
+
+ return preg_replace($patterns, $replacements,
+ stripslashes($comments));
+}
+
+///
/// Show the activity for a bug
function show_history($bugid) {
global $q, $t, $STRING;
@@ -136,7 +154,7 @@
'newpostedby' => $row['login'],
'newpostedon' => date(TIMEFORMAT, $row['created_date']).' on '.
date(DATEFORMAT, $row['created_date']),
- 'newcomments' => textwrap('+ '.stripslashes($row['comment_text']),72,"\n+ ")
+ 'newcomments' => textwrap('+ '.format_comments($row['comment_text']),72,"\n+ ")
));
// If this comment is the first additional comment after the creation of the
// bug then we need to grab the bug's description as the previous comment
@@ -147,7 +165,7 @@
$t->set_var(array(
'oldpostedby' => $by,
'oldpostedon' => date(TIMEFORMAT,$on).' on '.date(DATEFORMAT,$on),
- 'oldcomments' => textwrap(stripslashes($comments),72)
+ 'oldcomments' => textwrap(format_comments($comments),72)
));
} else {
$row = $q->grab();
@@ -155,7 +173,7 @@
'oldpostedby' => $row['login'],
'oldpostedon' => date(TIMEFORMAT,$row['created_date']).' on '.
date(DATEFORMAT,$row['created_date']),
- 'oldcomments' => textwrap(stripslashes($row['comment_text']),72)
+ 'oldcomments' => textwrap(format_comments($row['comment_text']),72)
));
}
$t->parse('cblock', 'commentblock', true);
@@ -314,7 +332,7 @@
$changedfields['resolution_id'] = $resolution_id;
}
if ($comments) {
- $comments = htmlspecialchars($comments);
+ $comments = $comments;
$q->query("insert into ".TBL_COMMENT." (comment_id, bug_id, comment_text, created_by, created_date)"
." values (".$q->nextid(TBL_COMMENT).", $bugid, '$comments', $u, $now)");
}
@@ -516,6 +534,7 @@
}
}
+ // Show the comments
$q->query('select comment_text, c.created_date, login'
.' from '.TBL_COMMENT.' c, '.TBL_AUTH_USER
." where bug_id = $bugid and c.created_by = user_id order by c.created_date");
@@ -525,8 +544,8 @@
while ($row = $q->grab()) {
$t->set_var(array(
'bgcolor' => (++$i % 2 == 0) ? '#dddddd' : '#ffffff',
- 'rdescription' => eregi_replace('(bug)[[:space:]]*(#?)([0-9]+)',
- "\\1 <a href='$me?op=show&bugid=\\3'>\\2\\3</a>",nl2br($row['comment_text'])),
+ 'rdescription' => nl2br(format_comments(
+ htmlspecialchars($row['comment_text']))),
'rreporter' => maskemail($row['login']),
'rcreateddate' => date(TIMEFORMAT,$row['created_date']).' on '.
date(DATEFORMAT,$row['created_date'])
@@ -590,4 +609,4 @@
page_close();
-?>
\ No newline at end of file
+?>
Index: config.php
===================================================================
RCS file: /cvsroot/phpbt/phpbt/config.php,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- config.php 2001/09/22 16:55:33 1.11
+++ config.php 2001/09/29 14:50:26 1.12
@@ -28,6 +28,9 @@
define ('PHPLIBPATH', ''); // If not in the include path
define ('JPGRAPH_PATH', ''); // If not in the include path
+// Location of your cvs web interface (see format_comments() in bug.php)
+define ('CVS_WEB', 'http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/phpbt/phpbt/');
+
// Database Config
define ('DB_TYPE', 'mysql'); //using PHPlib file naming
define ('DB_HOST', 'localhost');
|
|
From: Benjamin C. <bc...@us...> - 2001-09-29 04:03:58
|
Update of /cvsroot/phpbt/phpbt/docs/html In directory usw-pr-cvs1:/tmp/cvs-serv16114/html Removed Files: bug.html Log Message: That shouldn't be there --- bug.html DELETED --- |
|
From: Benjamin C. <bc...@us...> - 2001-09-29 04:02:41
|
Update of /cvsroot/phpbt/phpbt/docs/html In directory usw-pr-cvs1:/tmp/cvs-serv15929/html Modified Files: adminguide.html dependencies.html devguide.html docs.css index.html Log Message: Added the installation instructions Index: adminguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/adminguide.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- adminguide.html 2001/09/27 13:40:20 1.1 +++ adminguide.html 2001/09/29 04:02:38 1.2 @@ -90,6 +90,159 @@ ></P ></DIV ></BLOCKQUOTE +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="INSTALLATION" +>2.1. Installation Instructions</A +></H1 +><P +></P +><OL +TYPE="1" +><LI +><P +>Install PHPlib (<A +HREF="http://sourceforge.net/projects/phplib/" +TARGET="_top" +>http://sourceforge.net/projects/phplib</A +>) if it's not already installed. Note that with recent versions of PHP, PHPlib needs to be patched. Please do the following with the patch file, <TT +CLASS="FILENAME" +>page.inc.patch</TT +> in the distribution directory:</P +><TABLE +BORDER="0" +BGCOLOR="#EEEEEE" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +>cat page.inc.patch | patch -p0 -b /path/to/phplib/page.inc</PRE +></TD +></TR +></TABLE +><P +>Make sure you replace <TT +CLASS="FILENAME" +>/path/to/phplib</TT +> with the actual path to the installation of PHPlib. On windows systems you can edit <TT +CLASS="FILENAME" +>page.inc</TT +> and change line 67 from <TT +CLASS="COMPUTEROUTPUT" +>if (isset($user)) {</TT +> to <TT +CLASS="COMPUTEROUTPUT" +>if (isset($user) && $user) {</TT +>.</P +></LI +><LI +><P +>Copy the directory tree from the tarball to a location suitable for serving web pages.</P +></LI +><LI +><P +>Run the <TT +CLASS="FILENAME" +>configure</TT +> script. This will change <TT +CLASS="FILENAME" +>config.php</TT +> (creating a backup) and will run <TT +CLASS="FILENAME" +>configure_db</TT +>, which will create <TT +CLASS="FILENAME" +>createdb.sql</TT +>. </P +><P +><SPAN +><I +CLASS="EMPHASIS" +>-- or --</I +></SPAN +></P +><P +>Configure manually: + <P +></P +><OL +TYPE="a" +><LI +><P +>Edit the constants in <TT +CLASS="FILENAME" +>config.php</TT +>.</P +></LI +><LI +><P +>Run <TT +CLASS="FILENAME" +>configure_db</TT +> to get <TT +CLASS="FILENAME" +>createdb.sql</TT +>.</P +></LI +></OL +> + </P +></LI +><LI +><P +>If you want to use JpGraph (<A +HREF="http://www.aditus.nu/jpgraph/" +TARGET="_top" +>http://www.aditus.nu/jpgraph</A +>) to display the bug summary info, you will also need to edit <TT +CLASS="FILENAME" +>jpgraph.php</TT +> from the JpGraph disribution.</P +></LI +><LI +><P +>Edit <TT +CLASS="FILENAME" +>createdb.sql</TT +>, changing the admin info in the database insert. You can search on the text <TT +CLASS="COMPUTEROUTPUT" +>ad...@ex...</TT +> (around line 240).</P +></LI +><LI +><P +>Use <TT +CLASS="FILENAME" +>createdb.sql</TT +> to create your database. With MySQL it can be done as follows: + </P +><TABLE +BORDER="0" +BGCOLOR="#EEEEEE" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +>mysql -h <db host> -u <username> -p<yourpassword> < createdb.sql</PRE +></TD +></TR +></TABLE +></LI +><LI +><P +>Browse on over to the installation, choose Admin tools, login with the info you put in the database creation script, and create your first project.</P +></LI +><LI +><P +>Start reporting bugs.</P +></LI +></OL +></DIV ></DIV ><DIV CLASS="NAVFOOTER" Index: dependencies.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/dependencies.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- dependencies.html 2001/09/27 13:40:20 1.1 +++ dependencies.html 2001/09/29 04:02:38 1.2 @@ -77,7 +77,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN79" +NAME="AEN127" ></A ><P ></P Index: devguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/devguide.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- devguide.html 2001/09/27 13:40:20 1.1 +++ devguide.html 2001/09/29 04:02:38 1.2 @@ -113,7 +113,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN16" +NAME="AEN64" ></A ><P ></P @@ -140,7 +140,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN21" +NAME="AEN69" ></A ><P ></P Index: docs.css =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/docs.css,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- docs.css 2001/09/27 13:40:20 1.1 +++ docs.css 2001/09/29 04:02:38 1.2 @@ -6,8 +6,5 @@ font-family: "Verdana","Arial","Helvetica","MS Sans Serif","Sans-Serif"; text-align: right; background-color: #FFDDBB; - padding: .1em; } - -.PROGRAMLISTING { - border: 1px black solid; + padding: .1em; } Index: index.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/index.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- index.html 2001/09/27 13:40:20 1.1 +++ index.html 2001/09/29 04:02:38 1.2 @@ -64,6 +64,15 @@ HREF="adminguide.html" >Administrator's Guide</A ></DT +><DD +><DL +><DT +>2.1. <A +HREF="adminguide.html#INSTALLATION" +>Installation Instructions</A +></DT +></DL +></DD ><DT >3. <A HREF="devguide.html" |
|
From: Benjamin C. <bc...@us...> - 2001-09-29 04:02:41
|
Update of /cvsroot/phpbt/phpbt/docs/sgml
In directory usw-pr-cvs1:/tmp/cvs-serv15929/sgml
Modified Files:
phpbt.sgml
Added Files:
installation.sgml
Log Message:
Added the installation instructions
--- NEW FILE: installation.sgml ---
<!-- -*- sgml -*- -->
<sect1 id="installation">
<title>Installation Instructions</title>
<orderedlist>
<listitem>
<para>Install PHPlib (<ulink url="http://sourceforge.net/projects/phplib/">http://sourceforge.net/projects/phplib</ulink>) if it's not already installed. Note that with recent versions of PHP, PHPlib needs to be patched. Please do the following with the patch file, <filename>page.inc.patch</filename> in the distribution directory:</para>
<screen>cat page.inc.patch | patch -p0 -b /path/to/phplib/page.inc</screen>
<para>Make sure you replace <filename>/path/to/phplib</filename> with the actual path to the installation of PHPlib. On windows systems you can edit <filename>page.inc</filename> and change line 67 from <computeroutput>if (isset($user)) {</computeroutput> to <computeroutput>if (isset($user) && $user) {</computeroutput>.</para>
</listitem>
<listitem>
<para>Copy the directory tree from the tarball to a location suitable for serving web pages.</para>
</listitem>
<listitem>
<para>Run the <filename>configure</filename> script. This will change <filename>config.php</filename> (creating a backup) and will run <filename>configure_db</filename>, which will create <filename>createdb.sql</filename>. </para>
<para><emphasis>-- or --</emphasis></para>
<para>Configure manually:
<orderedlist>
<listitem>
<para>Edit the constants in <filename>config.php</filename>.</para>
</listitem>
<listitem>
<para>Run <filename>configure_db</filename> to get <filename>createdb.sql</filename>.</para>
</listitem>
</orderedlist>
</para>
</listitem>
<listitem>
<para>If you want to use JpGraph (<ulink url="http://www.aditus.nu/jpgraph/">http://www.aditus.nu/jpgraph</ulink>) to display the bug summary info, you will also need to edit <filename>jpgraph.php</filename> from the JpGraph disribution.</para>
</listitem>
<listitem>
<para>Edit <filename>createdb.sql</filename>, changing the admin info in the database insert. You can search on the text <computeroutput>ad...@ex...</computeroutput> (around line 240).</para>
</listitem>
<listitem>
<para>Use <filename>createdb.sql</filename> to create your database. With MySQL it can be done as follows:
</para>
<screen>mysql -h <db host> -u <username> -p<yourpassword> < createdb.sql</screen>
</listitem>
<listitem>
<para>Browse on over to the installation, choose Admin tools, login with the info you put in the database creation script, and create your first project.</para>
</listitem>
<listitem>
<para>Start reporting bugs.</para>
</listitem>
</orderedlist>
</sect1>
<!-- Local Variables: -->
<!-- sgml-indent-step: 2 -->
<!-- sgml-indent-data: 2 -->
<!-- sgml-parent-document: "phpbt.sgml" -->
<!-- End: -->
Index: phpbt.sgml
===================================================================
RCS file: /cvsroot/phpbt/phpbt/docs/sgml/phpbt.sgml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- phpbt.sgml 2001/09/27 13:40:20 1.1
+++ phpbt.sgml 2001/09/29 04:02:38 1.2
@@ -5,6 +5,9 @@
<!-- Shortcuts -->
<!ENTITY phpbt "phpBugTracker">
+<!-- Administrator's Guide -->
+<!ENTITY installation SYSTEM "installation.sgml">
+
<!-- Developer's Guide -->
<!ENTITY devstandards SYSTEM "devstandards.sgml">
<!ENTITY dependencies SYSTEM "dependencies.sgml">
@@ -31,6 +34,9 @@
<abstract>
<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>
+
+ &installation;
+
</chapter>
<chapter id="devguide">
|
|
From: Benjamin C. <bc...@us...> - 2001-09-28 13:33:14
|
Update of /cvsroot/phpbt/phpbt In directory usw-pr-cvs1:/tmp/cvs-serv21843 Modified Files: CHANGELOG TODO Log Message: Updated for 0.3.2 Index: CHANGELOG =================================================================== RCS file: /cvsroot/phpbt/phpbt/CHANGELOG,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- CHANGELOG 2001/09/18 03:51:03 1.15 +++ CHANGELOG 2001/09/28 13:33:09 1.16 @@ -1,3 +1,9 @@ +-- 0.3.2 -- 28 Sep 2001 +: Added patch and patch instructions for page.inc (in PHPlib). +: Tried to make the configure script a little more portable. +: Users can now add CCs to bug change notifications. +: Fixed some bugs with bug updating. + -- 0.3.1 -- 17 Sep 2001 : Fixed the perm and group checks. : Fixed a bug when selecting an OS in the bug query. Index: TODO =================================================================== RCS file: /cvsroot/phpbt/phpbt/TODO,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- TODO 2001/09/15 17:17:10 1.7 +++ TODO 2001/09/28 13:33:09 1.8 @@ -1,6 +1,5 @@ Bugs: - Create bugs via email -- Add CCs to bugs New Account: - Allow the admin to control whether users can create new accounts |
|
From: Benjamin C. <bc...@us...> - 2001-09-28 13:25:43
|
Update of /cvsroot/phpbt/phpbt
In directory usw-pr-cvs1:/tmp/cvs-serv19948
Modified Files:
INSTALL
Added Files:
page.inc.patch
Log Message:
Added patch and patch instructions for page.inc
--- NEW FILE: page.inc.patch ---
--- page.inc Fri Sep 28 06:23:14 2001
+++ page.inc Fri Sep 28 06:22:56 2001
@@ -64,7 +64,7 @@
if (isset($sess)) {
$sess->freeze();
- if (isset($user)) {
+ if (isset($user) && $user) {
$user->freeze();
}
}
Index: INSTALL
===================================================================
RCS file: /cvsroot/phpbt/phpbt/INSTALL,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- INSTALL 2001/09/15 16:56:12 1.8
+++ INSTALL 2001/09/28 13:25:40 1.9
@@ -1,12 +1,18 @@
Ok, here's the quick and dirty install instructions:
-1. Edit the database creation script, changing the info for the Admin user.
-2. Run the database creation script (currently only MySQL) by running
- "mysql -u <user> -p<password> < createdb.sql"
1. Install PHPlib (http://sourceforge.net/projects/phplib/) if it's not already
- installed.
+ installed. Note that with recent versions of PHP, PHPlib needs to be
+ patched. Please do the following with the patch file in this directory:
+ cat page.inc.patch | patch -p0 -b /path/to/phplib/page.inc
+
+ Make sure you replace /path/to/phplib with the actual path to the installation
+ of phplib. On windows systems you can edit page.inc and change line 67
+ from 'if (isset($user)) {' to 'if (isset($user) && $user) {' (without the
+ quotes).
+
2. Copy the directory tree from the tarball to a location suitable for serving
web pages.
+
3. Run the configure script. This will change config.php (creating a backup)
and run configure_db which creates createdb.sql.
@@ -15,13 +21,18 @@
3. Configure manually.
a. Edit the constants in config.php.
b. Edit the variables in configure_db and run it to get createdb.sql.
+
4. If you want to use jpgraph (http://www.aditus.nu/jpgraph/)
to display the bug summary info, you will also need to edit
jpgraph.php from the jpgraph disribution.
+
5. Edit createdb.sql, changing the admin info in the database insert. You can
search on the text ad...@ex... (around line 240).
+
6. Use createdb.sql to create your database. With MySQL it can be done like
mysql -h <db host> -u <username> -p<yourpassword> < createdb.sql
+
7. Browse on over to the installation, choose Admin tools, login with the info
you put in the database creation script, and create your first project.
+
8. Start reporting bugs
|
|
From: Benjamin C. <bc...@us...> - 2001-09-27 13:40:24
|
Update of /cvsroot/phpbt/phpbt/docs/sgml
In directory usw-pr-cvs1:/tmp/cvs-serv18455/sgml
Modified Files:
devstandards.sgml
Added Files:
dependencies.sgml docs.dsl phpbt.sgml template.sgml
Log Message:
Starting the documentation book
--- NEW FILE: dependencies.sgml ---
<!-- -*- sgml -*- -->
<sect1 id="dependencies">
<title>Dependencies</title>
<abstract>
<para>&phpbt; requires one external package, PHPlib, and can optionally use JpGraph.</para>
</abstract>
<sect2 id="dep-phplib">
<title>PHPlib</title>
<para>PHPlib can be found at <ulink url="http://phplib.sourceforge.net/">http://phplib.sourceforge.net</ulink>. It provides the database abstraction layer, html templates, and session and authentication management.</para>
</sect2>
</sect1>
<!-- Local Variables: -->
<!-- sgml-indent-step: 2 -->
<!-- sgml-indent-data: 2 -->
<!-- sgml-parent-document: "phpbt.sgml" -->
<!-- End: -->
--- NEW FILE: docs.dsl ---
<!DOCTYPE style-sheet PUBLIC "-//James Clark//DTD DSSSL Style
Sheet//EN" [
<!ENTITY docbook.dsl PUBLIC "-//Norman Walsh//DOCUMENT DocBook HTML
Stylesheet//EN" CDATA dsssl>
]>
<style-sheet>
<style-specification use="docbook">
<style-specification-body>
;; Copyright (c) 2001 Jesse Goerz, NewbieDoc project.
;; http://sourceforge.net/projects/newbiedoc
;; Permission is granted to copy, distribute and/or modify this
;; document under the terms of the GNU Free Documentation License,
;; Version 1.1 or any later version published by the Free Software
;; Foundation; with no Invariant Sections, with no Front-Cover
;; Texts, and with no Back-Cover Texts. A copy of the license can
;; be found at http://www.fsf.org/copyleft/fdl.html.
;;
;; $Log: docs.dsl,v $
;; Revision 1.1 2001/09/27 13:40:20 bcurtis
;; Starting the documentation book
;;
;; Revision 1.1 2001/05/05 08:37:08 jgoerz
;; stable: stylesheet for single html file
;;
;; Revision 1.2 2001/05/04 04:24:02 jesse
;; Added callouts, changed bgcolor for body and
;; verbatim environments.
;;
;; Revision 1.1 2001/04/24 09:09:54 jesse
;; Initial revision
;;
(define %generate-article-toc%
;; Should a Table of Contents be produced for Articles?
#t)
(define (toc-depth nd)
(if (string=? (gi nd) (normalize "book"))
;;
;; Docbook default is 1 level deep
;; I don't understand "normalize book" but
;; it doesn't seem to affect if we use
;; articles. I changed it to 2 deep.
;;
3
2))
(define %generate-article-titlepage%
;; Should an article title page be produced?
#t)
(define %titlepage-in-info-order%
;; Place elements on title page in document order?
#f)
(define %admon-graphics%
;; Use graphics in admonitions?
#t)
(define %admon-graphics-path%
;; Path to admonition graphics
;; Sets the path, probably relative to the directory
;; where the HTML files are created, to the admonition
;; graphics.
;;
;; This needs to be "./images/" for tar distributed articles
;; This needs to be "../images/" for tar distributed Newbiedoc book
;; This needs to be "../images/" for individual articles on our website
"../images/")
(define %callout-graphics%
;; If true, callouts are presented with graphics (e.g., reverse-video
;; circled numbers instead of "(1)", "(2)", etc.).
;; Default graphics are provided in the distribution.
#t)
(define %callout-graphics-path%
;; Sets the path, probably relative to the directory where the HTML
;; files are created, to the callout graphics.
"../images/callouts/")
(define %callout-graphics-number-limit%
;; If '%callout-graphics%' is true, graphics are used to represent
;; callout numbers. The value of '%callout-graphics-number-limit%' is
;; the largest number for which a graphic exists. If the callout number
;; exceeds this limit, the default presentation "(nnn)" will always
;; be used.
10)
(define ($admon-graphic$ #!optional (nd (current-node)))
;; Admonition graphic file
;; Given an admonition node, returns the name of the
;; graphic that should be used for that admonition.
(cond ((equal? (gi nd) (normalize "tip"))
(string-append %admon-graphics-path% "tip.gif"))
((equal? (gi nd) (normalize "note"))
(string-append %admon-graphics-path% "note.gif"))
((equal? (gi nd) (normalize "important"))
(string-append %admon-graphics-path% "important.gif"))
((equal? (gi nd) (normalize "caution"))
(string-append %admon-graphics-path% "caution.gif"))
((equal? (gi nd) (normalize "warning"))
(string-append %admon-graphics-path% "warning.gif"))
(else (error (string-append (gi nd) " is not an admonition.")))))
(define ($admon-graphic-width$ #!optional (nd (current-node)))
"25")
(define %number-programlisting-lines%
;; Enumerate lines in a 'ProgramListing'?
#f)
(define %linenumber-length%
;; Width of line numbers in enumerated environments
;; Line numbers will be padded to %linenumber-length% characters.
0)
(define %linenumber-mod%
;; Controls line-number frequency in enumerated environments.
;; Every %linenumber-mod% line will be enumerated.
1)
(define %linenumber-padchar%
;; Pad character in line numbers
;; Line numbers will be padded (on the left) with %linenumber-padchar%
" ")
(define %shade-verbatim%
;; Should verbatim environments be shaded?
#t)
(define ($shade-verbatim-attr$)
;; Attributes used to create a shaded verbatim environment.
(list
(list "BORDER" "0")
(list "BGCOLOR" "#EEEEEE")
(list "WIDTH" ($table-width$))))
(define %section-autolabel%
;; Are sections enumerated?
#t)
(define %body-attr%
;; What attributes should be hung off of BODY?
(list
(list "BGCOLOR" "#FFFFFF")
(list "TEXT" "#000000")
(list "LINK" "#0000FF")
(list "VLINK" "#800080")
(list "ALINK" "#FF0000")))
(define %stylesheet%
;; Name of the stylesheet to use
"docs.css")
(define %stylesheet-type%
;; The type of the stylesheet to use
"text/css")
(define %html40%
;; Generate HTML 4.0
#t)
(define %use-id-as-filename%
;; Use ID attributes as name for component HTML files?
#t)
;;Default extension for filenames?
(define %html-ext%
".html")
</style-specification-body>
</style-specification>
<external-specification id="docbook" document="docbook.dsl">
</style-sheet>
--- NEW FILE: phpbt.sgml ---
<!-- -*- sgml -*- -->
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN"
[
<!-- Shortcuts -->
<!ENTITY phpbt "phpBugTracker">
<!-- Developer's Guide -->
<!ENTITY devstandards SYSTEM "devstandards.sgml">
<!ENTITY dependencies SYSTEM "dependencies.sgml">
]>
<book id="index">
<bookinfo>
<title>&phpbt;</title>
<abstract>
<para>&phpbt; is a web-based bug reporting and tracking system. It allows development teams to manage the testing and debugging segments of the development cycle.</para>
</abstract>
</bookinfo>
<chapter id="userguide">
<title>User's Guide</title>
<abstract>
<para>Currently all interactions with &phpbt; are done via the web interface. Users can submit bugs, communicate with developers and testers about bugs, and search through the bug database.</para>
</abstract>
</chapter>
<chapter id="adminguide">
<title>Administrator's Guide</title>
<abstract>
<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>
</chapter>
<chapter id="devguide">
<title>Developer's Guide</title>
<abstract>
<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>
&devstandards;
&dependencies;
</chapter>
</book>
<!-- Local Variables: -->
<!-- sgml-indent-step: 2 -->
<!-- sgml-indent-data: 2 -->
<!-- End: -->
--- NEW FILE: template.sgml ---
<!-- -*- sgml -*- -->
<sect1 id="uniquesectionid">
<title>Example Documentation Section</title>
<abstract>
<para>Summary of what this section is about.</para>
</abstract>
<sect2 id="subsectid">
<title>Subsection title</title>
<para>Subsection content</para>
<para>More content</para>
</sect2>
</sect1>
<!-- Local Variables: -->
<!-- sgml-indent-step: 2 -->
<!-- sgml-indent-data: 2 -->
<!-- sgml-parent-document: "phpbt.sgml" -->
<!-- End: -->
Index: devstandards.sgml
===================================================================
RCS file: /cvsroot/phpbt/phpbt/docs/sgml/devstandards.sgml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- devstandards.sgml 2001/09/25 04:13:10 1.4
+++ devstandards.sgml 2001/09/27 13:40:20 1.5
@@ -1,31 +1,24 @@
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN"
-
-[
-<!ENTITY phpbt "phpBugTracker">
-]>
-
-<article id="index" xreflabel="Development Standards">
- <articleinfo>
- <title>Development Standards</title>
- <abstract>
- <para>
- This document will contain the coding and process standards to be
- followed by the developers working on &phpbt;.
- </para>
- </abstract>
- </articleinfo>
+<!-- -*- sgml -*- -->
+<sect1 id="devstandards">
+ <title>Development Standards</title>
+ <abstract>
+ <para>
+ This section details the coding and process standards to be
+ followed by the developers working on &phpbt;.
+ </para>
+ </abstract>
- <sect1 id="devstandards-code" xreflabel="Coding Standards">
+ <sect2 id="devstandards-code" xreflabel="Coding Standards">
<title>Coding Standards</title>
- <sect2 id="devstandards-indenting" xreflabel="Indenting">
+ <sect3 id="devstandards-indenting" xreflabel="Indenting">
<title>Indenting</title>
<para>
Use an indent of one tab per indent.
</para>
- </sect2>
+ </sect3>
- <sect2 id="devstandards-control" xreflabel="Control Structures">
+ <sect3 id="devstandards-control" xreflabel="Control Structures">
<title>Control Structures</title>
<para>
These include if, for, while, switch, etc. Here is an example if
@@ -53,9 +46,9 @@
readability and decreases the likelihood of logic errors being
introduced when new lines are added.
</para>
- </sect2>
+ </sect3>
- <sect2 id="devstandards-funccalls" xreflabel="Function Calls">
+ <sect3 id="devstandards-funccalls" xreflabel="Function Calls">
<title>Function Calls</title>
<para>
Functions should be called with no spaces between the function name,
@@ -72,9 +65,9 @@
As displayed above, there should be one space on either side of an
equals sign used to assign the return value of a function to a variable.
</para>
- </sect2>
+ </sect3>
- <sect2 id="devstandards-funcdefs" xreflabel="Function Definitions">
+ <sect3 id="devstandards-funcdefs" xreflabel="Function Definitions">
<title>Function Definitions</title>
<para>
Function definitions follow the format of function calls, with the
@@ -120,9 +113,9 @@
}
</programlisting>
- </sect2>
+ </sect3>
- <sect2 id="devstandards-comments" xreflabel="Comments">
+ <sect3 id="devstandards-comments" xreflabel="Comments">
<title>Comments</title>
<para>
Non-documentation comments are strongly encouraged. A general rule of
@@ -130,9 +123,9 @@
want to try and describe that", you need to comment it before you
forget how it works.
</para>
- </sect2>
+ </sect3>
- <sect2 id="devstandards-including" xreflabel="Including Code">
+ <sect3 id="devstandards-including" xreflabel="Including Code">
<title>Including Code</title>
<para>
Anywhere you are unconditionally including a class file, use
@@ -146,31 +139,31 @@
with <function>require_once()</function> will not be included again by
<function>include_once()</function>.
</para>
- </sect2>
+ </sect3>
- <sect2 id="devstandards-phptags" xreflabel="PHP Tags">
+ <sect3 id="devstandards-phptags" xreflabel="PHP Tags">
<title>PHP Tags</title>
<para>
Always use <computeroutput><?php ?></computeroutput>
to delimit PHP code, not the <computeroutput><? ?></computeroutput>
shorthand.
</para>
- </sect2>
+ </sect3>
- <sect2 id="devstandards-constants" xreflabel="Naming Constants">
+ <sect3 id="devstandards-constants" xreflabel="Naming Constants">
<title>Naming Constants</title>
<para>
Constants should always be uppercase, with underscores to separate
words.
</para>
- </sect2>
+ </sect3>
- </sect1>
+ </sect2>
- <sect1 id="otherconventions" xreflabel="Other Conventions">
+ <sect2 id="otherconventions" xreflabel="Other Conventions">
<title>Other Conventions</title>
- <sect2 id="devstandards-filenaming" xreflabel="File Naming">
+ <sect3 id="devstandards-filenaming" xreflabel="File Naming">
<title>File Naming</title>
<para>
File names should be all lowercase and contain no spaces. HTML files
@@ -179,13 +172,19 @@
template files should match the name of the PHP file that will be using
it, e. g., <filename>index.html</filename> would be the template file
for <filename>index.php</filename>. Where one PHP file uses more than one
- templates, the templates should be similarly named:
+ template, the templates should be similarly named:
<filename>user.php</filename> could use
<filename>userlist.html</filename> and <filename>userform.html</filename>
for a list of users and editing a user, respectively.
</para>
- </sect2>
+ </sect3>
+
+ </sect2>
- </sect1>
+</sect1>
-</article>
+<!-- Local Variables: -->
+<!-- sgml-indent-step: 2 -->
+<!-- sgml-indent-data: 2 -->
+<!-- sgml-parent-document: "phpbt.sgml" -->
+<!-- End: -->
|
|
From: Benjamin C. <bc...@us...> - 2001-09-27 13:40:24
|
Update of /cvsroot/phpbt/phpbt/docs/html
In directory usw-pr-cvs1:/tmp/cvs-serv18455/html
Added Files:
adminguide.html bug.html dependencies.html devguide.html
docs.css index.html userguide.html
Log Message:
Starting the documentation book
--- NEW FILE: adminguide.html ---
<HTML
><HEAD
><TITLE
>Administrator's Guide</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.72
"><LINK
REL="HOME"
TITLE="phpBugTracker"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="User's Guide"
HREF="userguide.html"><LINK
REL="NEXT"
TITLE="Developer's Guide"
HREF="devguide.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="docs.css"></HEAD
><BODY
CLASS="CHAPTER"
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="userguide.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="devguide.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="ADMINGUIDE"
>Chapter 2. Administrator's Guide</A
></H1
><BLOCKQUOTE
CLASS="ABSTRACT"
><DIV
CLASS="ABSTRACT"
><A
NAME="AEN12"
></A
><P
></P
><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
><P
></P
></DIV
></BLOCKQUOTE
></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="userguide.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="devguide.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>User's Guide</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
> </TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Developer's Guide</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
--- NEW FILE: bug.html ---
<table>
<title>Schema for table bug</title>
<thead>
<row>
<entry>Field</entry>
<entry>Type</entry>
<entry>Null</entry>
<entry>Key</entry>
<entry>Default</entry>
<entry>Exrowa</entry>
</row>
</thead>
<row>
<entry>bug_id</entry>
<entry>int(10) unsigned</entry>
<entry>
</entry>
<entry>PRI</entry>
<entry>0</entry>
<entry>
</entry>
</row>
<row>
<entry>title</entry>
<entry>varchar(100)</entry>
<entry>
</entry>
<entry>
</entry>
<entry>
</entry>
<entry>
</entry>
</row>
<row>
<entry>description</entry>
<entry>text</entry>
<entry>
</entry>
<entry>
</entry>
<entry>
</entry>
<entry>
</entry>
</row>
<row>
<entry>url</entry>
<entry>varchar(255)</entry>
<entry>
</entry>
<entry>
</entry>
<entry>
</entry>
<entry>
</entry>
</row>
<row>
<entry>severity_id</entry>
<entry>tinyint(3) unsigned</entry>
<entry>
</entry>
<entry>
</entry>
<entry>0</entry>
<entry>
</entry>
</row>
<row>
<entry>priority</entry>
<entry>tinyint(3) unsigned</entry>
<entry>
</entry>
<entry>
</entry>
<entry>0</entry>
<entry>
</entry>
</row>
<row>
<entry>status_id</entry>
<entry>tinyint(3) unsigned</entry>
<entry>
</entry>
<entry>
</entry>
<entry>0</entry>
<entry>
</entry>
</row>
<row>
<entry>resolution_id</entry>
<entry>tinyint(3) unsigned</entry>
<entry>
</entry>
<entry>
</entry>
<entry>0</entry>
<entry>
</entry>
</row>
<row>
<entry>assigned_to</entry>
<entry>int(10) unsigned</entry>
<entry>
</entry>
<entry>
</entry>
<entry>0</entry>
<entry>
</entry>
</row>
<row>
<entry>created_by</entry>
<entry>int(10) unsigned</entry>
<entry>
</entry>
<entry>
</entry>
<entry>0</entry>
<entry>
</entry>
</row>
<row>
<entry>created_date</entry>
<entry>bigint(20) unsigned</entry>
<entry>
</entry>
<entry>
</entry>
<entry>0</entry>
<entry>
</entry>
</row>
<row>
<entry>last_modified_by</entry>
<entry>int(10) unsigned</entry>
<entry>
</entry>
<entry>
</entry>
<entry>0</entry>
<entry>
</entry>
</row>
<row>
<entry>last_modified_date</entry>
<entry>bigint(20) unsigned</entry>
<entry>
</entry>
<entry>
</entry>
<entry>0</entry>
<entry>
</entry>
</row>
<row>
<entry>project_id</entry>
<entry>int(10) unsigned</entry>
<entry>
</entry>
<entry>
</entry>
<entry>0</entry>
<entry>
</entry>
</row>
<row>
<entry>version_id</entry>
<entry>int(10) unsigned</entry>
<entry>
</entry>
<entry>
</entry>
<entry>0</entry>
<entry>
</entry>
</row>
<row>
<entry>component_id</entry>
<entry>int(10) unsigned</entry>
<entry>
</entry>
<entry>
</entry>
<entry>0</entry>
<entry>
</entry>
</row>
<row>
<entry>os_id</entry>
<entry>tinyint(3) unsigned</entry>
<entry>
</entry>
<entry>
</entry>
<entry>0</entry>
<entry>
</entry>
</row>
<row>
<entry>browser_srowing</entry>
<entry>varchar(255)</entry>
<entry>
</entry>
<entry>
</entry>
<entry>
</entry>
<entry>
</entry>
</row>
<row>
<entry>close_date</entry>
<entry>bigint(20) unsigned</entry>
<entry>
</entry>
<entry>
</entry>
<entry>0</entry>
<entry>
</entry>
</row>
</table>
--- NEW FILE: dependencies.html ---
<HTML
><HEAD
><TITLE
>Dependencies</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.72
"><LINK
REL="HOME"
TITLE="phpBugTracker"
HREF="index.html"><LINK
REL="UP"
TITLE="Developer's Guide"
HREF="devguide.html"><LINK
REL="PREVIOUS"
TITLE="Developer's Guide"
HREF="devguide.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="devguide.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 3. Developer's Guide</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
> </TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="DEPENDENCIES"
>3.2. Dependencies</A
></H1
><BLOCKQUOTE
CLASS="ABSTRACT"
><DIV
CLASS="ABSTRACT"
><A
NAME="AEN79"
></A
><P
></P
><P
>phpBugTracker requires one external package, PHPlib, and can optionally use JpGraph.</P
><P
></P
></DIV
></BLOCKQUOTE
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="DEP-PHPLIB"
>3.2.1. PHPlib</A
></H2
><P
>PHPlib can be found at <A
HREF="http://phplib.sourceforge.net/"
TARGET="_top"
>http://phplib.sourceforge.net</A
>. It provides the database abstraction layer, html templates, and session and authentication management.</P
></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="devguide.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"
> </TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Developer's Guide</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="devguide.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
> </TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
--- NEW FILE: devguide.html ---
<HTML
><HEAD
><TITLE
>Developer's Guide</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.72
"><LINK
REL="HOME"
TITLE="phpBugTracker"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Administrator's Guide"
HREF="adminguide.html"><LINK
REL="NEXT"
TITLE="Dependencies"
HREF="dependencies.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="docs.css"></HEAD
><BODY
CLASS="CHAPTER"
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"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="dependencies.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="DEVGUIDE"
>Chapter 3. Developer's Guide</A
></H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>3.1. <A
HREF="devguide.html#DEVSTANDARDS"
>Development Standards</A
></DT
><DD
><DL
><DT
>3.1.1. <A
HREF="devguide.html#DEVSTANDARDS-CODE"
>Coding Standards</A
></DT
><DT
>3.1.2. <A
HREF="devguide.html#OTHERCONVENTIONS"
>Other Conventions</A
></DT
></DL
></DD
><DT
>3.2. <A
HREF="dependencies.html"
>Dependencies</A
></DT
></DL
></DIV
><BLOCKQUOTE
CLASS="ABSTRACT"
><DIV
CLASS="ABSTRACT"
><A
NAME="AEN16"
></A
><P
></P
><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"
>http://www.sourceforge.net/projects/phpbt</A
>, or to simply submit patches, bug reports, or feature requests.</P
><P
></P
></DIV
></BLOCKQUOTE
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="DEVSTANDARDS"
>3.1. Development Standards</A
></H1
><BLOCKQUOTE
CLASS="ABSTRACT"
><DIV
CLASS="ABSTRACT"
><A
NAME="AEN21"
></A
><P
></P
><P
> This section details the coding and process standards to be
followed by the developers working on phpBugTracker.
</P
><P
></P
></DIV
></BLOCKQUOTE
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="DEVSTANDARDS-CODE"
>3.1.1. Coding Standards</A
></H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="DEVSTANDARDS-INDENTING"
>3.1.1.1. Indenting</A
></H3
><P
> Use an indent of one tab per indent.
</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="DEVSTANDARDS-CONTROL"
>3.1.1.2. Control Structures</A
></H3
><P
> These include if, for, while, switch, etc. Here is an example if
statement, since it is the most complicated of them:
</P
><TABLE
BORDER="0"
BGCOLOR="#EEEEEE"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
> if ((condition1) || (condition2)) {
action1;
} elseif ((condition3) && (condition4)) {
action2;
} else {
defaultaction;
}
</PRE
></TD
></TR
></TABLE
><P
> Control statements should have one space between the control keyword
and opening parenthesis, to distinguish them from function calls.
</P
><P
> You are strongly encouraged to always use curly braces even in
situations where they are technically optional. Having them increases
readability and decreases the likelihood of logic errors being
introduced when new lines are added.
</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="DEVSTANDARDS-FUNCCALLS"
>3.1.1.3. Function Calls</A
></H3
><P
> Functions should be called with no spaces between the function name,
the opening parenthesis, and the first parameter; spaces between
commas and each parameter, and no space between the last parameter,
the closing parenthesis, and the semicolon. Here's an example:
</P
><TABLE
BORDER="0"
BGCOLOR="#EEEEEE"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
> $var = foo($bar, $baz, $quux);
</PRE
></TD
></TR
></TABLE
><P
> As displayed above, there should be one space on either side of an
equals sign used to assign the return value of a function to a variable.
</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="DEVSTANDARDS-FUNCDEFS"
>3.1.1.4. Function Definitions</A
></H3
><P
> Function definitions follow the format of function calls, with the
opening brace at the end of the line of the function declaration. The
global variable list (if used) should be placed on the line immediately
following the opening brace, with a blank line between the variable
list and the first line of function code. If the global variable list
is not neccessary, include a blank line between the opening brace and
the first line of function code.
</P
><TABLE
BORDER="0"
BGCOLOR="#EEEEEE"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
> function fooFunction($arg1, $arg2 = '') {
global $foo1, $foo2;
if (condition) {
statement;
}
return $val;
}
</PRE
></TD
></TR
></TABLE
><P
> Arguments with default values go at the end of the argument list.
Always attempt to return a meaningful value from a function if one is
appropriate. Here is a slightly longer example:
</P
><TABLE
BORDER="0"
BGCOLOR="#EEEEEE"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
> function connect(&$dsn, $persistent = false) {
if (is_array($dsn)) {
$dsninfo = &$dsn;
} else {
$dsninfo = DB::parseDSN($dsn);
}
if (!$dsninfo || !$dsninfo['phptype']) {
return $this->raiseError();
}
return true;
}
</PRE
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="DEVSTANDARDS-COMMENTS"
>3.1.1.5. Comments</A
></H3
><P
> Non-documentation comments are strongly encouraged. A general rule of
thumb is that if you look at a section of code and think "Wow, I don't
want to try and describe that", you need to comment it before you
forget how it works.
</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="DEVSTANDARDS-INCLUDING"
>3.1.1.6. Including Code</A
></H3
><P
> Anywhere you are unconditionally including a class file, use
<A
HREF="http://php.net/manual/en/html/function.require-once.html"
TARGET="_top"
> <TT
CLASS="FUNCTION"
>require_once()</TT
></A
>. Anywhere you are
conditionally including a class file (for example, factory methods),
use <A
HREF="http://php.net/manual/en/html/function.include-once.html"
TARGET="_top"
> <TT
CLASS="FUNCTION"
>include_once()</TT
></A
>. Either of these will
ensure that class files are included only once. They share the same file
list, so you don't need to worry about mixing them - a file included
with <TT
CLASS="FUNCTION"
>require_once()</TT
> will not be included again by
<TT
CLASS="FUNCTION"
>include_once()</TT
>.
</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="DEVSTANDARDS-PHPTAGS"
>3.1.1.7. PHP Tags</A
></H3
><P
> Always use <TT
CLASS="COMPUTEROUTPUT"
><?php ?></TT
>
to delimit PHP code, not the <TT
CLASS="COMPUTEROUTPUT"
><? ?></TT
>
shorthand.
</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="DEVSTANDARDS-CONSTANTS"
>3.1.1.8. Naming Constants</A
></H3
><P
> Constants should always be uppercase, with underscores to separate
words.
</P
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="OTHERCONVENTIONS"
>3.1.2. Other Conventions</A
></H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="DEVSTANDARDS-FILENAMING"
>3.1.2.1. File Naming</A
></H3
><P
> File names should be all lowercase and contain no spaces. HTML files
should have <TT
CLASS="FILENAME"
>.html</TT
> as the extension, and PHP files
should have <TT
CLASS="FILENAME"
>.php</TT
> as the extension. Where possible,
template files should match the name of the PHP file that will be using
it, e. g., <TT
CLASS="FILENAME"
>index.html</TT
> would be the template file
for <TT
CLASS="FILENAME"
>index.php</TT
>. Where one PHP file uses more than one
template, the templates should be similarly named:
<TT
CLASS="FILENAME"
>user.php</TT
> could use
<TT
CLASS="FILENAME"
>userlist.html</TT
> and <TT
CLASS="FILENAME"
>userform.html</TT
>
for a list of users and editing a user, respectively.
</P
></DIV
></DIV
></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="dependencies.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"
> </TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Dependencies</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
--- NEW FILE: docs.css ---
.ARTICLE {
font-family: "Verdana","Arial","Helvetica","MS Sans Serif","Sans-Serif";
}
.TITLE {
font-family: "Verdana","Arial","Helvetica","MS Sans Serif","Sans-Serif";
text-align: right;
background-color: #FFDDBB;
padding: .1em; }
.PROGRAMLISTING {
border: 1px black solid;
}
--- NEW FILE: index.html ---
<HTML
><HEAD
><TITLE
>phpBugTracker</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.72
"><LINK
REL="NEXT"
TITLE="User's Guide"
HREF="userguide.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="docs.css"></HEAD
><BODY
CLASS="BOOK"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#800080"
ALINK="#FF0000"
><DIV
CLASS="BOOK"
><A
NAME="INDEX"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="AEN2"
>phpBugTracker</A
></H1
><DIV
><DIV
CLASS="ABSTRACT"
><A
NAME="AEN4"
></A
><P
></P
><P
>phpBugTracker is a web-based bug reporting and tracking system. It allows development teams to manage the testing and debugging segments of the development cycle.</P
><P
></P
></DIV
></DIV
><HR></DIV
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>1. <A
HREF="userguide.html"
>User's Guide</A
></DT
><DT
>2. <A
HREF="adminguide.html"
>Administrator's Guide</A
></DT
><DT
>3. <A
HREF="devguide.html"
>Developer's Guide</A
></DT
><DD
><DL
><DT
>3.1. <A
HREF="devguide.html#DEVSTANDARDS"
>Development Standards</A
></DT
><DD
><DL
><DT
>3.1.1. <A
HREF="devguide.html#DEVSTANDARDS-CODE"
>Coding Standards</A
></DT
><DT
>3.1.2. <A
HREF="devguide.html#OTHERCONVENTIONS"
>Other Conventions</A
></DT
></DL
></DD
><DT
>3.2. <A
HREF="dependencies.html"
>Dependencies</A
></DT
><DD
><DL
><DT
>3.2.1. <A
HREF="dependencies.html#DEP-PHPLIB"
>PHPlib</A
></DT
></DL
></DD
></DL
></DD
></DL
></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"
> </TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
> </TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="userguide.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
> </TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
> </TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>User's Guide</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
--- NEW FILE: userguide.html ---
<HTML
><HEAD
><TITLE
>User's Guide</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.72
"><LINK
REL="HOME"
TITLE="phpBugTracker"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="phpBugTracker"
HREF="index.html"><LINK
REL="NEXT"
TITLE="Administrator's Guide"
HREF="adminguide.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="docs.css"></HEAD
><BODY
CLASS="CHAPTER"
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="index.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="adminguide.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="USERGUIDE"
>Chapter 1. User's Guide</A
></H1
><BLOCKQUOTE
CLASS="ABSTRACT"
><DIV
CLASS="ABSTRACT"
><A
NAME="AEN8"
></A
><P
></P
><P
>Currently all interactions with phpBugTracker are done via the web interface. Users can submit bugs, communicate with developers and testers about bugs, and search through the bug database.</P
><P
></P
></DIV
></BLOCKQUOTE
></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="index.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="adminguide.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>phpBugTracker</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
> </TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Administrator's Guide</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
|
|
From: Benjamin C. <bc...@us...> - 2001-09-27 13:37:54
|
Update of /cvsroot/phpbt/phpbt/docs/html In directory usw-pr-cvs1:/tmp/cvs-serv17701/html Removed Files: devstandards.html Log Message: Moving to the book --- devstandards.html DELETED --- |
|
From: Benjamin C. <bc...@us...> - 2001-09-26 14:20:40
|
Update of /cvsroot/phpbt/phpbt
In directory usw-pr-cvs1:/tmp/cvs-serv22327
Modified Files:
configure
Log Message:
Use read to get the choices rather than backticks
Index: configure
===================================================================
RCS file: /cvsroot/phpbt/phpbt/configure,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- configure 2001/09/23 21:20:00 1.13
+++ configure 2001/09/26 14:20:37 1.14
@@ -35,7 +35,7 @@
if [ $? -gt 0 ]; then
return
fi
- ADMINEMAIL=`<$tempfile`
+ read ADMINEMAIL <$tempfile
$DIALOG --backtitle "phpBT Configuration" \
--title "Installation Path (2 of 5)" \
@@ -46,7 +46,7 @@
if [ $? -gt 0 ]; then
return
fi
- INSTALLPATH=`<$tempfile`
+ read INSTALLPATH <$tempfile
$DIALOG --backtitle "phpBT Configuration" \
--title "Attachment Path (3 of 5)" \
@@ -58,7 +58,7 @@
if [ $? -gt 0 ]; then
return
fi
- ATTACHMENT_PATH=`<$tempfile`
+ read ATTACHMENT_PATH <$tempfile
$DIALOG --backtitle "phpBT Configuration" \
--title "Installation URL (4 of 5)" \
@@ -67,7 +67,7 @@
if [ $? -gt 0 ]; then
return
fi
- INSTALLURL=`<$tempfile`
+ read INSTALLURL <$tempfile
$DIALOG --backtitle "phpBT Configuration" \
--title "PHPlib Path (5 of 5)" \
@@ -77,7 +77,7 @@
return
fi
- PHPLIBPATH=`<$tempfile`
+ read PHPLIBPATH <$tempfile
}
database() {
@@ -90,7 +90,7 @@
if [ $? -gt 0 ]; then
return
fi
- DB_TYPE=`<$tempfile`
+ read DB_TYPE <$tempfile
$DIALOG --backtitle "phpBT Configuration" \
--title "Database Host (2 of 5)" \
@@ -99,7 +99,7 @@
if [ $? -gt 0 ]; then
return
fi
- DB_HOST=`<$tempfile`
+ read DB_HOST <$tempfile
$DIALOG --backtitle "phpBT Configuration" \
--title "Database User (3 of 5)" \
@@ -108,7 +108,7 @@
if [ $? -gt 0 ]; then
return
fi
- DB_USER=`<$tempfile`
+ read DB_USER <$tempfile
$DIALOG --backtitle "phpBT Configuration" \
--title "Database Password (4 of 5)" \
@@ -117,7 +117,7 @@
if [ $? -gt 0 ]; then
return
fi
- DB_PASS=`<$tempfile`
+ read DB_PASS <$tempfile
$DIALOG --backtitle "phpBT Configuration" \
--title "Database Table Prefix (5 of 5)" \
@@ -126,7 +126,7 @@
if [ $? -gt 0 ]; then
return
fi
- DB_TBL_PREFIX=`<$tempfile`
+ read DB_TBL_PREFIX <$tempfile
}
change_features() {
@@ -182,7 +182,7 @@
retval=$?
- choice=`<$tempfile`
+ read choice <$tempfile
if [ $retval -eq 0 ]; then
for selected in $choice
do
@@ -216,7 +216,7 @@
--inputbox "If JPGraph is not in PHP's include path, specify the location of JPGraph." 0 0 $JPGRAPH_PATH \
2> $tempfile
if [ $? -eq 0 ]; then
- JPGRAPH_PATH=`<$tempfile`
+ read JPGRAPH_PATH <$tempfile
fi
fi
@@ -234,7 +234,7 @@
retval=$?
- choice=`<$tempfile`
+ read choice <$tempfile
if [ $retval -eq 0 ]; then
case $choice in
Administrivia)
|
|
From: Ben C. <php...@be...> - 2001-09-26 14:11:53
|
Since we've had some rather serious bug fixes over the last few days, I'm planning on pushing out a release near the end of this week. I'd like to get the configure script working for Patrick before that, so I'll be working on that a bit this morning. Javier, did you ever get the configure script working for you? |
2 messages has been excluded from this view by a project administrator.
