Closed (fixed)
Project:
Comment closer
Version:
6.x-1.3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Aug 2009 at 15:59 UTC
Updated:
2 Nov 2010 at 16:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
Tally commentedWould it not be better to have the fresh install defaults set up so that nothing is changed? It seems that the issue many have is the module installs with defaults that are not wanted by every user.
If you want to keep the defaults, then a checkbox to enable the module is a feature I see with other modules, for example, Boost.
Comment #2
geerlingguy commentedI created a quick module to do this on my sites, and by default, it won't disable any comments until you tell the module which for which node types you'd like to disable comments. This way it's a bit of a safer default.
It's pretty simple, but it gets the job done for my needs.
Comment #3
johnalbinConsidering how long this issue has been open (I understand not having time to work on your module), defaulting to "don't close any comments" is an easier and better option.
A "activate" button would be confusing from a UX perspective. Also, you'd have to track whether that button has ever been pressed; a DX annoyance.
Comment #4
rmiddle commentedI need to get this one done.
@3 JohnAlbin
My plan was for a simple check box with "Enabled" if checked it runs if not checked it doesn't
Thanks
Robert
Comment #5
nancydruHere you go, Robert. It allows "Never" to be a cycle time, and is the default.
Comment #6
geerlingguy commentedUpdating title... hard to understand based on the title, still :-/
Comment #7
nancydruWorks for me.
Have you tested the patch?
Comment #8
nancydruCommitted to 6.x-1.x-dev
Comment #9
nancydru