Posted by laceiba on August 20, 2009 at 6:27pm
Jump to:
| Project: | Comment closer |
| Version: | 6.x-1.3 |
| Component: | Code |
| Category: | bug report |
| Priority: | major |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Howdy Folks,
Comment closer is locking topics in my forum even though I have "forum" unselected in my comment closer settings. This is not an issue with the initial setup. This is something that is ongoing. I unlock the topics, but comment closer shuts them down again. I want to close down all comments on all the other nodes except the forum. I want those to remain open indefinitely. I am using Advanced Forum, if that makes any difference. Any ideas?
Comments
#1
I have temporarily disabled this module until a fix is available. I barely know any PHP, but I might take a look at the code to see if I can make sense of anything. I may also check out the Rules module to see if I can accomplish the same thing with that.
#2
I had this same issue. The solution is very simple. There is a line in the module code that reads
$query .= " AND type IN (". db_placeholders($process_node_type_list) .")";This line should read instead
$query .= " AND type IN (". db_placeholders($process_node_type_list, 'text') .")";The problem is that the default placeholder is 'int', but the node type is 'text'. Unfortunately, once the module has changed comments to read only, you either have to run your own SQL on the server to set it back to read/write for the content that was incorrectly changed, or you have to change it back node by node through the Drupal interface.
#3
Ran into a similar problem, so can confirm the bug it doesnt abide to the content types that have been specified. Trying the above fix, will report back with the results.
#4
See also #945032: Incorrect use of db_placeholders
#5
Committed to 6.x-1.x-dev
#6
Automatically closed -- issue fixed for 2 weeks with no activity.