| 1 |
pjm2 |
1.1 |
PHP interface for i-scream reports |
| 2 |
|
|
================================== |
| 3 |
|
|
|
| 4 |
|
|
|
| 5 |
|
|
Installation |
| 6 |
|
|
------------ |
| 7 |
|
|
You must be running a web server that supports PHP4 scripting. |
| 8 |
|
|
All of the files in the archive must be located in the same |
| 9 |
|
|
directory for normal operation. |
| 10 |
|
|
|
| 11 |
|
|
Configuration |
| 12 |
|
|
------------- |
| 13 |
|
|
Each section of the reports may be configured by editing the |
| 14 |
|
|
appropriate _config.inc.php file. This will be required to |
| 15 |
|
|
tell each section the paths to use to find the i-scream report |
| 16 |
|
|
data. |
| 17 |
|
|
|
| 18 |
|
|
Customising |
| 19 |
|
|
----------- |
| 20 |
|
|
If necessary, the header and footer of each page may be altered. |
| 21 |
|
|
The header area of each page is stored in title.inc.php and |
| 22 |
|
|
contains some PHP scripting, so care must be taken not to affect |
| 23 |
|
|
the functionality of this file. The footer area is stored in |
| 24 |
|
|
bottom.inc and is static. Other PHP files may be altered as |
| 25 |
|
|
required, however, i-scream accepts no responsibility for any |
| 26 |
|
|
damage caused. |
| 27 |
|
|
|
| 28 |
|
|
Privacy |
| 29 |
|
|
------- |
| 30 |
|
|
In some circumstances, data provided by the i-scream monitoring |
| 31 |
|
|
system may be regarded as 'personal data'. It is your |
| 32 |
|
|
responsibilty to control access to such data in a web environment |
| 33 |
|
|
and ensure that you comply fully with the Data Protection Act 1998. |
| 34 |
|
|
|
| 35 |
|
|
|
| 36 |
|
|
Copyright i-scream 2001 |
| 37 |
tdb |
1.2 |
http://www.i-scream.org |
