#154 I'm told to slow down when I wasn't moving too fast
Closed: Fixed None Opened 8 years ago by mattdm.

A couple of times while commenting, I got an interstitial saying that I was commenting too fast and need to slow down. The first time, I wrote a one-liner and so maybe didn't hit some some threshold, but the second one was several paragraphs with thought as I wrote.

I was able to press back and my writing was preserved, but I did have to submit it again. This seems like a pretty bad experience for users.

This might provide some insight into the problem. I wonder if other folks are hitting the same problem?


Replying to [comment:1 jzb]:

This might provide some insight into the problem. I wonder if other folks are hitting the same problem?


Ah, I bet that the last comment there nails it -- it identifies a problem when using a load balancer. I wonder if all Wordpress instances running in OpenShift are subject to this.

Got it again, and this time I noticed that another comment did come in a few seconds before. So that's clearly it.

We do currently have load balancing setup for the magazine to handle the traffic that comes in. I will get with some of the WordPress guys I know in irc and see what they suggest and then see what our openshift guys here in the tower suggest. I will keep this ticket updated. The load balancer is needed because of the higher traffic flow periods that the site occasionally gets.

JZB as far as all WordPress instances, no when the application is created you have the option to turn on load balancing. On the old site it was not enabled. This is the first time I have heard of the site giving this issue. I will check into it with the teams i mentioned in the last comment :)

Yeah, at quick glance the fix in the link above of using X-FORWARDED-FOR headers seems right (and probably should be the default for all wordpress on openshift).

Getting reports of this hitting people other than me trying to comment.

Going to restart the Instance tonight when the traffic is lower and see if that will provide a short term fixed at least for the comments. I am working with the Openshift guys to see what we can do about this issue.

I have applied the update JZB found and restarted the Magazine instance. I will keep this bug open for a few days, please let me know if you run into this issue again. If we are good for a few days I will go ahead and close it :)

I have watched the logs for about 10 minutes after I restarted the instance and dont see any issues. I have also made a backup of the comment.php file incase we do run into issues down the road.

Me and Mattdm met up on irc and tested the site with the new patch I put in last night. Everything is working :) So I am going to close this ticket. The site is much more responsive since the restart. I have also turned off the Slideshow plugin as I was going through the logs and it was slowing queries down, hence when you went to the site it would take a second or two then load the content. I talked to mattdm and he said the site looks nice without it. I think once we get some new artwork for the slide show then we can test a few different slideshow plugins and find which one works the best for us. I do have an active design ticket open for more artwork for the site.


This is happening again -- I think probably the fix got lost in the recent theme update.

Hey Chris, can you check if the patch is still applied? I'm getting the error still.

Fixed the following in the comments.php removing the $ip from the db_flood control

function check_comment_flood_db( $email, $date ) {
global $wpdb;
if ( current_user_can( 'manage_options' ) )
return; // don't throttle admins
$hour_ago = gmdate( 'Y-m-d H:i:s', time() - 3600 );
if ( $lasttime = $wpdb->get_var( $wpdb->prepare( "SELECT comment_date_gmt FROM $wpdb->comments WHERE comment_date_gmt >= %s AND ( comment_author_IP = %s OR comment_author_email = %s ) ORDER BY comment_date_gmt DESC LIMIT 1", $hour_ago, $ip, $email ) ) ) {
$time_lastcomment = mysql2date('U', $lasttime, false);
$time_newcomment = mysql2date('U', $date, false);
$flood_die = apply_filters('comment_flood_filter', false, $time_lastcomment, $time_newcomment);
if ( $flood_die ) {
do_action('comment_flood_trigger', $time_lastcomment, $time_newcomment);

        if ( defined('DOING_AJAX') )
            die( __('You are posting comments too quickly.  Slow down.') );

Login to comment on this ticket.