Hi,
enabling the notifications_custom.module returns the following error message for me:
--------
warning: Invalid argument supplied for foreach() in notifications_custom\notifications_custom.module on line 118
--------
I enabled only the Custom subscription module (6.x-2.0-beta2).
With respect to Messagin/Notifications, I have the following modules enabled:
* Messaging (6.x-2.1): Messaging module, Messaging PHPMailer module.
* Notfifications (6.x-2.1): Notifications module, Content Notifications module, Notifications Autosubscribe module, Notifications UI module, Taxonomy Notifications module.
My Notification module settings are as follows:
Under the content subscription settings, I have the following settings enabled:
Active notification types: enabled for each content type seperatly (with different settings).
Tag-notifications: enabled for 2 of 4 vocabularies.
Under the UI settings I enabled the visible subscription types for threads only. The user account pages I enabled the 'Tag' setting under 'Manage own subscription'.
If the module works, I would allow the setup of 'compulsory' subscriptions and, even more helpful, the 'allocation' of typical notifications to users. - GREAT!
However, to fix the bug, I'd appreciate your help.
Best regards,
Felix
Comments
Comment #1
danepowell commentedI am not able to reproduce this - to be clear, you simply enabled Custom subscriptions at admin/build/modules/list, and as soon as you clicked "Save configuration" you got the error mentioned above?
Comment #2
maikeru commentedI also received the error.
I created a custom subscription, but didn't enter any fields.
Then I went to admin/messaging/notifications/content and the error displayed.
Once I added a field, the error disappeared.
Michael
Comment #3
danepowell commentedI followed the steps in #2 but am still not able to reproduce this error. Can you try the latest dev version- maybe this has been fixed? If you still get the error be sure to use the dev version of notifications/messaging as well.
Comment #4
jose reyero commentedClosing, no follow up.
Comment #5
wahavi commentedComment #6
oliverpolden commentedYep, I second that. Adding fields for a custom subscription requires the 'Save fields' button to be clicked before the actual field is saved.