Ability for users to set per-node settings for comments?
| Project: | User Comment |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Dave Reid |
| Status: | closed |
How about a way to allow users to turn comments on and off for a specific node or type, and to turn approval on or off for a specific node?
Basically, I was hoping that this module would allow users to perform all normal comment tasks for their own content - just not other people's content, similar to how users can be granted privileges to edit or delete cck nodes they've created, without being given permission to edit/delete all nodes of that type.
Currently, if a node type is set to have comments turned on, then regardless of the user's wishes, people can leave comments on the node (although the user can set that node type to require their approval before comments appear).
It would be nice if users could be allowed to decide on a per-node, or even just per-type basis whether comments would be allowed at _all_ for their nodes.
Is this possible?
#1
@Coyote
That sounds like a useful feature, but I'm unfortunately tied up in work on the user relationships module, so I probably won't be able to get to it any time soon. If you can't wait and want to do the work yourself, feel free to submit a patch for review.
#2
Cool... I may try to do that, but I'm currently working on two and a half huge projects, so it won't be soon, if at all.
: )
Great module by the way!
#3
>>How about a way to allow users to turn comments on and off for a specific node or type, and to turn approval on or off for a specific node?<<
This would be a great feature, I'll wait for this :)
#4
I'll get a patch written for this, seeing as it makes sense to merge my newly-created Admin my content comments module into this one.
#5
Here's the patch that adds a 'administer comments on own content' that allows users to enable/disable comments on their own content. I'm not sure about the permission string name, it could maybe be more clear.
#6
Revised patch that fixes the error in usercomment_menu() with undefined access callbacks (they needed to be strings).
#7
Patch applies and works exactly as advertised. Exactly what I needed, hope it gets rolled in soon.
#8
I don't want to seems mad, but I liked to have the option to have a sidebar to scroll comment under every node.
#9
Subscribe
waiting for commit, patch works!
#10
Subscribe, 'must have' functionality for this module!
#11
Sorry for the lag applying this patch. I was hip deep in a project and then went traveling and blah blah blah.
I just applied the patch and a new release should be available once the packaging script does its thing. If you're impatient, you can pull from the DRUPAL-6--1 branch. I didn't test myself, so if there are problems, please re-open this issue or create a new one.
#12
Thanks very much gwen!
#13
Automatically closed -- issue fixed for 2 weeks with no activity.
#14
Is the patch applied on the dev. version on the front page? The dev. version on the front page has a date "2009-Jan-31", however gwen's "just applied the patch" message is posted 3 months later on April 22, 2009.
#15
Oops, I made some errors with tagging in CVS, so the packaging script wasn't updating the dev release. I modified so the packaging script should do its thing when it's ready. But if you're in a hurry, you can get the files from CVS (branch: DRUPAL-6--1).
#16
Looks like a 6.x-1.0-beta1 is available now. Marking as fixed.
#17
Automatically closed -- issue fixed for 2 weeks with no activity.