Here is something I wrote recently:
The other field on the blogAPI settings page, XML-RPC Engine, determines which is the preferred set of functions that should be used if the publishing client supports more than one API. The options include Blogger, MetaWeblog and Moveabletype and the recommended default is Blogger, simply due to the larger number of functions it supports. There is no reason to change this setting, even if you wish to use the MetaWeblog or Moveabletype APIs, as the setting is only responsible for publishing the preferred API, and doesn't turn anything on or off.
(emphasis added)
Upon reviewing this, Morbus correctly asks
If there is no reason to change the setting, because it seemingly doesn't do anything important, why is it there?
Therefore this patch takes away the configurability and just defaults to Blogger. Since it is, after all, only a preference for some form of mostly non-existent auto-discovery, and even in the worst case doesn't restrict the functionality, why should we bother people with it?
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | blogapi_5.patch | 1.18 KB | ax |
| blogapi.patch.txt | 2.51 KB | robertdouglass |
Comments
Comment #1
chx commentedMakes sense to me as the new XML-RPC library supports introspection anyways.
Comment #2
Bèr Kessels commentedMakes a lot of sense. Offering options for the sake of options is plain silly :) This sounds like such a case.
Comment #3
dries commentedCommitted to HEAD. Less is more.
Comment #4
(not verified) commentedComment #5
ax commentedthe patch committed only removes the *usage* of the setting, but not the setting itself. attached patch does so.
Comment #6
walkah commented+1 . please apply, Dries.
Comment #7
Jaza commentedThis setting appears to be gone in HEAD. Closing issue.