This unexpected, unplanned, and un-beta-tested release comes to you with a bunch of TypePad related tweaks and a new TypePad feature.
Download Pocket SharpMT 2.6: ZIP | ARM
I was originally planning on adding support for the “Future” Post Status option that’s in MT3 and TypePad – thanks to ***Dave for checking into this for me! – but it seems that ya have to set the status after you post the entry, so a bit of a re-write would be required. Right now status is sent as a boolean along with the post, and, well, it’s more of a change than I wanted to introduce with this… I’ve added it to the list for the next release, though.
For TypePad, the following things are now fixed: the crash on start up that was related to Blog Links, Edit in Browser, and a tweak to the Options dialog. Most of this related to the desktop version, but I’m rev’ing Pocket SharpMT to keep it up to speed. FYI: the crash on start up wasn’t the “smart caching” like I thought it was, so I left that in there. One of the things I had to do for MT was kludge some formatting for ISO-date formatting. XML-RPC expected a certain format and MT never returns the proper ISO format, so I had to clean that up on Blog Link request… TypePad corrects the error, so my “nifty workaround” wasn’t needed any more.
Also, if you have a www.typepad.com Host Name you will be in TypePad mode; any other host will be MT mode. I plan to have a better handling scheme for this in SharpMT 3.
Lastly, it seems that TypePad caps the number of links you can request to 250. Since I was starting with a new list (yet have over 500 posts) I had to export the links in a different way: I used a TypePad template to spit out an XML document with the existing links in the form the blogLinks.xml requires. If you find yourself in a similar situation, I’ve added a text fill called “TypePad Links.txt” to the SharpMT directory: if you add this template to your blog, you can get the XML you need to have a full Blog Links list again.
And yes, these fixes were added to the SharpMT 3 code base, so it shouldn’t be a problem in the future…
Read: SharpMT FAQ
Read: Pocket SharpMT FAQ