I don't know why its happening but I get this message from Notifications in my error log:

implode() [<a href='function.implode'>function.implode</a>]: Invalid arguments passed in /home/cctvcamb/public_html/sites/all/modules/notifications/notifications.module on line 1432.

Does this mean anything to anyone? It so far doesn't seem to effect anything in terms of sending notifications to users.

CommentFileSizeAuthor
#14 notifications-453498-14.patch1.29 KBkaare
#13 453498.patch734 bytesarthurf

Comments

toddwoof’s picture

toddwoof commented

I'm getting the same error -- actually, lots and lots of the same error -- after upgrading to 6.x-2.0. Anyone have any ideas? I've been trying to figure out the new settings arrangement, based on the idea that I might be missing something in the configuration, but can't find anything obviously wrong with how I have it configured.

toddwoof’s picture

toddwoof commented

Some additional details:

Running D 6.11 with Zen theme.
Updgrading to Notifications/Messaging 2.0 results in many, many implode errors, maybe on every hit.
It seems to be related to hits by anonymous users.
Switched to Bluemarine to see if the theme was the problem, but no change.
Reverted to Notifications 1.1 and Messaging 1.1 and errors stopped.

Identical behavior on my development site.

swellbow’s picture

swellbow commented

Also getting this. Confirming it happens with anonymous users but not logged in users. I have notifications disabled for the particular content type, but this function still runs, passing a $type of 'unsubscribe'. Since the user is anonymous, they have no subscription information, and implode runs on an empty array.

It's being called by notifications_token_values ($type = user) if that helps any.

seaneffel’s picture

seaneffel commented

Here is more information:

I'm using OG 6.x-1.3 and Notifications 6.x-2.0.

I have a long chain of errors for each time a user submits content to an OG group. In my use case, users can only be subscribed to new content published in OG groups. The Drupal error log around the time of each of these postings started with these messages.

When a user submits a node, there is an error for each outgoing notification (one for each subscribed user):

array_key_exists() [<a href='function.array-key-exists'>function.array-key-exists</a>]: The first argument should be either a string or an integer in /home/cctvcamb/public_html/sites/all/modules/notifications/notifications.module on line 761.

And then another error, also for each outgoing notification:

implode() [<a href='function.implode'>function.implode</a>]: Invalid arguments passed in /home/cctvcamb/public_html/sites/all/modules/notifications/notifications.module on line 1432.

The notifications do get sent to the users, but the error log is flooded with this pair of errors. Sometimes groups with 100 members the error log is staggeringly large.

Can anyone explain why this is happening?

Rosamunda’s picture

Rosamunda commented

subscribing

jose reyero’s picture

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

The OG problem is a different one, see http://drupal.org/node/432556

So does this happen without OG? And which page causes this error? (viewing a node, submitting a comment.... )

swellbow’s picture

swellbow commented

For me this is happening without OG when users submit a new node (of a custom type). This node submit is also running validation api and mollom, but they don't seem to be involved as far as this error is concerned.

I have not seen this behavior with comments.

seaneffel’s picture

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

Yes, it is still happening without the OG_notifications module. And its also the same as swellbow says, its not generating this error when submitting comments.

dicreat’s picture

dicreat commented

I have the same error.

boonep’s picture

boonep commented

subscribing

Gerard McGarry’s picture

Gerard McGarry commented

It happens independently of OG for me - like when a blog comment is posted or a type of content that can be subscribed to. Although, my feeling is that this started *before* the 2.0 version.

Mike Gogulski’s picture

Mike Gogulski commented

subbing

arthurf’s picture

arthurf commented
StatusFileSize
new 453498.patch734 bytes

The issue with line 761 seems to be that $sid is not set, but the function array_key_exists($sid, $cache) requires that $sid have a value. If I understand this correctly, this patch should fix it.

kaare’s picture

kaare
him/his
Primary language Norwegian Bokmål
Location Tromsø
commented
StatusFileSize
new notifications-453498-14.patch1.29 KB

The original post is related to the same problem I had, issue #484728: Incomplete test causing implode() to fail in notifications_get_link(). and is caused by an undefined $elements variable in notifications_get_link().

Could you try this patch (and read the explanation in #484728: Incomplete test causing implode() to fail in notifications_get_link()) and verify that this works?

dicreat’s picture

dicreat commented

Patch #14 work for me. Thanks.

swellbow’s picture

swellbow commented

Patch #14 works for me as well. Thanks a lot!

jose reyero’s picture

jose reyero commented
Status: Active » Fixed

Done some fix, following the lines of #14

wxman’s picture

wxman commented

Every time I got the error mentioned above, I also got this one on my apache log:
Call to undefined function pathauto_cleanstring() in /var/www/clients/client2/web2/web/sites/all/modules/custom_breadcrumbs/custom_breadcrumbs.module on line 324
I don't know if they're connected, but I'm going to try the patch today.

Status: Fixed » Closed (fixed)

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