Disheartening WordPress Bug?


I don’t know if this has happened to anyone else…

I just finished writing a blog post that I’ve been working on for the last three days (total time writing and editing: about 3.5 hours).

As an afterthought, I decided to paste a funny image into the body of the post, so I uploaded the image using the controls on the ‘post.php’ page. After clicking on the thumbnail and choosing ‘Send to Editor’, the image was pasted into the text, and I published the article.

I was redirected to the publicly-viewable page containing the new article, only to discover that the last 75% of the text in my message had completely disappeared.

Ugh.

I tried clicking the BACK button in FireFox to retrieve any previous version of my post, but despite FireFox’s current memory consumption (236,340 KB of RAM, ostensibly used for caching of pages in the HISTORY), all of the historic versions of my post had been replaced with the new truncated version.

Shit.

Now there’s nothing left for me to do but re-write.

Maybe I’ll get to it tomorrow. Maybe not.

In the mean time, I think I’ll install the WordPress Versioning Plugin, so that in the future, when this inevitably happens again, I can just perform a rollback.

socially-bookmark this article:
Add 'Disheartening WordPress Bug?' to Del.icio.us Add 'Disheartening WordPress Bug?' to digg Add 'Disheartening WordPress Bug?' to FURL Add 'Disheartening WordPress Bug?' to blinklist Add 'Disheartening WordPress Bug?' to My-Tuts Add 'Disheartening WordPress Bug?' to reddit Add 'Disheartening WordPress Bug?' to Feed Me Links! Add 'Disheartening WordPress Bug?' to Technorati Add 'Disheartening WordPress Bug?' to Socializer 

6 Responses to “Disheartening WordPress Bug?”

  1. NZ Says:

    “In the mean time, I think I’ll install the WordPress Versioning Plugin, so that in the future, when this inevitably happens again, I can just perform a rollback.”

    Or use one of the desktop blog editors like BlogJet or something…

  2. Bill Keller Says:

    Dang, I just switched *to* wordpress.

  3. benji Says:

    Well, Bill, I should mention that (aside from this one issue), I’ve been extremely happy with WordPress.

    Incidentally, I just intalled the Versioning plugin, and it doesn’t work correctly with WP version 2.0+. Even if it did work correctly, it doesn’t provide a diff (or any other view of the versions), so you have to perform rollbacks blindly. Yikes.

  4. Kisakookoo Says:

    Hi! Why I can’t fill my info in profile? Can somebody help me?
    My login is Kisakookoo!

  5. Jeromy Says:

    Great plugin man, just ran into a problem after making the latest wordpress 2.3.2 upgrade. When trying to save a page or a post, I’m greeted with this error:

    Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /mnt/Target01/340035/346509/www.experiencedynamics.com/web/content/wp-content/plugins/wp-versioning/versioning_19.2.php on line 61

    Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /mnt/Target01/340035/346509/www.experiencedynamics.com/web/content/wp-content/plugins/wp-versioning/versioning_19.2.php on line 63

    Warning: Cannot modify header information - headers already sent by (output started at /mnt/Target01/340035/346509/www.experiencedynamics.com/web/content/wp-content/plugins/wp-versioning/versioning_19.2.php:61) in /mnt/Target01/340035/346509/www.experiencedynamics.com/web/content/wp-includes/pluggable.php on line 391

    Which of course disappears after deactivating the plugin - any thoughts?

  6. Jeromy Says:

    Hmm, well - I just did the install again (even though that file had been deleted!) and now it works fine - weird

Leave a Reply