Viewing 13 replies - 1 through 13 (of 13 total)
  • Thread Starter nickaster

    (@nickaster)

    Interesting. I think this may be a conflict with the HeadSpace plugin. I will report on their board

    Thread Starter nickaster

    (@nickaster)

    So… turns out this is not Headspace, nor, by trial and error does this get fixed by deactivating any plugins. Kinda driving me nuts. Has anyone seen anything like this? Now it only displays ONE comment even though the display suggests it’s showing 1-20.

    Thanks!

    Have you tried switching to the default theme to rule out any theme-related problems?

    Thread Starter nickaster

    (@nickaster)

    Oh good lord. You’re right. That’s what it is. Why would a theme affect the back end? That seems really dodgy. It did not originally have this problem, so I assume changes I’ve made at some point did this. But god only knows how to diagnose… would you even have a clue as to where to begin?

    Anything that includes additional functionality (especially javascript) can affect the back end. Plugins tend to be the obvious culprits but I have seen themes create problems sometimes too.

    You could try going through the theme and pulling out any javascript first, then start reducing the functions in functions.php but, to be honest, you may have very little of the theme left by the time you’re finished.

    Thread Starter nickaster

    (@nickaster)

    What’s puzzling is that the first time I noticed this problem it seemed to be connected to the Headspace Plugin. By disabling that plugin temporarily, the problem went away.

    A few weeks later, that solution stopped working. Now, only the theme disabling, as you suggested above, does the trick. Also, I have not made any substantial changes to the theme in a while, so I’ve no idea what changed to cause this, the original theme did not conflict.

    By ‘removing’ javascipt, where would I go? Into the headers? There’s loads of JS on the site, mostly caused by plugins. If I so much as touch functions.php it tends to nuke the site, so I’m wary of that approach

    Can you think of anything that “accumulates over time” that might be screwing with my set up?

    Are you running Headspace again now? If so, it might be an idea to deactivate it. I’m pretty sure I’ve heard of it causing problems in 2.8.

    In fact, deactivate all plugins then try reactivating them one by one and run each for a few days (if possible) to ensure that it’s not creating any issues.

    Thread Starter nickaster

    (@nickaster)

    Utterly bizarre… so I’ve been turning plugins on and off and now, it’s WP-Polls that fixes the problem. But… then suddenly it stopped working. Then turning headspace on/off fixed it… now it’s skunked totally again regardless of the plugins. So there’s something psychotically unstable going on in there.

    You think this is just a crap theme?

    Have you tried switching to the default theme? Do the comments re-appear? Have you tried repairing your database?

    Thread Starter nickaster

    (@nickaster)

    Yeah, like I said before, if I switch to the default theme it does fix it (however, the theme didn’t cause problems before). I have yet to try the Javascript concept you mentioned. What’s the best way to repair the database? Is that something I do at the host level via phpMyAdmin? Or is there a plugin for that?

    Thread Starter nickaster

    (@nickaster)

    Thanks for your help. SO… I did the “check table” command for all tables on the database and everything says OK. However phpMyAdmin spit out the following at the end:

    Problems with indexes of table bb_meta
    More than one INDEX key was created for column object_type
    Problems with indexes of table wp_comments
    More than one INDEX key was created for column comment_approved
    Problems with indexes of table wp_role_scope_rs
    More than one INDEX key was created for column max_scope

    Are any of those things non-standard problems I should be aware of and do something about? I realize two of the three are something else, but the wp-comments one might be related!

    Thanks!

    Thread Starter nickaster

    (@nickaster)

    Anyone got any idea what that INDEX key stuff is? I guess there’s nothing wrong with the DB?

    Those warnings mean that you have duplicate indexes. They shouldn’t cause any failures but might negatively effect performance.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Incomplete Comments Display (on backend)’ is closed to new replies.