Ticket #5023 (closed enhancement: fixed)

Opened 10 months ago

Last modified 9 months ago

Add Windows Live Writer manifest XML file (and images), enables tagging support

Reported by: josephscott Assigned to: westi
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 (0.8 kB) - added by josephscott on 10/04/07 20:17:12.
wlw-head.zip (11.4 kB) - added by josephscott on 10/04/07 21:17:42.
WLW manifest file using the wp_head hook
wlw-head.diff (1.3 kB) - added by josephscott on 10/04/07 21:18:13.
Changes to wp core to add the WLW manifest file using the wp_head hook.

Change History

09/20/07 18:35:41 changed by ryan

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?

09/20/07 22:51:07 changed by josephscott

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.

09/20/07 22:55:10 changed by josephscott

I updated the zip file to move the images to wp-includes/images/ instead of wlw/

10/04/07 20:17:12 changed by josephscott

  • attachment wlwmanifest.zip added.

10/04/07 21:17:42 changed by josephscott

  • attachment wlw-head.zip added.

WLW manifest file using the wp_head hook

10/04/07 21:18:13 changed by josephscott

  • attachment wlw-head.diff added.

Changes to wp core to add the WLW manifest file using the wp_head hook.

10/04/07 21:33:08 changed by josephscott

I've added two new attachments that make use of the wp_head hook to add the wlwmanifest.xml file.

10/05/07 15:36:29 changed by westi

  • owner changed from anonymous to westi.
  • status changed from new to assigned.

I have a look at getting this is 2.4

10/05/07 17:29:34 changed by ryan

  • status changed from assigned to closed.
  • resolution set to fixed.

(In [6192]) WLW manifest from josephscott. fixes #5023 for trunk

10/05/07 19:32:45 changed by ryan

  • status changed from closed to reopened.
  • resolution deleted.
  • milestone changed from 2.4 to 2.3.1.

opening for 2.3.1 consideration

10/06/07 22:43:26 changed by rob1n

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.

10/06/07 23:09:47 changed by DD32

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?

10/07/07 06:07:18 changed by josephscott

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.

10/07/07 07:30:12 changed by westi

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.

10/09/07 21:09:49 changed by ryan

  • status changed from reopened to closed.
  • resolution set to fixed.

(In [6211]) wlw manifest from josephscott. fixes #5023 for 2.3