Debugging a prometheus instance gone wrong:

Verify that your tables are correct.  The table descriptions are 
found in -

(top level of prometheus)/prometheus-library/sql/table/(database name)/


Now for the nity gritty, debugging via changing source (ikcy poo).
Before you start this you'll need to remove the autoload.lib which
contains a precompiled version of the source base so that you can
edit code.

rm (top level of prometheus)/autoload.lib

The debugging messages will dump within the source of the rendered
html as comments. Look for lines like :

<!-- Mysql_Db::Admin_Privlages_Db - error cannot connect -->

If you are having issues with the sessions for example:

Go into the sessions database file :
(top level of prometheus)/prometheus-library/db/Session_Db/

edit the Session.object to have the following lines changed:

 $this->debug->Off();

becomes:

 $this->debug->On();

Files to edit to activate debugging for other parts of the system:

Admin Privlages (AdminPrivlages_Db) -
   Controls who gets the administrative console (add/edit/delete users)

   Edit:
      Mysql_AdminPrivlages_Db.object

Customer Information Db (CustomerInformation_Db) -
   Controls the customer information that is associated to the
   user account information.

   Edit:
      Mysql_CustomerInformation_Db.object
      Mysql_CustomerAddress_Db.object
      Mysql_CustomerPhoneNumber_Db.object

Mail Server Settings (MailServer_Settings_Db) -
   Stores the settings for the user's mailboxes.

   Edit:
      Mysql_MailServerSettings_Db.object

Prometheus Information Manager ( PPIM_Db ) -
   Manages the personal information for the user.

   Edit:
      Mysql_PPIM_email_Db.object
      Mysql_PPIM_person_Db.object

User ( User_Db ) -
   The users database.

   Edit:
      Mysql_User_Db.object
      Mysql_User_Theme_Db.object
      User.object

User Domains ( User_Domain_Db ) -
   The user domain database is a collision domain mechanism that
   breaks up the username space.

   Edit:
      Mysql_User_Domain_Db
