Debugging Help - Read First Before Posting Issue

Raven · Posted: Sun May 04, 2008 11:29 pm

Lately I've noticed that the path to resolution to several different issues has been with the theme being used. Please notice that I said the path to resolution Wink

.

Before posting your issue, please just take a moment to switch to the fisubice theme that comes with RavenNuke(tm). If your issue still exists then it's probably not theme related. However, if the issue does NOT exist when using the fisubice theme then the chances are very good that it IS theme related. This will help expedite a resolution to your issue.

Raven · Posted: Mon May 05, 2008 10:04 am

Another great debugging tool is included in RavenNuke(tm) that definitely deserves mention in the event you aren't inclined to read the documentation Wink

.

Only registered users can see links on this board!
Get registered or login to the forums!

has added code that tracks all SQL calls and reports back different amounts of information based upon what log level you set. In the rnconfig.php file there is a setting called $loglevel. By default it is set to 0 (zero). Here is the internal documentation/note from the rnconfig.php file. It is self explanatory.

Code:

/*********************************************************************************
* SQL Logging to Text Log File:
* Calls through db/mysql.php only are logged.
* loglevel = 0 -> no logging (default setting)
* loglevel = 1 -> logs sql errors (with associated IP address) only
* loglevel = 2 -> logs ALL sql query statements and errors and is intended for
* development testing purposes only as the log file can grow
* rather quickly!
* set up a dblog file in your /rnlogs directory with privileges of 666 to use this
*********************************************************************************/
$loglevel = 0;

This is a most excellent utility to use when all looks well and you can't seem to figure out why something isn't adding a record, modifying a record, etc.

Also, setting the $error_reporting to E_ALL ($error_reporting = E_ALL;) while debugging will assist you.

Be sure to always check your server error log for other messages that may be helpful.