Trying to get OG set up can't get past Messaging and Notifications.
After enabling Notifications UI, the following errors appear on front page (not on admin pages):
warning: implode() [function.implode]: Invalid arguments passed in .../public_html/drupal-5.6/sites/all/modules/notifications/notifications.module on line 340.
warning: implode() [function.implode]: Invalid arguments passed in .../public_html/drupal-5.6/sites/all/modules/notifications/notifications.module on line 341.
user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '))' at line 1 query: SELECT s.*, f.* FROM notifications s INNER JOIN notifications_fields f ON s.sid = f.sid WHERE s.uid = 1 AND event_type = 'node' AND (()) in .../public_html/drupal-5.6/includes/database.mysql.inc on line 172.I'm also having trouble with using Send module and Messaging module together. Send has always worked great but enabling simple mail in Messaging results in blank pages on Content Types edit pages. Any clues are appreciated. BTW, the site that shows the errors above has never had send enabled. I working in a clean install to try to work through the Messaging/Notifications issues.
Drupal v 5.6 PATCHED to 5.8 (4 changed files)
MySQL v5.0.15a
PHP v5.2.6
Comments
Comment #1
moshe weitzman commentedPerhaps related - I see "warning: in_array() [function.in-array]: Wrong datatype for second argument in /Users/mw/contributions/modules/notifications/notifications_ui/notifications_ui.module on line 332." Am also using OG with our og_notifications module and simple messaging
Comment #2
moshe weitzman commentedThis happenned when I had not setup the behavior on the content type admin form.
Comment #3
Saganesque commentedComment #4
jose reyero commentedThese warnings are due to incomplete parameters or set up. However, I've added some additional parameter checking in the code so no more warnings are thrown.
See also http://drupal.org/node/272917
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.