warning: Illegal offset type in isset or empty

I was also seeing this when "Content Notifications" was enabled.

Then I noticed that my Notification_Extras module was 6.x-2.0-beta :-P

Upgraded that to 6.x-4.0-beta5 and the error went away.

Im getting this on line 611
notifications 6.x-4.x-dev

Am using 6.x-4.0-beta7 of notifications module and am seeing the same error message at line 612 when I try to add a node to the site. This message only appeared after I enabled 'content notifications'. I currently do not have notifications_extra installed. I will install and report back ...

Adam

Tried enabling (one at a time):
'cck notifications'
'nice links'
'comment subscriptions'
and
'messaging notifications'

(all 6.x-4.0-beta5)

Error message did NOT disappear. The issue persists. Will have a closer look at the code. @FoxHaven - which notification add-ons modules do you have enabled?

Regards

Adam

We have the following enabled:

Custom subscriptions 6.x-4.0-beta7
Digest notifications 6.x-4.0-beta7
Notifications UI 6.x-4.0-beta7
Notifications 6.x-4.0-beta7
Taxonomy Notifications 6.x-4.0-beta7

On the one hand, we don't have any warnings except:

Duplicate tokens
The following tokens are defined by multiple modules and may cause problems when performing token replacement.
node:node-url (defined by modules: token, notifications_content)

On the other hand, our subscriptions still don't work :-/

Thanks Foxhaven

Interesting you had a duplicate token message - that token (node:node-url) was not 'replaced' (correctly) for me in the test e-mails. Instead of getting the URL I just had the word 'Array' instead. I was able to get round this by using PHP instead (preferred) or assembling the URL from the base url and the nid.

HOWEVER I have since dropped down to the 2.x versions of messaging and notifications (decided I (the client) could live without anonymous notifications for now). All of my errors disappeared and token replacement started to work for node:node-url. (LOL - but still can't get the views saved search notifications to work - http://drupal.org/node/675980#comment-4729882, but that another story)

Adam

same here - using 6.x-4.x-dev - subscribing

same here - line 612 with 4.0 beta7

the offending lines make me wonder - do i care? just call it true and be done with it? what's going to happen then? i'm only using notifications to go along with signup cck... so there's only one content type that's gonna have notifications on it anyhow... any thoughts?

/**
* Check whether we have enabled events of this type
*
* @param $key
* Event type key
* @param $default
* Default value to return if not set
*/
function notifications_event_enabled($key, $default = TRUE) {
$info = variable_get('notifications_event_enabled', array());
$status = isset($info[$key]) ? $info[$key] : $default;
// If this has a parent type, will be enabled just if parent is
if ($status && ($parent = notifications_event_types($key, 'parent'))) {
return notifications_event_enabled($parent, FALSE);
}
else {
return $status;
}
}

Subscribing for 6.x-4.x-dev

warning: Illegal offset type in isset or empty in ...\modules\notifications\notifications.module on line 611.

need the 6.x-4.x-dev since it has the node templates for content type not available in v2 of notifications and messaging

Nevermind just like #1, had to update the notification extra to 6.x-4.x-dev and the error went away.

i'm getting this same error on the same line, using notifications 4.0 beta 7, and i believe my culprit was Views Saved Searches module... i'm thinking this is due to incompatibility with that module with Notifications 4.0... but I have yet to completely understand that. Does anyone have Views Saved Search (Subscriptions) module working with Notifications 4.0 (Beta 7)?

This error was triggered here when enabling Organic Groups Notifications automatically required the installation of Content Notifications, which in turn then produced two identical errors once Modules reloaded. Then when Organic Groups Notifications was disabled, one error went away. Then after disabling Content Notifications the error remained but went away after Content Notifications and Organic Groups Notifications were uninstalled.

Using:
Notifications 6.x-4.0-beta7
Content Notifications 6.x-4.0-beta7
Organic Groups Notifications 6.x-2.2

I did not test without OG Notif., so it may have nothing to do with the errors, dunno.

Did anyone ever get Views Saved Searches working with Notifications 4.0 (Beta 7)...? I'm getting the same error message...