The pieces are nearly in place, not to mention the fact that OAuth will pretty much be essential if WordPress is going to adopt OpenID at some point down the road. Heck, Stephen Paul Weber already got OAuth + AtomPub working for WordPress, and has completed a basic OAuth plugin for WordPress. There are a number of reasons why WordPress should adopt OAuth - and not just because we’re going to require it for DiSo. This topic hit the wp-xmlrpc mailing list where the conversation quickly devolved into spattering about SSL and other security related topics.Īllan Odgaard (creator TextMate, as far as I can tell!) even proposed inventing another authorization protocol. The argument is that this will make WordPress more secure out of the box - but the question is at what cost? And, is there a better solution to this problem rather than disabling features and functionality (even if only a small subset of users currently make use of these APIs) if the changes end up being short-sighted? Without this address, it’s as if the blog was never updated.In the past couple days, there’s been a bit of a dust-up about some changes coming to WordPress in 2.6 - namely disabling ATOM and XML-RPC APIs by default. (An RPC/API Endpoint URL is the Web address that sends out the ping alerting the world to a new or updated post. There is no explicit RPC URL setting in any of the four blog setting windows. The error message told me to correct the setting-but going to the settings window didn’t help matters. When I tried posting a blog entry I had saved as a draft, I got an error message telling me that I needed to fill in the correct RPC URL. The way this blog is set up, the parent site is using a version of Movable Type to host several blogs on a private server consequently, the app wasn’t able to auto-detect the settings and load in crucial information like the API Endpoint URL. However, the second blog I tried to produce within MarsEdit was a failure. Configuring the application for this blog was easy-all I had to do was enter the blog’s name (it will be displayed as an option in MarsEdit’s main window pane) and the homepage URL, then click the Auto-Detect Settings From URL button, and a few seconds later, I was in business. One of the blogs I tested MarsEdit on is hosted on Typepad’s service. Users may be slightly more challenged by how to configure their individual blogs-and that difficulty could offset MarsEdit’s ease of use in blog production. Lightroom ( ), and Flickr, letting you upload photos from your libraries with a single click.Īs you produce your post in one window, you can check to see how it’s formatted in the preview pane that pops up nearby.Ĭomposing and publishing posts is the easy part. This is a handy feature for people who are responsible for producing multiple blog posts per day or for people who are queuing up posts for pre-planned vacations and time off. Using the Edit Date option under the Posts menu, you can type the date and time you want a specific post to go live. It would be nice if you could edit in the preview pane-for example, in one test post, a subject-verb disagreement eluded me in the composition window but popped into plain relief in the preview window, and it would have been easier to correct it the minute I saw it-but this feature is not a vital must-have.Īnother welcome new feature within MarsEdit is the ability to schedule your blog posts’ publication. You now have the option to compose posts in either Rich Text or HTML format, and as you type, a separate preview pane pops up and lets you see how your post is going to look. The biggest selling point for the new version: an improved WYSIWYG interface for post composition.
0 Comments
Leave a Reply. |