User login

Boston Drupal Meetup

To find out what is making a cron run very long (or failing)

A bunch of functions run when cron is run, to find out what is causing the overall run to take a long time (possibly timing out and breaking), you need to look at them piece by piece. This code does that:

Code courtesy Tim Hilliard and tip courtesy George Cassie.

Browsing the Drupal database

Moshe on browsing the database at the Boston

He uses the Mac program SequelPro (completely free and open source).


Find $db_url in settings.php

username, password, host, and database name.

Can put this data into Sequel Pro.

Bottom line: as long as you have a backup, do not be afraid to fiddle with your database!

Syndicate content