These two modules, ch_debugger and ch_nodeapi_preexec, are hook debuggers, used for collecting arrays and objects and store the data in a table for later analysis.

As the module is now, it's made for listening on:

  • nodeapi
  • user
  • form_alter
  • views_pre_view
  • views_pre_build
  • views_pre_execute

If you want to create other/different hooks, please follow the logic's of the existing six hooks in this module.

You can by advance install 'Xdebug' from xdebug.org.
If that PHP plugin is enabled, the debugger will store the call line in the table, which can be pretty help full, when debugging.

Getting started:

Install both modules, and set the permission for 'administer site configuration'
Now enter /admin/settings/ch_debugger and set your needs and role permissions.
By role, I mean a role that may trig a hook.

All the output goes to /admin/reports/ch_debugger, where you can see all the collected data, grouped in php instances.

In the case of following a nodeapi, you can enable the 'ch_nodeapi_preexec' module and get a hook running time on every nodeapi hooks.
This module places a time stamp inside the nodeapi object, to follow.
This can be very help full when working with performance issues.

Just like the Devel module's dpm / dvm function, this module got a sdd($obj) function that stores data when needed.

How does this module differ from other debugging modules:
I'm using devel on a daily basis. It is a nice tool, but it is lacking a few features.

  1. On some dpm() dumps, the output disappears for some reason
  2. When running dpm(), the http header tends to get overfilled with the returning dpm data
  3. On some dpm() dumps, I need to compare objects or arrays
  4. On some hook "run through", I need to do a speed test.
  5. No need of placing dpm in code!

Why that project name?
Well, a lack of fantacy!

The link to the project is HERE

CommentFileSizeAuthor
ch_debugger.jpg146.67 KBChristian Heiberg
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

PA robot’s picture

Status: Needs review » Needs work

There are some errors reported by automated review tools, did you already check them? See http://ventral.org/pareview/httpgitdrupalorgsandboxChristianHeiberg20601...

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)

Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).

I'm a robot and this is an automated message from Project Applications Scraper.

PA robot’s picture

Status: Needs work » Closed (won't fix)

Closing due to lack of activity. Feel free to reopen if you are still working on this application (see also the project application workflow).

I'm a robot and this is an automated message from Project Applications Scraper.

Christian Heiberg’s picture

Christian Heiberg’s picture

Status: Closed (won't fix) » Needs review

From what I know, there is no issues, when running in my constellation.
But there is allways room for improvement.

Christian Heiberg’s picture

The errors reported in comment #1 is relating to the fact, that the project was spotted ad a D7 project, which is not the case.

klausi’s picture

Status: Needs review » Needs work

As far as I see most of them apply to D6 as well, so please fix them first.

PA robot’s picture

Status: Needs work » Closed (won't fix)

Closing due to lack of activity. Feel free to reopen if you are still working on this application (see also the project application workflow).

I'm a robot and this is an automated message from Project Applications Scraper.