Posted by AFowle on April 13, 2009 at 6:58pm
Jump to:
| Project: | Organic groups |
| Version: | 6.x-2.x-dev |
| Component: | og_notifications |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Zen |
| Status: | closed (fixed) |
Issue Summary
This error has occurred several times when I have pressed the "Run Process" button in the queue manager.
warning: array_key_exists(): The first argument should be either a string or an integer in /host/sites/all/modules/notifications/notifications.module on line 671.
I have not managed to pin down the circumstances yet and I am sorry I cannot provide more details - I was actually trying to test OG 6.x-2.0-rc1. May be an interaction between the two.
Comments
#1
See also http://drupal.org/node/360291#comment-1470248 and wherever this comment gets reposted!
#2
We got the same problem with OG 1.4:
warning: array_key_exists() [function.array-key-exists]: The first argument should be either a string or an integer in modules/notifications/notifications.module on line 671.
#3
same problem with OG 1.4
subscribing
#4
og 1.4??
Added some notes about og/notifications compatibility in this project's front page.
Anyway I think this is an issue with notifications_og. The function _og_notification_check_message() just returns TRUE / FALSE so it is not used properly in og_notifications_message_alter().
Btw, couldn't we use a better method for this message template rewriting? which other hooks do we need?
#5
D6.10
M&N 6.x-2.0-beta5
OG 6.x-2.x-dev (2009-Apr-24)
This combination is a huge improvement, for this error and others. Not quite perfect though. I think remaining errors are in messaging and OG notifications, so I'll post there.
#6
Making the title more explanatory. I keep getting bug reports in Notifications about this. We need to fix it before next release.
#7
Hi,
I am fixing this issue, I using these modules:
- OG 2.x (today tarball)
- Notifications 2.0
Trying to get your bugs reported, but no luck. Bug fixed?
Thanks
#8
#9
I am sorry I do not understand your comment, but later versions do work better as you have discovered.
As for the "Priority" it should be "critical" according to the handbook (see link near "post new comment") and I don't think it was necessary for you to change it - Jose Reyero, main author of the module, chose critical himself.
#10
Is this fixed if using the 2.x versions of both ?
#11
Yes it seems to be. I'm currently using
Drupal 6.11
OG 6.x-2.x-dev (2009-May-02)
M & N 6.x-2.0
Trouble is there are so many variations to try with just these modules, then further interactions with views etc. So I can't say there are no problems, but this combination is a significant advance.
#12
Subscribing.
Is this going to be solved at 6.1.x versions too?
#13
I now work with :
Drupal 6.11
OG 6.x-2.0-rc1
M & N 6.x-2.0
and I got this error :
warning: array_key_exists() [function.array-key-exists]: The first argument should be either a string or an integer in .../modules/notifications/notifications.module on line 761
after commenting with immidiate notifications on.
So I guess this problem wasn't fixed, or should I try the 2.x-dev version of OG ?
#14
It´s not fixed on 2.x version either (I didn´t tried the dev, only the stable one).
#15
Same issue using 6.x-1.3. subscribing.
#16
I tested this with the latest devs, delivery method = Web and send interval = 2 minutes with about 20 notifications queued. I could not reproduce the error. Please test again and provide detailed steps for reproduction of the issue, if need be.
This is non-critical.
-K
P.S. 63reasons: If you aren't working on a solution to an issue, please avoid setting yourself as the assignee.
#17
We were still awaiting cooperation on the issue, but go ahead if you can get it before us.
#18
@ Zen
I consider this fixed (as the original poster). I haven't seen the problem for some time, in the rapidly evolving mix of OG and M&N. See post #11. I am now using
Drupal 6.12
Messaging 6.x-2.0
Notifications 6.x-2.0
Organic groups 6.x-2.x-dev (2009-May-14)
As others have said above, it would be more comfortable to have a released version of OG rather than the dev. I don't know what the practice is for closing an issue before the released version?
I am very grateful to the developers of both sets of modules.
#19
Adrian, thanks for the confirmation. There will very likely be an RC out RSN.
-K
#20
Automatically closed -- issue fixed for 2 weeks with no activity.
#21
subscribe