Ticket #5023 (closed enhancement: fixed)
Add Windows Live Writer manifest XML file (and images), enables tagging support
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | low | Milestone: | 2.3.1 |
| Component: | XML-RPC | Version: | |
| Severity: | minor | Keywords: | has-patch, wlw, xmlrpc |
| Cc: | josephscott |
Description
Windows Live Writer (WLW) uses an XML manifest file to determine what features a blog supports. By default it does a good job supporting WordPress without a manifest file, but that doesn't include support to mt_keywords (tagging) in XML-RPC methods. The included manifest file turns on tagging support in WLW.
The zip file includes the following:
wlwmanifest.xml wlw/WpComments.png wlw/WpIcon.png wlw/WpWatermark.png
Attachments
-
wlwmanifest.zip
(820 bytes) -
added by josephscott 4 years ago.
-
wlw-head.zip
(11.4 KB) -
added by josephscott 4 years ago.
- WLW manifest file using the wp_head hook
-
wlw-head.diff
(1.3 KB) -
added by josephscott 4 years ago.
- Changes to wp core to add the WLW manifest file using the wp_head hook.
Change History
comment:2
josephscott — 4 years ago
Sure, the images can go to wp-includes/images/. If I'd been paying attention I would have put them there in the first place :-)
The blog-postapi-url with .. came from J.J. Allaire at Microsoft. I asked him about at one point and he explained it this way:
One note, for getting to the correct location of wp-admin the following pattern is more robust than "{blog-homepage-url}/wp-admin/"
{blog-postapi-url}/../wp-admin/
This handles the case of the blog not being the homepage for the site, e.g. http://foo.wordpress.com/blog/ is the blog and a custom page is located at http://foo.wordpress.com.
comment:3
josephscott — 4 years ago
I updated the zip file to move the images to wp-includes/images/ instead of wlw/
josephscott — 4 years ago
-
attachment
wlw-head.diff
added
Changes to wp core to add the WLW manifest file using the wp_head hook.
comment:4
josephscott — 4 years ago
I've added two new attachments that make use of the wp_head hook to add the wlwmanifest.xml file.
- Owner changed from anonymous to westi
- Status changed from new to assigned
I have a look at getting this is 2.4
- Status changed from assigned to closed
- Resolution set to fixed
- Status changed from closed to reopened
- Resolution fixed deleted
- Milestone changed from 2.4 to 2.3.1
opening for 2.3.1 consideration
How does this benefit people who don't use WLW? It's just a waste of code, space and bandwidth to echo this useless line for most of us who don't use WLW.
IMO this should have been a plugin or an option at least.
IMO this should have been a plugin or an option at least.
Perhaps at first at least.
Mind you, Does WLW have a header/user agent it sends? Perhaps it could be tied to that instead?
comment:10
josephscott — 4 years ago
There has been at least one other XML-RPC client vendor who has expressed interest in using the wlwmanifest.xml file.
The question is probably better put as, should this be in core? Given the huge popularity of WLW I'd say yes. That said, yes, it can also be done as a plugin.
comment:11
westi — 4 years ago
I think this is perfect for the core actually. Improving support for XMLRPC clients out of the box is important. If the more technical users who don't use these client want to save the minimal amount of bandwidth adding an extra line in <head></head> then you can remove the action easily and it won't be sent.
Most new users will see it as a bug if we don't have good support for WLW.
comment:12
ryan — 4 years ago
- Status changed from reopened to closed
- Resolution set to fixed
Can the images be but in wp-includes/images?
I'm not understanding the need for .. in the urls. Where does blog-postapi-url point?