By mygumbo on

I've just upgraded to 5.3, but don't think that the upgrade is related to this problem. My PHP script log shows the following error:

PHP Fatal error: Call to undefined function dbquery() in /drupal-5.3/includes/common.inc(1347) : eval()'d code on line 21

I get the error hourly, when cron is running (and bombing with the time exceeded error). How do I track down what is trying to call dbquery (instead of db_query)?

Thanks for any clues.

⋅ Categories: Drupal 5.x

Comments

styro’s picture

styro commented

Or barring that a text editor that can search the contents of files in subdirectories.

If you can't find it in the file system, then it must be code you've submitted into the drupal database. Probably unlikely to be in the database though if it is running during cron.

--
Anton
New to Drupal? | Troubleshooting FAQ
Example knowledge base built with Drupal

gpk’s picture

gpk commented

You could also try the devel or trace modules ... probably best done on a developmental instance (or as a minimum, take a backup first) - devel in particular carries health warning.

Either of these will give a traceback to the source of the offending "dbquery".

gpk
----
www.alexoria.co.uk

gpk
----
www.alexoria.co.uk

mygumbo’s picture

mygumbo commented

Thanks for your ideas. I tracked the problem down to the notify module, and from there, to a content page with bad PHP content (dbquery called instead of db_query). Notify was including teasers from pages and it bombed, hosing the whole cron job as it went. I'm posting over in notify project issues. Thanks again.

gpk’s picture

gpk commented

Presumably the bad page wasn't frequently visited!!

Not sure this is really notify's fault. If you put bad PHP in a block or on a page it is well known that it can hose your site. ARAIK Drupal has no way at present of recovering from this. No harm in bringing it to their attention though.

gpk
----
www.alexoria.co.uk

gpk
----
www.alexoria.co.uk