jesseg

The issue seems to also happen when you are running WP on a VMWare hosted system. VMware has always been wonky about time, after about three weeks my system clock is about a day ahead. If I reboot it at that point it resyncs with the VMWare ESX server clock, and boom, my posts are dated a day or two in the future.

I disabled the flood-trigger in mine by commenting out the following lines in ./wp-includes/comment-functions.php

// do_action(‘comment_flood_trigger’, $time_lastcomment,
$time_newcomment);
// die( __(‘Sorry, you can only post a new comment once
every 15 seconds. Slow down cowboy.’) );

And it seems to work wonderfully – (it still checks the timestamp, just doesn’t care or act on what it finds) if I am the recipient of a true flood I’ll probably regret having done this, but as I’ve had a handful of users complain about this particular bug, I felt it more prudent to remove the limitation.