Hi guys!

I get the following error when I try to run cron:
Fatal error: Call to a member function leftJoin() on a non-object in */sites/all/modules/l10n_update/l10n_update.check.inc on line 115

Lubas

CommentFileSizeAuthor
#5 l10n_update.check_.patch1.6 KBrobertgarrigos
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

int’s picture

I confirm this bug.

berkas1’s picture

I confirm this bug, too... Please, fix it:)

Jej’s picture

Exactly on the same line for me :)

Jej’s picture

I solved it like this (just changing the methods chaining):

$q = db_select('l10n_update_project', 'p');
$q->innerJoin('languages', 'l');
$q->leftJoin('l10n_update_file', 'f', 'p.name = f.project AND l.language = f.language');
$q->condition('p.status', 1);
$q->condition('l.enabled', 1);
// If the file is not there, or it is there, but we did not check since $before.
$q->condition(db_or()->isNull('f.status')->condition(db_and()->condition('f.status', 1)->condition('f.last_checked', $be
$q->range(0, $count);
$q->fields('p', array('name'));
$q->fields('f');
$q->addField('l', 'language', 'lang');
$q->orderBy('last_checked');
$result = $q->execute();

robertgarrigos’s picture

Status: Active » Needs review
FileSize
1.6 KB

This fixed the problem. Here is a patch to review.

lionheart8’s picture

Hi
How exactly does one (php layman) apply this patch? Does one paste it somewhere (where, line?) in that file? Exactly which elements of the patch are "pasted" ... ?
Tried to gamble doing that but could not get it right. ;)
Regards

Lubas’s picture

wasare’s picture

Status: Needs review » Reviewed & tested by the community

The patch #5 worked for me.

Thanks!

Anonymous’s picture

When will create a new dev Version the last for the Drupal 7 is from 2010-Dec-09!!

Chris

int’s picture

Priority: Major » Critical

this bug is critical, since break core functionalities like cron and other things...

Gábor Hojtsy’s picture

Status: Reviewed & tested by the community » Fixed

Great, committed, thanks.

Status: Fixed » Closed (fixed)

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