desipio

OK, I fixed it. The <15 is in a different spot in 2.5 but it’s still in wp-includes/comment.php.

/**
* wp_throttle_comment_flood() – {@internal Missing Short Description}}
*
* {@internal Missing Long Description}}
*
* @since 2.1.0
*
* @param unknown_type $block {@internal Missing Description}}
* @param unknown_type $time_lastcomment {@internal Missing Description}}
* @param unknown_type $time_newcomment {@internal Missing Description}}
* @return unknown {@internal Missing Description}}
*/
function wp_throttle_comment_flood($block, $time_lastcomment, $time_newcomment) {
if ( $block ) // a plugin has already blocked… we’ll let that decision stand
return $block;
if ( ($time_newcomment – $time_lastcomment) < 15 )
return true;
return false;

I changed this line:

if ( ($time_newcomment – $time_lastcomment) < 15 )

to: if ( ($time_newcomment – $time_lastcomment) < -3800 )

No more posting too quickly error.

I’m still not sure why flood control isn’t something you can adjust through Options, though.

Thank you for your help on both questions. It’s my readers who are asking for them. So they will have brought it upon themselves.

Actually, they never post their real e-mails. They enjoy making up phony e-mail addresses to go with whoever they pretend to be posting as (during Cubs’ games…usually the players making pithy comments about the games) and like to be clever, and often vulgar e-mails. I will make sure to warn the innocent however, not to use real e-mail addresses.

Again, thanks.

Here’s another of the things I don’t get though. This morning, I restored WordPress 1.2.2 and everything worked just fine. Could it be that all I have to ask them to do is to allow the upgrade process to work (raise the file size minimum temporarily), and then WordPress 1.5 will hum along at its space saving best after that?