You are here: Home » Website Maintenance » Upgraded to WordPress 2.8.2, long posts getting cut off

Upgraded to WordPress 2.8.2, long posts getting cut off

by Dave Doolin on July 22, 2009 · 0 comments

(Reading time: 2 – 2 minutes)

Website In A Weekend was upgraded to WordPress 2.8.2 release a day or two ago. The 2.8.2 release fixes a cross-site scripting (XSS) security problem. I’m not sure how dangerous that issue was for most people.

I noticed when I went to check today’s article “Using Google Analytics to Measure Traffic to Your WordPress Blog” that there was no text showing either on the website or in the RSS feed. Which is bad. Really bad. The text was all there in the post when I edited it.

After some investigation, it seems that WordPress won’t display any of the post at all if it’s over about 1690 words.

I “fixed” it by shortening the end of the post, so you will now be able to read it if you missed it in the RSS feed earlier today.

The entire post is saved in text format elsewhere, and I’ll add the chopped out part later if possible.

There isn’t yet any report of a similar problem on the 2.8.3 task list, but I’m going to keep watch.

In the meantime, if you haven’t upgraded yet, don’t.

Scheduling issues coming to light

The problem with a scheduled post getting published immediately is now in the bug tracking system, and reports from others with the same problem are starting to surface. This is typical: today’s bugs take a couple of weeks to crawl up Google search results. Here’s more information:




Would you like more? Send me a letter...
"Hi Dave,
Website In A Weekend seems pretty cool. I'm serious about this WordPress and web stuff, and I'd like to keep up with it. My name is and my email address is . I'm comfortable with email newsletters. I know you will protect my privacy, and that I can unsubscribe at any time. "

Leave a Comment

CommentLuv Enabled

Previous post:

Next post: