All the best,
Greg

The login details you supplied did not permit me to login to see what you are seeing. (Generally speaking, I’m thinking that posting login details in a public comment area is probably not a very good idea; who knows how many people tried to login before I did?) However, I would refer you to my reply to your previous note, which I’m guessing you have not yet seen, as you didn’t mention whether you had followed my suggestions:

previous reply

In addition, I noticed immediately that the front page of the site is suffering from severe rendering errors. Checking with the W3C’s markup validation service, it returned a full 68 errors and 37 warnings. Badly broken XHTML markup may impair the ability of the JavaScript counter to function by preventing the function from locating the page elements it needs.

So, I’d encourage you to have a look at the previous reply as well as to address the structural errors in the page coding, since the latter may impair both this plugin and many other plugins which use JavaScript to modify elements on the page.

All the best,
Greg

If you need admin rights to fix only tell me.

Since WordPress now displays the total number of words in a post right on the post editing page, I’m guessing that most blog authors will look to that when trying to keep their posts under a target size. By using that word count, blog authors can then tailor their own material and exercise their own judgement as to how best to deal with situations where they might be tempted to run over their preferred limit.

This is quite a bit different from the context which the plugin is addressing, where the comment form is completely open to the public, and the blog owner can’t expect every member of the public to share their aims or preferences with regard to what is left as a comment. The plugin enforces one part of the blog author’s preferences by processing long comments and either truncating them, putting them in the moderation queue, or dumping them as spam.

Structurally speaking, it wouldn’t really make sense to throw an oversized blog post into comment moderation — or the comment spam bucket — and similarly, I’m guessing that few blog authors would want a plugin abruptly truncating their posts for them.

All of which is to say: I appreciate what you’re asking, but I think there are better ways to limit lengths when we’re talking about actual articles posted by blog authors, as opposed to comments on articles left by members of the public.

All the best,
Greg

Would it be possible to adapt your Comment Length Limiter Plugin to be used as an entry length limiter for WordPress bloggers themselves. For example, If I wanted my blog entries to be limited to 5000 characters, could you see a way to adapt this to limit blog entries? How about blog entry titles? If your Comment Length Limiter Plugin could not conceivably do this, would you consider writing another plugin that would do so?

Thanks for your contributions to the WordPress community.

JB