If you're new here, you may want to subscribe to my RSS feed. You can even subscribe by email! Thanks for visiting!
One other niggle I found with Live Writer:
Even if you set your blog’s time to a time in the future, it publishes it straight away.
I decided to publish my FIR report for this week (FIR #256) at the same time as FIR normally comes out, so set the time several hours in advance.
Imagine my disappointment and embarrassment, then, when the post appeared immediately upon publishing it, rather than ‘holding’ it until the publishing time I had set. I know that my blog can withhold posts until a pre-set publishing time because I’ve done it from within the very blog engine I’m using now, Zoundry.
The very wise and must-read geek, Amit Agarwal, asked me if Live Writer still corrupts images when I keep the image size ‘as is’ rather than let Live Writer resize it. Yup - it still corrupts. His question challenged me to think about how Live Writer copes with images when it links to them, rather than actually uploading them itself. The funny thing is that logic tells me that it shouldn’t corrupt them. But sometimes my eyes tell me that it does. But maybe that’s just my eyes playing up… But Live Writer certainly does optimise already-optimised images (to poor effect), whether you let it resize them or not.
If Live Writer could address the niggles I have then I would have no hesitation in switching over fully to it. But until then, Zoundry is still my editor of choice. Just.
I know that there are a plethora of offline blog editors out there, each with different features. I know that each of us prefers one over another. To each his own…
Powered by Zoundry
{ 1 trackback }
{ 7 comments… read them below or add one }
Tris Hussey 07.11.07 at 7:56 am
Lee are you using the latest version of LW? I had the exact same problem, but the latest version fixed all that.
Lee Hopkins 07.12.07 at 10:27 am
Tris - the version I have is 1.0 (build 12.0.1183.516)
Is yours different? Plus, Dan York also finds that it won’t delay posts: http://snipurl.com/1o6hx
Lee Hopkins 07.12.07 at 10:36 am
Tris - i just downloaded the latest version and installed and it’s the same version.
Tris Hussey 07.12.07 at 10:42 am
I just checked mine and yes that’s it. Very strange.
Joe Cheng [MSFT] 07.14.07 at 2:41 am
Your meta tag says WordPress 1.2. You’re not really using such an old verison of WordPress, are you? If so, upgrading to a more recent build will fix this problem.
I don’t know how it’s possible that Zoundry doesn’t have this problem, all we do is pass a future date in dateCreated. Are you 100% sure the problem is only with WLW?
By the way, we do in general make an effort to warn you if your blog doesn’t support future posting (or if we don’t know if it does). You should get a dialog asking for confirmation before you publish. However, since your blog is WordPress we expect it to work, thus you don’t get a warning.
Joe Cheng [MSFT] 07.14.07 at 2:41 am
(Sorry, I forgot to subscribe to comments)
Lee Hopkins 07.14.07 at 9:28 pm
Hey Joe,
REALLY appreciate you coming into this! The metatag on my blog is confusing, because I am 98.37% sure that my host upgraded me to WP2.0.
If I go into my wp-admin screen, look at Options, it tells me it’s version 2.1 - weird, huh?
I’m going to wander over to my other post to go through your 1-5 comments (because I can’t remember what I posted! {grin})