Ok, just a couple of small issues I want on the record…
Twitter has stopped posting my SMS updates. I think after sending a couple while I was overseas in Ireland and the UK they decided to cut me off. Could they must have been dinged for receiving out-of-country SMS messages from me? Really, I’d prefer them to tell me.
On the upside, I resorted to ping.fm for my posting updates. They don’t do SMS, but they do post a custom email for you to send stuff to. They even clipped the “This message was sent from my BlackBerry” footer from the posting. So I lost SMS, gained email and since unlimited email is included in my plan I actually come out ahead.
I still would like to have been told I was going to lose SMS. I think I’ll ask Twitter customer service about it and see what they come back with.
The other issue is slightly more frustrating. Each time I post from Windows’ Live Writer I get a double-post. I looked around and this is not an uncommon issue. Funny thing is, I think this only happens when I post on my laptop. That is, I remember making posts from my desktop ‘puter and not noticing a double-post. This posting is on my desktop now, so it’s part of a grand experiment… I’m suspicious it’s either a bad plugin, somehow I’ve got doubled settings in my laptop or drafts I save to an offline folder are breaking things somehow. Stay tuned for more riveting developments.
So there you are. Blogging is hell—when the tools don’t work. The Twitter issue balanced out to a net-zero in the end, but I’ll have a tough time giving up on Live Writer if I can’t get around this double-post thing.
Update: There it is. Plain as the nose on your face, TWO postings of the same article. Even the permalink IDs are the same. Now my suspicion moves me to believe this is a BlogEngine.net issue... I wonder if it's because I posted to two categories. Instead of littering the blog with test posts, I'm going to try a posting tomorrow. At least theissue isn't a laptop-vs-desktop installation thing, both posting locations suck the same, so I can look elesewhere for a solution!
Update 2: A solution, kind of. It seems this is a BlogEngine bug. To cut it short, there seems to be two instances of the same post in memory. There is actually only one post recorded so it's not worth it to delete the extra post. The trcik to erasing the double post is to reset your web app-- the easiest way is to edit your Web.Config file... add/remove a carriage return from the endo of the file and save it. This forces a reload and poof, the double post is gone. I bet they're caching the post and the trigger is firing twice... why is an issue for another day.
Tags: blogging, blogengine.net, web.config, double-posts