Closed (won't fix)
Project:
Notifications
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
21 Apr 2008 at 14:34 UTC
Updated:
24 May 2010 at 23:17 UTC
Jump to comment: Most recent file
Comments
Comment #1
thepanz commentedHi, this is a alpha patch that enable content-type subscribing permissions. (I added also an .install file, for settings clearing )
Maybe I'm missing something else, but "it simply works" :)
There is an undocumented $op in hook_notifications() called 'access', have I to add checks also there?
Regards!
Comment #2
thepanz commentedSorry, I left in some debug messages!
New patch
Comment #3
jose reyero commentedThe idea sounds good. But about the implementation it looks like making the options yet more complex, while we are trying to go the other way, making them simpler.
Why don't you just replace the 'subscribe to content' permission for multiple 'subscribe to xxx' for each content type?. That combined with the 'subscribe to content type' permission would allow enough flexibility IMHO and would be an acceptable solution.
Comment #4
mstef commentedOn a very related note, if a user were to subscribe to a certain content type, does the notifications modules check if the user has read permissions to the newly created nodes before notifying? From a few quick tests it seems that it does, but I thought I'd ask just to make sure..
Thanks
Comment #5
jose reyero commentedAbout permissions, yes, node view permissions are checked.
No more features for 2.x branch. They will be welcomed for 4.x