Recently we upgraded our blog to WordPress 2.5.1 and have been battling a horrible bug ever since. When we save or edit a post most of our content is sometimes lost. Unfortunately, it isn’t occurring with enough frequency for us to track down the specific cause of the problem and we have enough projects lined up over here to keep us from digging through the WordPress code ourselves to solve it in any reasonable time. So we’ve opened up a ticket in WordPress’ bug tracker that outlines the problem in more detail and continue to wait for a response from someone on the dev team to let us know what might be the culprit.

In the meantime, the fear of not knowing if your post would be lost when saved forced us to saving the content to notepad before publishing. This is a less than useful solution to the problem because even doing this it seems that once a post starts truncating itself upon saving, it continues to do it every time. The only solution is to delete it and start anew. [We're noticing the problem crops up most often when another user edits an entry not their own. It truncates the post arbitrarily and then proceeds to reject contributions to that post past the truncated length. Needless to say, the frequency and creativity of expletives uttered in the office has spiked dramatically.—Ed]

So today, I took some time to hunt down remote posting solutions that allowed us to save our posts without needing to log in to WordPress directly. ScribeFire was the first solution I tried and has turned out to be an incredibly useful tool. ScribeFire is a FireFox extension that allows us to create posts directly in FireFox and saves them to our blog via the WordPress API.

There is still some functionality lacking: the ability to change post author, adding excerpts and making use of some of the plugins that modified our post entry page to name a few. But we see their release schedule to be rather efficient and hope to request some features that make it into the next release (or until WordPress identifies the problem that forced us to this solution in the first place). [It should also be noted that the extension on the whole is rather impressive considering that it's blog-engine agnostic and works for many different providers.Ed]

Posted in: Rants