MarsEdit displays a list of recent posts in the MarsEdit window ( Figure 37).įigure 37. Supply your username and password so that MarsEdit can contact the server and interact with your blog. Enter the requested information ( Figure 36). MarsEdit displays a dialog box requesting your username and password if you have never worked with this blog before, or have not saved the password. I have selected my 'test' blog in the MarsEdit Weblogs Drawer. If necessary, choose View > Show Weblogs to display the Weblogs Drawer.Ĭlick once on the name of your blog in the Weblogs Drawer to select it ( Figure 35).įigure 35. The blog is added to the list of blogs in the Weblogs Drawer. We suggest you set this to a number between 10 and 30.Ĭlick the OK button ( Figure 34). Number of posts to download is the number of recent posts MarsEdit will automatically download. īlog ID is usually 1 for a WordPress blog. The address for this file is the address for your blog, followed by /xmlrpc.php. RPC URL is the address of the xmlrpc file. Software is the system your blog is using. MarsEdit could not successfully obtain the settings it needed, so edit them manually. It does not need to be the same name that appears on your blog.įigure 33. Name is any name you wish to use for your blog inside MarsEdit. I have entered the settings for my blog in MarsEdit.Ĭlick on the System tab button to configure the base settings: If you choose to Edit Settings by hand the Blog settings dialog is displayed ( Figure 34).įigure 34. Click the Edit Settings button to continue setting the preferences or the Cancel button to continue to the main MarsEdit window with incorrect settings. If it has a problem it will display an alert ( Figure 33). MarsEdit attempts to automatically obtain the settings it requires. Weblog URL: the address for your blog.If you use MarsEdit to post to several blogs, this name will let you know which one you're working with. Weblog name: use a name that is meaningful to you.
Enter your blog's name and address to begin. When you first start MarsEdit it displays a Getting Started screen. If you have never used it before a Getting Started window is displayed ( Figure 32).įigure 32. We used version 1.1.2 in writing this chapter.Įxtensive help is available from the application's Help menu. If there is a person who can be trusted with gremlins in XML character encoding world, it’s Sam, and while XChar is a burden when you want to read your own Russian XML feed in plain-text, it’s a perfect fit for the problem we are facing here (generating well-formed XML no matter how great the cost or readability of the product).MarsEdit is a weblog client for Macintosh OS X available from A 30-day trial version is free. The library we all love and use is Jim’s XML Builder - an extremely versatile and friendly block-based XML generator, which also happens to have one of the most extensive XML character sanitization routines available - the so-called XChar harness by Sam Ruby. The XML writer in Ruby’s RPC works based on text concatenation. well the rest is expected to somehow happen when you pass your results to XML RPC. Let’s put it that way - the only sanitization done is replacing the obligatory entities. I wish I didn’t - to spare you a search, the file you need is create.rb. Even though it might be present in the blog entry itself, it should never bleed through into the XML representation for an RPC call! So I went out to investigate what writes XML for Ruby’s XML RPC. This is an ASCII “control” non-printable character, and putting it into XML is anything but responsible. Don’t know how MacOS X managed to type it into the entry box in MarsEdit, but it certainly was there! The character in question is ASCII 005, the ENQ character. I copied the XML response into a standalone XML document and ran it through xmllint.Įven more interesting.
But then an update to MarsEdit came along, and lo and behold - the updated MarsEdit was not able to retreive the very entry the old one has made. When I’ve posted it and retreived it via MarsEdit, everything went well. Recently I’ve posted an entry about caches. The module is somewhat antiquated and the docs are not always telling all that you might need, but there is a little problem which is actually very serious - it uses a bozo XML writer. So I’ve implemented a small MetaWeblog responder based on Ruby’s XML-RPC module. I also don’t have an aversion to Dave Winer, and Atompub is not there yet IMO. I’ve written this blog with an aim for spotless MetaWeblog API support (I hate Web UI’s and I own both MarsEdit and Ecto licenses). This one is an example of why if you do XML you better do it right.
0 kommentar(er)
