Posted by tsvenson on February 12, 2009 at 9:36pm
Jump to:
| Project: | Comment closer |
| Version: | 6.x-1.3 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I really like the idea with this module. However, at least for me, it would be so much more useful if it was possible to configure the comment closing individually for each content type and also for each new node created.
Is this something that might be possible in the future?
Comments
#1
Currently you can select content types to close but it is include or not include. So you could say close blog,story,book after 180 but you couldn't close blog at 60, story at 180, and book at 360 days.
I would accept a patch to do that.
Thanks
Robert
#2
Sorry, but I am very new to Drupal, so at the moment I am quite busy learning everything the core, and several contributed, can do.
I do know a fair bit about PHP development, and I plan to do module development some time in the future. So far I have found existing modules for everything I need, but I am sure I will find something not already done lol. Your module seems like something I could help with, but unfortunately I can't give any promise on when that will happen.
#3
I would also be very interested in this feature.
#4
subscribe
#5
Let me make sure I understand. You want:
#1 is relatively easy; I see no reason to not include this.
#2 is considerably more difficult. First, we would need to find some place to store that interval and then do much more processing to expire individual nodes.
#6
Hi Nancy,
I like the basic idea with this module, but its to inflexible without being able to have more granular configuration options.
1 - Content types
Lets say you have two content types, news and articles. News are fresh, while articles has a much longer life span. Therefore it would be very useful to be able to be able to set a short time for when comments to news should be open, while for articles much longer.
2 - Individual nodes
Core does support being able to close comments completely on individual nodes, so that option is not needed. But lets say you create a node about something that ends a certain date. For example you have a competition and users can submit their entry in the comments. The competition ends at a specified date. For that it would be useful to be able to set that comments are closed at the same date as well.
Thinking of this, maybe it could be an idea to look into if leveraging the Rules module could be an idea to add flexibility. I have previously used the Node Limit Number module that in version 2 did just that. It added a lot of flexibility to it and enabled it to be used in many new ways that otherwise would have required patches.
#7
I am already at work on moving the age setting to the content type. I have no problem with that part of the request as it makes sense.
#2 is sort of do-able right now. The Scheduler module can set dates upon which a node is published or unpublished. Once a node is unpublished, obviously, comments may not be added. Or, once I have #1 working, you can create a new content type with a different lifetime. I understand the desired functionality; I'm just not sure yet how, or if, I want to do it in this module.
As far as Rules goes, I will not make this module depend on a fairly heavy module (that I have never used) when there is similar functionality in core (actions, triggers). Robert may decide he wishes to. I may look into Actions support at some point, but not right now.
#8
Committed to 6.x-1.x-dev.
#9
Automatically closed -- issue fixed for 2 weeks with no activity.