Drupal Quick & Dirty Debugging


So you’re coding along, developing your site, minding your own business, when you load a page you see some totally vague, obscure error message such as:

Where do you even start debugging something like that?

Well, you could start with looking at line 504 of node.module…

$value) {
Uh, yeah. That’s helpful.

If you were astute, you might also observe that line 504 is inside of the node_load() function. So that narrows it down to… only one of the 80,000 places node_load() might be called from one of your core or contributed modules or themes. Ugh…

You could decide to get all fancy, and install an IDE like Komodo, Eclipse, or Zend, and use their real-time debugging features to step through the code one line at a time to figure out what’s happening. It’s pretty time-consuming, and it takes up lots of resources on your machine, but it’ll probably…

View original post 685 more words


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s