While developing we strongly recommend to use logs for errors detection.

DHTMLX permits logging to be controlled in two ways:

• Basic
• Detailed

If any error occurs during data processing, client-side data processor object will receive “error” action containing short info about the problem (full info will be written to the log).

$conn->enable_log("path");

• path - absolute or relative path to text file where log will be written.

When critical error occurs all log records for current session (full error info) will be sent to client and shown in browser (useful for debugging, not recommended for production):

$conn->enable_log("path",true);

• path - absolute or relative path to text file where log will be written.
• The second parameter enables detailed mode.

During development you may need to write some custom data to the log (can be useful for custom server-side events).
To add custom text or data to log file:

• Activate logging (basic or detailed).
• Call log() function with your data inside.

$conn->enable_log("temp.log");
LogMaster::log("any text here");

Dataprocessor has its own client-side logger, which can be enabled by including one additional js file - dhtmlxdataprocessor_debug.js