RSS feedComment Timeout 1.3 beta 1
The latest version of Comment Timeout is now available for immediate download. This fixes several bugs:
1. The plugin no longer raises a warning when installed on a server where allow_call_time_pass_reference is turned off in your php.ini file.
2. It is now possible to disallow hyperlinks in comments entirely, by setting the maximum number of hyperlinks to zero.
3. Hyperlinks that contain line breaks are now counted correctly.
One important note: If you are upgrading from an earlier version, and had set it to allow unlimited hyperlinks in your comments, it will now reject all comments containing any hyperlinks at all. To fix this, go to the options page and uncheck the box that says “Reject all comments containing more than 0 hyperlinks” — or alternatively, you can change the zero to some larger number of your choice.
Posted at 21:48 in WordPress plugins 
Welcome to my website. My name is James McKay and I am a
web developer from Horsham, West Sussex, UK.
20:05
Nice update, thank you for the fast feedback!
20:20
Thanks for update. Now no links in comments
03:49
James, thanks for this plugin, but I’m still getting an error that I got with the last version too:
Warning: Invalid argument supplied for foreach() in /home/[path path path]/wp-content/plugins/CommentTimeout.php on line 385
Warning: Invalid argument supplied for foreach() in /home/[path path path]/wp-content/plugins/CommentTimeout.php on line 394
Anyone else reporting such problems?
08:51
Which version of WordPress are you using? My other reports of this error come from people who are trying to use it with WP 1.5, which isn’t supported.
02:43
Currently at 2.0.2.
09:27
Many thanks for this - I have been looking for something similar for a while! Could an option to update the database (ornot) be included in some future release to make closure of posts for comment permanent? There might need to be an option to globally undo that of course!
17:07
I just started using this plugin a few days ago. Everything worked fine, until today. All of today’s posts have the comments disabled incorrectly. The problem seems to be with this plugin, since when I disable the plugin, the comments are enabled again. Any ideas?
21:04
Wonderful plugin, I’m just migrating to wordpress on a test system, and noticed an error (of omission) in function comment_form_bits($postID). In the 2nd part of it, the IPAddressCheck section, the closing bracket is missing, right after the $this->hash($_SERVER[’REMOTE_ADDR’]);. This was wreaking havoc with my layout, because it wasn’t closing the input tag, thus messing everything else up. Hope this helps, and keep up the good work!
07:39
thanks, I will test the new beta
08:16
I’m also having the same problem with Nathan *points up* I’m currently using WP 2.0.2. And BTW, the ZIP file I downloaded is labeled v1.3 beta, but the file (after extraction) is labeled alpha
09:10
I’ll get these two issues fixed in the next release of the plugin. Unfortunately I haven’t been able to give it much attention recently because of a fairly heavy workload combined with a bout of flu. Sorry too about the confusion with the version number — the file name is correct.
09:21
Yea sure, and do inform us when the next release takes place
And, why doesn’t my gravatar appear? Hmm..
21:30
Hey, I just wanted to say thanks for the plugin. I have more than 1400 posts, so it was generating tons of spam. I used your plugin to cut off comments after 120 days. Almost immediately, it cut my comment spam from 100-600 a day to about five or six. Wow!
23:11
Nathan/pelf: can you try version 1.3 beta 2 and let me know how you get on with it?
03:50
I downloaded and activated it and then logged out. But when I checked out my earlier posts (those published last year), I could still leave a comment. Did I miss anything here?
03:43
Looks like it works fine for me now, James. Thanks for all the hard work.
07:28
Err.. Why isn’t it working on my blog? I set it to close comment after 60 days, then signed out. But I could still leave a comment on a post I published in December 2006 (definitely more than 60d).
Perhaps this plugin clashes with some of the others I have installed, I’m not surprised.. LOL.
07:40
That could possibly be the case. You can find out by disabling all the other plugins on your blog and switching to the default theme. If that fixes the problem, switch your theme back and re-enable the other plugins one at a time until the problem reasserts itself. That should tell you where the conflict is.
11:31
OK, James, thanks for the suggestion (otherwise I wouldn’t haven known how best to do it)! =)