Common Functionality - Error in Common Functionality 7.2
Provides runtime error reporting.
This provides error reporting for use by projects that wish to perform sanity checking to ensure application integrity. The reporting is provided in such a way that it does not hinder the end-user experience of the application while still providing the necessary information to system administrators.
This is not intended to replace the devel module. The devel module does report backtrace, but solely for the purposes of development.
Justification: It is a common practice in the drupal community to not perform sanity checking. Sanity checking is a form of runtime integrity management that is used to ensure that an application runs as expected and that states of inconsistency are avoided.
While sanity checking may incur a slight performance penalty, the gains of security and data integrity vastly outweight the peformance penalties.
Maintaining application integrity provides the following benifits:
- Security via Integrity. That is, the fewer inconsistent states that exist, then fewer attack vectors exist.
- Reliability and Quality of Code The application will provide a higher grade of quaility and reliability that which can be offered by applications that do not perform sanitization.
- Improved Debugability By reporting errors, warnings, and other inconsistent information, site administrators should have an easier time debugging runtime problems.
Parent topics
File
- modules/
cf_error/ cf_error.module, line 8 - Common Functionality - Error Module.
Functions
Name |
Location | Description |
|---|---|---|
| cf_error_cf_permission_alter |
modules/ |
Implements hook_cf_permission_alter(). |
| cf_error_menu |
modules/ |
Implements hook_menu(). |
Classes
|
Name |
Location | Description |
|---|---|---|
| cf_error |
modules/ |
|
| cf_error_code |
modules/ |