Navigation

Building extensions
  - Introduction
  - Life cycle & Execution mode
  - Content Page Extension
  - Examples
  - Interact with extensions
  - Interact with SMMenu
  - Interact with SMPages
  - Debugging

Building design templates
  - Introduction
  - Place holders
  - Repeating blocks
  - Examples

Framework API
  - Introduction
  - Simple data attributes
  - Authentication
  - Configuration manager
  - Data Sources (DB)
  - Environment data
  - Extension base class
  - The extension context
  - The extension manager
  - Filesystem functions
  - The Form component
  - Image provider
  - Key Value Collections
  - Language handling
  - Logging and error handling
  - GUIDs & Random numbers
  - Various utilities
  - Send and receive data
  - Template engine
  - Text files
  - Strongly typed

GUI Controls
  - Introduction
  - Input types
  - Option list
  - Link button
  - Tree menu
  - Grid view
  - Fieldset (sub form)
  - JavaScript library

Receiving payments
  - Introduction
  - PayPal and Ewire

More help
  - Forum

Logging and error handling

Logging is an important step in qualified debugging (search for errors). Sitemagic CMS comes with the SMLog class, which enables easy logging anywhere in the code.

SMLog::Log(__FILE__, __LINE__, "Loading data");

// Load data here

if (data successfully loaded) // psuedo code
SMLog::Log(__FILE__, __LINE__, "Successfully loaded data");
else
SMLog::Log(__FILE__, __LINE__, "An error occured while loading data");

PHP errors and uncatched exceptions are automatically catched by error handlers. Ordinary errors are written to the SMLog data source, while exceptions are being displayed to the user with a user friendly error message and a complete stack trace, which makes it easy to find the given error.

More information about automatic logging and debugging can be found in the section Debugging under Building extensions.

SMLog class

Function	Return type	Description
::Log($errFile:string, $errLine:integer, $errMsg:string)		Log error or message. The file in which the error occures is stored in __FILE__. A reference to the current line is available using __LINE__. Messages are written to the SMLog data source.
LogDeprecation($depClass:string, $depFunc:string)		Log call to deprecated function (used when no alternative function is available). Example: SMLog::LogDeprecation(__CLASS__, __FUNCTION__);
LogDeprecation($depClass:string, $depFunc:string, $newClass:string, $newFunc:string)		Log call to deprecated function (used when alternative function is available). Example: SMLog::LogDeprecation(__CLASS__, __FUNCTION__, __CLASS__, "NewFunction");