[UNDEFINED module = notifications, key = title, type = digest, method = mimemail, search = notifications,digest,,]- [UNDEFINED module = notifications, key = digest, type = event, method = mimemail, search = notifications,event,,]

I'm trying to track down what's causing this error. It's happening in a digested email and there's no content getting built for the digests.

Any help steering me in the right direction would be greatly appreciated.

I'm using Messaging 6.x.2.x and Notifications 6.x.2.x-dev (// $Id: CHANGELOG.txt,v 1.1.2.11.2.51.2.19 2009/06/16 15:23:09 jareyero Exp $)

CommentFileSizeAuthor
#17 574918.patch1.02 KBowen barton

Comments

adam_b’s picture

adam_b commented
Title: error in mimemail email » UNDEFINED error in messages

I'm getting the same problem, but I'm not using mimemail (so have changed the title):

[UNDEFINED module = notifications, key = title, type = digest, method =
mail, search = notifications,digest,,]

- [UNDEFINED module = notifications, key = digest, type = event, method =
mail, search = notifications,event,,]

I am getting some correct e-mails, so I don't know why it's breaking only sometimes.
I'm using Notifications 6.x-2.1 and Messaging 6.x-2.1 on Drupal 6.14.

Any thoughts?

dlumberg’s picture

dlumberg commented

It seems to be a problem of an event (eid) getting deleted from the notifications_event table and not from the notifications_queue table so when it goes to digest it's building an empty event. Supposedly the error is getting built in the notifications.cron.inc file.

adam_b’s picture

adam_b commented

Okay, that sounds sensible, thanks. Has anybody worked out how to fix it? ideally permanently, but if not, in the short term?

askibinski’s picture

askibinski commented
Category: support » bug

Got the same error.

jose reyero’s picture

jose reyero commented
Status: Active » Postponed (maintainer needs more info)

I'd need more info about under which conditions this happens.

Try enabling messaging_debug and running the queue manually (Manage Subscriptions > Queue)

askibinski’s picture

askibinski commented

Looks to me like this issue was fixed in the 2.2 release.

duplicate of #552788: php undefined variable notices ?

jose reyero’s picture

jose reyero commented
Status: Postponed (maintainer needs more info) » Fixed

Thanks for reporting

Status: Fixed » Closed (fixed)

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

webservant316’s picture

webservant316 commented
Version: 6.x-2.x-dev » 6.x-2.2
Status: Closed (fixed) » Active

Re-opened the issue.

I have the same problem running notifications 6.x-2.2 with Drupal 6.19.

LiuShaz’s picture

LiuShaz commented
Version: 6.x-2.2 » 6.x-2.3

Same problem on 6.x-2.3 with Drupal 6.20

adeputter’s picture

adeputter commented

Same problem with 6.x.2.3 en Drupal 6.20.

franz’s picture

franz
any
Location Montréal
commented

After a lot of debugging, I found that this happens for me when creating a new group (using og_notifications). For some reason, a row with event id = 0 is added to the admin user in the notifications queue (probably because it is the group admin)

Still debugging

delty’s picture

delty commented

Subscribing - same issue here with a recent update to the latest version.

arosboro’s picture

arosboro commented

Getting this error too, does this only go to the admin of the group?

srees’s picture

srees commented

Much later than the last comment...surprised it isn't fixed!

I can confirm that this issue is still in existence. I can also confirm that the instance we saw this pop up was after a new group was created, as in comment #12.

gmaximus’s picture

gmaximus commented

I just run into this problem myself... using notifications 2.3 and latest version of Drupal... Also using Views saved searches...

owen barton’s picture

owen barton commented
Status: Active » Needs work
StatusFileSize
new 574918.patch1.02 KB

This isn't a fix, but the attached patch adds watchdog logging to aid in debugging as well as a variable (no UI) to aid in not frustrating users in the meantime.

srees’s picture

srees commented
Issue summary: View changes

This ticket was forever ago (and I KNOW we need to upgrade...) but it cropped up again for us. Tracing today's digest that had the UNDEFINED error, resulted in discovering a new node was created and immediately edited (new revision) to cause this. Not sure how to fix yet, but just putting that out there in case someone else can confirm.