sjjenkins

Nope. Still seeing same issue. Just living with it by periodically restarting memcached.

Bump

I’m having the same problem as TKList.

For example, With two comments, the bubble is replaced with the words “2 Comments.” And because it’s part of the H1, it’s HUGE! ??

Another issue with this approach: it doesn’t address the bubble link on the blog’s home page. That still links to [post URL]#tc-comment-title.

@arniarni: As long as you have Canonical URLs working properly in your WordPress setup, there’s no negative SEO impact to paginating comments, because each comment page will point to the same canonical URL.

Hi, @d4z_c0nf. Thanks for the speedy reply!

LOL – DERP! That did the trick. ?? Thx!

@arnani: As long as you have Canonical URLs working properly, you won’t have to worry about SEO issues. Each “version” of the page with different groups of comments will still be “seen” by Google as the same URL.

@d4z_c0nf: Thanks for this excellent tip and code. But does it not work on the grid front page layout?

Comment pagination works great on one of my blog posts that has over 500 comments:

https://www.stevejenkins.com/blog/2013/01/my-cisco-linksys-e4200-dd-wrt-settings-for-max-speed/

But posts pagination doesn’t seem to appear on my home page:

https://www.stevejenkins.com/blog/

This is what’s in my functions.php:

// Paginate Posts
add_action('wp_head', 'my_post_nav');
function my_post_nav(){
    if ( !function_exists('wp_pagenavi') )
        return;
    remove_action( '__after_loop' , array( TC_post_navigation::$instance , 'tc_post_nav' ), 20 );
    add_action( '__after_loop', 'wp_pagenavi', 20 );
}

// Paginate Comments
add_action('wp_head', 'my_comments_nav');
function my_comments_nav(){
    if ( ! function_exists('wp_commentnavi') )
        return;
    remove_action( '__comment' , array( TC_comments::$instance , 'tc_comment_navigation' ), 30 );
    add_action( '__comment', 'wp_commentnavi', 30 );
}

// Add Google Tag Manager and Ad Javacsript to Header
add_action ('wp_head' , 'add_gtm_script');
function add_gtm_script() {
?>

I’d appreciate any suggestions. Thanks! ??

Replying here so that I can be notified if anyone comes up with an awesome suggestion. This is also something I’m looking for!

Wow. Apparently the new version switched the flag from “classroom” to “location.”

Why? No clue. That’s really dumb. It should have at least been backward compatible for a few versions. Upgrading from v2 to v3 should not have broken this much stuff.

Very frustrated, as are the clients whose website I was working on.

Ah – yes, I’m using CloudFlare so it minifies it. I just shut off that setting, does that make it any easier to check?

Hmm… doesn’t seem to. ??

https://fairwoodmartialarts.com/schedule/

Updated version fixes this.

Yep! Fixed worked in new version. Thanks. ??

I notice the new version says it “attempts” to update this, and the Changelog also says “** NOTE ** This update adds lines to the wcs_style.css file and may affect the schedule styling. Test on a development machine before updating.”

As I suspect is the case with most WordPress users, I don’t have a “development machine” for my blog. ?? Can anyone confirm that the new version fixes the “too wide” issue and doesn’t break anything else?

Thanks, Otreva. Issue wasn’t fixed when I upgraded to 1.2.5.1, but the same fix you explained did the trick. Developer may want to update his CSS to use something a more specific than #content.

Thanks again!

Did some more tinkering. It’s not a browser cache issue… but it IS a reverse proxy cache issue: CloudFlare.

This plugin breaks if a site uses CloudFlare (https://cloudflare.com). Which is a bummer, since CloudFlare is a great free service that speeds up and protects many of my WordPress blogs. Turning CloudFlare off for this domain fixes the problem, and turning it back on breaks it again. I’ve tried turning off all the Beta features inside CloudFlare, but even at the “lowest” setting, CloudFlare still breaks this plugin. ??

Eran: CloudFlare is free, so may I suggest that you try it out and see if you can figure out how to make future versions compatible? CloudFlare is growing like crazy, and even if I’m the first person to report this problem, I have a feeling I won’t be the last… ??