Got debug messages from views today when upgrading to rc3. Got that it was views_plugin_query_default.inc that was throwing the error but not which view it was. I added a little thing to the error message saying which view it is that is throwing the error. Easier to find the error and fix it.

In views_plugin_query_default.inc on line 1386:

To:
debug('Exception in ' . $view->human_name . '['.$view->name.'] : ' . $e->getMessage());
From:
debug('Exception in: ' . $e->getMessage());

CommentFileSizeAuthor
#1 views-1348050-1.patch555 bytestim.plunkett

Comments

tim.plunkett’s picture

Version: 7.x-3.0-rc3 » 7.x-3.x-dev
Issue tags: -views3, -exception error, -Debugging
StatusFileSize
new555 bytes

Grepping through the various calls to debug(), this does seem like the one that gives the least information. Here's an actual patch.

dawehner’s picture

I'm not sure but why not use vpr()?

Vpr uses debug() if a simpletest is running
else it can write into the watchdog and in theory would be able to display the message in a certain region.

dawehner’s picture

Status: Needs review » Fixed

Committed a patch with vpr()

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.