This class extends the Mouse core class. It is extended by any data class object.

It utilizes the mysqli extension for the MySQL Database. It obtains its configuration details from the config.php file and the php.ini configuration file.

$this->mysqli = new mysqli(ini_get("mysqli.default_host"), ini_get("mysqli.default_user"), ini_get("mysqli.default_pw"), lms_get_env_val('db.db'));

Key public methods include:

db_prepare($sql, $bndprms)
db_write($stmt)
commit()  --optional
rollback()  --optional

This class extends the Page core class.

Default attributes are set, but may be overridden by classes extending this class.

$this->total_pages = 0;
$this->page_size = 10;
$this->current_page = 1;
$this->total_rows = 0; --override required

To utilize the features of this class, the total_rows attribute is the only required override. There are no key public methods.

This class is only extended by the DB core class. It is based on a limited implementation of Perl's Moose module. As such, it utilizes Reflection to catch methods which are undefined in extending classes.

The only public methods are:

has($attributes) --defines the attributes of the Mouse object
get_attribute_names() --gets the "name" of all attributes of the Mouse object

Reflection Methods

Mouse will interpret several Reflection methods. The first set of methods act upon the values of the Mouse Object Attribute; the second set of methods perform database functions; and the last method may be used to modify the Options of a particular Mouse Object Attribute.

Value Methods:
get_ --the Mouse Reader (getter) method
set_ --the Mouse Writer (setter) method
has_ --the Mouse Predicate (isset) method
clear_ --the Mouse Clearer (unset) method

DB Methods:
count_ --count the number of list results returned from the database for the Mouse Object
list_ --select multiple results from the database representing the Mouse Object
read_ --select a single result from the database representing the Mouse Object
delete_ --delete the current Mouse Object from the database
save_ --insert or update the current Mouse Object in the database

Attribute Methods:
modify_ --the Mouse Option editor

Reflection Methods Defined

Reader: For each attribute passed into Mouse via a "has" method, a getter method is created. For example, if "seq" is the attribute passed in, "get_seq" will be generated. This may be overridden by creating a "get_seq" method within the calling Object or within an Object which extends the calling Object.

Writer: For each attribute passed into Mouse via a "has" method, a setter method is created. For example, if "seq" is the attribute passed in, "set_seq" will be generated. This method will not be usable if the attribute's "is" option is set to "ro" (read only). This method may be overridden by creating a "set_seq" method within the calling Object or within an Object which extends the calling Object.

Predicate: For each attribute passed into Mouse via a "has" method, a predicate method is created. For example, if "seq" is the attribute passed in, "has_seq" will be generated. This may be overridden by creating a "has_seq" method within the calling Object or within an Object which extends the calling Object.

Clearer: For each attribute passed into Mouse via a "has" method, a clearer method is created. For example, if "seq" is the attribute passed in, "clear_seq" will be generated. This method will not be usable if the attribute's "is" option is set to "ro" (read only). This method may be overridden by creating a "clear_seq" method within the calling Object or within an Object which extends the calling Object.

Count: This generates the count of objects returned by the DB List Reader.

DB List Reader: This is a generic list collection obtained from dynamically generated SQL. It is optionally used in conjunction with the auto_render_list Render helper functions. For example, if "list_lms_audit()" is called, Mouse interprets this to be a "list" call of the "lms_audit" database table.

DB Reader: This is a single row DB reader which dynamically generates SQL based upon the Mouse Object and each Attribute's options. It is optionally used in conjunction with the auto_render_view Render helper functions. For example, if "read_lms_audit()" is called, Mouse interprets this to be a "read" of the "lms_audit" database table.

DB Delete: This is a single row DB deletion method for the Mouse object.

DB Save: This is a single row DB save method for the Mouse object.

Modify: In order to modify a Mouse Attribute after it has been instantiated, a variable can be set and passed via the "modify_" Reflection method. For example, in order to add or change the "link" option of the "subject" attribute:

$subject->link = function($data) {
       //message_id is in the 0th array position of this MOUSE object
       return('default.php?appname=message-view&message_id=' . $data[0]);}; 
$this->data->modify_subject($subject);

Attribute Options

Each Attribute in a Mouse Object has multiple Options which control how an Attribute is rendered and its specific requirements.

Main Options: isa, is, name, init, trigger, doc, join, control, required

List View Relevant Option Only: link, order

View and Edit Relevant Options Only: row, col

Edit Relevant Option Only: primary_key

List and View Relevant Options Only: style

Attribute Options Defined

"name": A name to report during errors, to set labels, and to set column names.

"is": Each attribute which is passed into Mouse via a "has" method will be considered readable and writable ("rw") unless otherwise specified with an "ro" (read only).

"isa": A valid PHP Type or a Mouse SubType (eg. boolean, integer, float, string, array, Str32, username, etc.). This is the only required option an Attribute must express.

"init": Default values for attributes may be assigned using the "init" option. If no value is passed in, the default value will be null. If an empty array is desired as the default, the init value will need to be "array()" AND/OR the "isa" value must be 'array'.

"required": If a particular Attribute is required (especially if the DB field cannot be null), this flag will be set to true. If a required Attribute isn't set, an error will be returned to the Page class.

"trigger": If you need to have a method execute any time an attribute's value is set (ie. when the "set_XXX" method is called), provide the name of the method you need to use to the "trigger" option. The "trigger" method will execute AFTER the "set_XXX" method is called. This method needs to be located within the calling Object. This does not occur when the attribute's default value is set via the "init" option.

"doc": Any string you may want to pass along with the attribute. For example, text describing the attribute. This option does not have any programmatic functionality.

"link": An optional Closure Function which permits the rendering of links on associated Attributes of a list view. For example, the Attribute below uses a link function to create a link on the values of the Subject Attribute which point to the message-view page with the message_id equal to the first (or 0th) Mouse Attribute (which, in this case is message_id):

subject => array(name => 'Subject', isa => 'Str32',
        link => function($data) {
                return('default.php?appname=message-view&message_id=' . $data[0]);})

"primary_key": For Mouse objects which are going to be saved, the table's primary key needs to be identified (boolean).

"join": For some attributes, the actual value may not be what needs to be displayed. For example, a user's name will always be displayed instead of the user_id. In order to achieve this, a table and column join may be used:

join => array(table => 'lms_user',
                column => 'lms_user.username',
                where => 'lms_user.user_id = lms_audit.user_id',
                group => 'lms_user.username')

If a column => " ' ' " is provided, an empty value is returned for the row. This is useful if you want to show a button, image, or link without data being pulled from the database.
If a column => " " is provided, no value is returned. This is useful if you want to track a value or calculation within a row, but don't want to have the DB SQL query affected.

"order": If there is an "orderable" nature to the attribute, then it may be indicated here with "asc" or "ascending" for sorting A-Z or "desc" or "descending" for sorting Z-A. It is best to arrange the ordered columns at the end of the has() method or all columns will be ordered after it in the SQL call. For example, positioning the ordered "date_time" column before the "user_id" and then sorting by the "user_id" in the auto_render_list method will result in the username being sorted within the date_time sort (that is, ORDER BY date_time, username).

"row": The row that a particular attribute is to be rendered on. This allows for specific arranging of attributes.

"col": The column that a particular attribute is to be rendered on. This allows for specific arranging of attributes.

"control": An optional Closure Function allows the rendering of HTML controls on Edit pages.

control => function($args) use ($options) {
        render_multiselect("to_user_id[]", $_POST['to_user_id'], $options, "5");}

"style": An optional Closure Function for setting the style of the output results in a List or View page.

style => function($data) {
       //$data[5] is the 6th column (a date) of a list collection
        if ($data[5] == "0000-00-00 00:00:00") {
                return("font-weight:bold;");}}

Example usage of all Attributes for a single Element:

$this->has(array(
        element => array(
                name => 'element name', //the element label/title; leave empty to hide element; empty by default; optional
                is => 'rw', //read-only (ro) or read-writable (rw); 'rw' by default; optional
                isa => 'int' //a valid PHP Type or Mouse SubType; required
                init => 'initial value", //null by default; optional
                required => 0, //set to true (1) if the field cannot be null; 0 by default; optional
                trigger => 'method_name', //execute method_name() existing in this class; null by default; optional
                doc => 'Any text describing what this element is', //null by default; optional
                link => function($data) {return('default.php');}, //turn element output into an HTML link; null by default; optional
                primary_key => 0, //if this is a DB table key, set to true (1); 0 by default; optional
                join => array(table => 'table_name',
                                column => 'table_name.column_name',
                                where => 'table_name.id = other_table.id',
                                group => 'column_name'), //Construct the DB JOIN for complex queries; optional
                order => 'ASC', //'ASC' or 'DESC' sort order for lists; 'ASC' by default; optional
                row => 1, //the row of a table an element will be rendered on; optional
                col => 1, //the column of a table an element will be rendered on; optional
                control => function($args) use ($optional) {do_some_work();}, //render the output as an HTML control; optional
                style => function($data) {do_some_work();}))) //render the output with function-defined CSS; optional

Example usage of relevant Attributes for a hypothetical Object:

$this->has(array(
        seq => array(isa => 'int'),
        audit_type => array(name => 'Audit Type', isa => 'Str32'),
        entry_type => array(name => 'Entry Type', isa => 'UCStr8'),
        date_time => array(name => 'Timestamp', isa => 'DateTime'),
        user_id => array(name => 'Username', isa => 'int'),
        modified_column => array(name => 'Modified Column', isa => 'Str32'),
        old_value => array(name => 'Old Value', isa => 'str'),
        new_value => array(name => 'New Value', isa => 'str')
));

Mouse SubTypes

Mouse SubTypes are children of the standard PHP Types. They can be used to construct commonly used patterns which conform to specific regular expressions (regexes) and post-setter manipulation (eg. capitalization, rounding, etc.).

Mouse SubTypes Defined

"isa": Each SubType must be based upon a valid PHP Type (Boolean, String, Integer, Float, or Array).

"regex": A regular expression used for validating the values passed in.

"where": A function used to modify the value prior to SETTING.

"message": A message to return if the regex doesn't match the value.

Example usage:

new SubType('UCStr8',
        array(isa => 'str',
                 regex => '/^[A-Z0-9-!"#$%&\(\)*+,.\/:;=?@_~ ]{0,8}$/',
                 where => function($val){return(strtoupper($val));},
                 message => 'Values must be alphanumeric capitals with a maximum of 8 characters.'));

This class is extended by any page class object and the FilterPage class directly.

The majority of its methods are overridden by the extending class. The only key public methods include:

addError($e)
addWarning($e)
addMessage($e)
addHeader($e)
addJavascript($e)

The execution sequence of methods which may be overridden is:

1) pre_render()
2) body_onload()
3) titleBar()
4) menuBar()
5) errorList()
6) warningList()
7) messageList()
8) render()
9) footer()


This file instantiates the User objects (UserGroup and User) and contains a number of non-class utility methods. These public methods are generally used internally, but may be used externally.

lms_get_user_id()
lms_get_username()
lms_get_current_user()
lms_get_user_object()
lms_get_primary_group_name($user)

This collection of functions acts to initiate the construction of objects and to regulate the associated privileges. URLs and redirects are managed here as well. It is called by the default files (cgi-bin/default.php and open-bin/default.php) and acts in turn to load the Core Classes.

There are no key public methods.

This collection of functions acts to produce output in specific formats or control structures.

Render HTML Controls:

render_input($html_args:array)
render_textarea($html_args:array, $value:string)
render_popup($name:string, $selected_option:string, $options:array of hash, $null_option:boolean, $style_arg:string, $onChange:string, $disabled:boolean)
render_multiselect($name:string, $selected_options:array, $options:array of hash, $number_rows:string, $multiselect:boolean, $style:string, $onchange_args:string, $disable_control:boolean)

Render General Input and Output:

lms_print_r($variable:any) [print the objects in HTML format for debugging purposes]
lmsecho($value:string) [htmlentities a value]
decho($value:string) [debug echo]
null_float($value:any) [cast as a float or NULL]
escape_js($value:string) [replace ', \, and \\ in JS]
lms_trim($value:string) [strip escapes and spaces]
csv_trim($string:string) [strip spaces]
csv_encode($data:array) [render hash as pipe-delimited text]

Page Controls and Views:

set_form($action:string, $encoding:string)
render_delete_button($owner_id:integer, $appname:string, $disable:boolean) [show a delete button if the user has the priv]
render_save_button()
render_button_bar($width:string, $owner_id:integer, $appname:string, $disable:boolean) [if this is an object that is "owned" by a single user, pass that owner_id and the name of the app so that the system can determine if a delete button should be shown]
render_pagination_bar($current_page:integer, $total_pages:integer, $total_rows:integer, $goToPage:boolean, $showGoToPage:boolean)
auto_render_list($data:MouseObject, $list:array of hash, $printable:boolean, $links:array of hash, $title: string)
auto_render_view($data:MouseObject, $title:string, $width:string, $links:array of hash)

This group of methods acts to execute common non-class based functionality.

The key public methods include:

lms_get_groups() [returns all LMS groups]
lms_mimetype($extension:string, $mimetype:string) [returns either extension or mime type for a given $extension or $mimetype]
lms_get_menu_data() [returns the menu list to build the main menu]
lms_array_match($patterns:array, $target:string, $optional_replace_value:$string) [given an array of regex patterns, see if a match occurs in the target]
hash_search_array($needle:hash of arrays, $haystack:array) [search an array with a hash(array) to get the array key]
lms_gen_rand_str($length:integer)
lms_crypt($s:string, $salt:string)
lms_uuid()

Auditing may be achieved in an automated fashion by conforming to a few simple database conventions.

First, the table that you want to audit needs to have a "user_id" which correlates to the user making the change. So, when a user creates, updates, or deletes a row, their user_id is used to track the change. Then, a few SQL scripts may be executed to generate the triggers necessary to populate the audit table.

To create the audit triggers, the following scripts may be run to generate the corresponding SQL statements.

SELECT CONCAT('CREATE TRIGGER ', table_name, '_update_audit AFTER UPDATE ON ', table_name,
' FOR EACH ROW BEGIN DECLARE i_index BIGINT(20); SET i_index = (SELECT MAX(cluster)+1 FROM lms_audit); ',
audit_column_gen(table_name, 'UPDATE'), ' END$$') FROM information_schema.columns
WHERE table_schema = DATABASE()
AND column_name = 'user_id'
AND table_name NOT LIKE 'lms_post'
AND table_name NOT LIKE 'lms_message'
AND table_name NOT LIKE 'lms_user'
AND table_name NOT LIKE 'lms_user_cookie'
AND table_name NOT LIKE '%audit%'
AND table_name NOT LIKE '%object%';

SELECT CONCAT('CREATE TRIGGER ', table_name, '_insert_audit AFTER INSERT ON ', table_name,
' FOR EACH ROW BEGIN DECLARE i_index BIGINT(20); SET i_index = (SELECT MAX(cluster)+1 FROM lms_audit); ',
audit_column_gen(table_name, 'INSERT'), ' END$$') FROM information_schema.columns
WHERE table_schema = DATABASE()
AND column_name = 'user_id'
AND table_name NOT LIKE 'lms_post'
AND table_name NOT LIKE 'lms_message'
AND table_name NOT LIKE 'lms_user'
AND table_name NOT LIKE 'lms_user_cookie'
AND table_name NOT LIKE '%audit%'
AND table_name NOT LIKE '%object%';

SELECT CONCAT('CREATE TRIGGER ', table_name, '_delete_audit AFTER DELETE ON ', table_name,
' FOR EACH ROW BEGIN DECLARE i_index BIGINT(20); SET i_index = (SELECT MAX(cluster)+1 FROM lms_audit); ',
audit_column_gen(table_name, 'DELETE'), ' END$$') FROM information_schema.columns
WHERE table_schema = DATABASE()
AND column_name = 'user_id'
AND table_name NOT LIKE 'lms_post'
AND table_name NOT LIKE 'lms_message'
AND table_name NOT LIKE 'lms_user'
AND table_name NOT LIKE 'lms_user_cookie'
AND table_name NOT LIKE '%audit%'
AND table_name NOT LIKE '%object%';

The above scripts require the audit_column_gen function available in the schema/lms_functions.sql file.

To delete the audit triggers, the following scripts may be run to generate the corresponding SQL statements.

SELECT CONCAT('DROP TRIGGER IF EXISTS ', table_name, '_update_audit$$') FROM information_schema.columns
WHERE table_schema = DATABASE()
AND column_name = 'user_id'
AND table_name NOT LIKE 'lms_post'
AND table_name NOT LIKE 'lms_message'
AND table_name NOT LIKE 'lms_user'
AND table_name NOT LIKE 'lms_user_cookie'
AND table_name NOT LIKE '%audit%'
AND table_name NOT LIKE '%object%';

SELECT CONCAT('DROP TRIGGER IF EXISTS ', table_name, '_insert_audit$$') FROM information_schema.columns
WHERE table_schema = DATABASE()
AND column_name = 'user_id'
AND table_name NOT LIKE 'lms_post'
AND table_name NOT LIKE 'lms_message'
AND table_name NOT LIKE 'lms_user'
AND table_name NOT LIKE 'lms_user_cookie'
AND table_name NOT LIKE '%audit%'
AND table_name NOT LIKE '%object%';

SELECT CONCAT('DROP TRIGGER IF EXISTS ', table_name, '_delete_audit$$') FROM information_schema.columns
WHERE table_schema = DATABASE()
AND column_name = 'user_id'
AND table_name NOT LIKE 'lms_post'
AND table_name NOT LIKE 'lms_message'
AND table_name NOT LIKE 'lms_user'
AND table_name NOT LIKE 'lms_user_cookie'
AND table_name NOT LIKE '%audit%'
AND table_name NOT LIKE '%object%';

Using either Mouse Object constructor detailed above, a Message Editor Page Class would look like:

class MessageEditor extends Page {
    function __construct() {
        parent::__construct("Message Editor");
        $this->data = new MessageDB();
        $this->list = array();
    }

    function pre_render() {
        parent::pre_render();

        //alternatively, the following may be set as init => $_POST[xxxx] in the MOUSE object
        if (isset($_POST["subject"])) {$this->data->set_subject($_POST["subject"]);}
        if (isset($_POST["message"])) {$this->data->set_message($_POST["message"]);}

        if (isset($_REQUEST['Save'])) {
            if (count($_REQUEST['to_user_id']) > 0) {
                foreach ($_REQUEST['to_user_id'] as $id) {
                    $this->data->set_to_user_id($id);
                    $this->data->save_lms_message();
                }
            }
            if ($this->error_count() == 0) {
                my_redirect("default.php?appname=message-mgr");
            }
        }

        if (isset($_REQUEST['Cancel'])) {
            my_redirect("default.php?appname=message-mgr");
        }
    }

    function body() {
        set_form("/cgi-bin/default.php?appname=message-edit");
        auto_render_view($this->data, "Create a Message", "600px");
        render_button_bar("600px");
        echo('</form>');

    }
}

Steps to create a new page:

1) Insert entry into the lms_app table.

INSERT IGNORE INTO lms_app (NAME, module, constructor, proper_name, GLOBAL)
    VALUES ('url-ref', 'objects/dir/file.php', 'Class', 'Name to Show on Page', 'global_variable');

2) Insert an entry into the lms_menu table.

INSERT IGNORE INTO lms_menu (NAME, url, hierarchy, groups, description, visible)
    VALUES ('Audits', '/cgi-bin/default.php?appname=audit', '90.25',
        (SELECT group_id FROM lms_group WHERE groupname IN ('Master Administrator')),
        'The system audit log menu', 1);

3) Insert an entry into the lms_app_group table (if the page being created is only available to certain groups)

INSERT IGNORE INTO lms_app_group (NAME, group_id)
    VALUES ('audit',
        (SELECT group_id FROM lms_group WHERE groupname IN ('Master Administrator')));

4) Add a root .php file to the objects subdirectory (eg. objects/dir/file.php)

<?php include_once("objects/admin/data/audit.php"); include_once("objects/admin/view/audit.php"); ?>

5) Add a data .php file to the data subdirectory (eg. objects/dir/data/file.php)

<?php class NameDB extends DB {
         function __construct() {
            parent::__construct();
           $this->has(array( ... ));
         }
      }
?>

6) Add a page .php file to the view subdirectory (eg. objects/dir/view/file.php)

<?php class Name extends Page {
         function __construct() {
            parent::__construct("Name");
           $this->data = new NameDB();
         }

         function body() {
             $this->auto_render();
         }
      }
?>

Using either Mouse Object constructor detailed above, a Message Manager Page Class would look like:

class MessageManager extends FilterPage {
    function __construct() {
        parent::__construct("Message Manager");
        $this->data = new MessageDB();
        $this->list = array();
        $this->attributes = array();
        $this->page_size = 20; //overload FilterPage
        $this->total_rows = $this->data->count_lms_message(); //overload FilterPage
    }

    function pre_render() {
        parent::pre_render();
        if ($_REQUEST['print']) {
            $this->page_size = $this->total_rows; //if this is a printable page, show all of the results
        }
        //select from lms_message table
        $this->list = $this->data->list_lms_message(($this->get_current_page()-1) * $this->get_page_size(),
                                                     $this->get_page_size());
    }

    function body() {
        if (!$_REQUEST['print']) {
            render_pagination_bar($this->current_page, $this->total_pages, $this->total_rows, true);
        }
        auto_render_list($this->data, $this->list, true);
        if (!$_REQUEST['print']) {
            render_pagination_bar($this->current_page, $this->total_pages, $this->total_rows, false);
        }
    }
}

The following examples take a Mouse class and produce a number of views reflecting standard Create, Read, Update, and Delete (CRUD) functionality.

Generally, Mouse objects can be constructed in one of two ways. The first way is to create a separate Mouse Object for each of the rendering types. The second way is with a single class representing the complete Mouse Object which uses “modify_” Reflection methods to alter the Object based on the type of rendering (eg. list, editor, or viewer) being performed. The first way is cleaner with regard to code clutter; the second, with regard to file clutter.

The first method is preferred as it is easier to read and manage, but the second method could provide a smaller memory footprint and faster memory access should the developer decide to keep the PHP files resident in the web server or compiled to C byte code.

Using either Mouse Object constructor detailed above, a Message Viewer Page Class would look like:

class MessageViewer extends Page {
    function __construct() {
        parent::__construct("Message Viewer");
        $this->data = new MessageDB();
        $this->list = array();
    }

    function pre_render() {
        parent::pre_render();
        //handle deletes if a mission_id is presented
        if ($_REQUEST['delete']) { $this->handle_delete(); }

        $this->message = $this->data->read_lms_message();
        if (empty($this->message)) { $this->addError("No message associated with this message ID."); }
    }

    function body() {
        if (!empty($this->message)) {
            $this->data->update_message_read_time();
            $links = array(array(link => "default.php?appname=message-view&delete=1&message_id=" .
                     $this->data->get_message_id(), label => "Delete"));
            auto_render_view($this->data, '"' . $this->data->get_subject() . '"', "600px", $links);
        }
    }

    function handle_delete() {
        $this->data->delete_lms_message();
        my_redirect('default.php?appname=message-mgr');
    }
}

Setting the global variable $DEBUG above the class declaration will provide significant feedback above the webpage's Title Bar and a small amount of feedback in the Message Area below the Menu Bar. If $DEBUG is set at a higher order (eg. std/page.php), the small amount of feedback in the Message Area will also be generated.

As an example:

ATTRIBUTE: seq= Array ( [isa] => int
                Read/Writable? = 1
                Initialize Value =
                Attribute Object ( [key] => seq [vals] => Array [name] => [read_writable] => 1 [isa] => integer [trigger] => [doc] => [type] => string [subtype] => Array

Verb is set? 1 (count)
Attribute exists? 0 (lms_audit)

Setting the global variable $DEBUG above the class declaration will provide significant feedback below the webpage's Footer. If $DEBUG is set at this level, any pages loaded after it by the system will also have its debugging activated. $DEBUG may also be set in cgi-bin/settings.php.

As an example:

PHP parsed this page in 0.349 seconds.
PHP used 1,108 KB at peak emalloc usage.
PHP used 1,311 KB at peak memory usage.

PHP has loaded the following files to render this page: Array ( [0] => C:\LMS\LIMS\cgi-bin\default.php [1] => C:\LMS\LIMS\cgi-bin\settings.php [2] => C:\LMS\LIMS\lib\objects\Objects.php [3] => C:\LMS\LIMS\lib\objects\Mouse.php [4] => C:\LMS\LIMS\lib\objects\Mouse-SubType.php [5] => C:\LMS\LIMS\lib\objects\Mouse-Attribute.php [6] => C:\LMS\LIMS\lib\objects\Mouse-SubTypes.php [7] => C:\LMS\LIMS\lib\objects\DB.php [8] => C:\LMS\LIMS\lib\objects\Page.php [9] => C:\LMS\LIMS\lib\objects\FilterPage.php [10] => C:\LMS\LIMS\lib\objects\System.php [11] => C:\LMS\LIMS\lib\objects\User.php [12] => C:\LMS\LIMS\lib\objects\Validation.php [13] => C:\LMS\LIMS\lib\objects\Render.php [14] => C:\LMS\LIMS\lib\objects\admin\audit.php [15] => C:\LMS\LIMS\lib\objects\admin\data\audit.php [16] => C:\LMS\LIMS\lib\objects\admin\view\audit.php [17] => C:\LMS\LIMS\lib\std\page.php [18] => C:\LMS\LIMS\lib\std\header.php [19] => C:\LMS\LIMS\lib\std\titlebar.php [20] => C:\LMS\LIMS\lib\std\menubar.php [21] => C:\LMS\LIMS\lib\std\messages.php [22] => C:\LMS\LIMS\lib\std\errors.php [23] => C:\LMS\LIMS\lib\std\footer.php