WLW doesn't give any mechanism for adding a new category when config'd with a MetaWeblogAPI blog.  When used with a WordPress blog it gives the ability to add categories and also tags (lighter weight). I've not tested it with other APIs.

MS Word does give a mechanism to add a category (with a mojoPortal blog), but it errors on posting. There is no error in the mojoPortal system log, but Fiddlers shows this:

POST:

<methodCall><methodName>metaWeblog.editPost</methodName>

<params><param><value><string>8</string></value></param>

<param><value><string>myusername@isp.com</string></value></param>

<param><value><string>mypassword-unencrypted</string></value></param>

<param><value><struct><member><name>title</name>

<value><string>My Post Title</string></value></member><member><name>description</name>

<value><string>myblogpoststring-escapedhtml</string></value></member>

<member><name>categories</name>

<value><array><data><value><string>ANEXISTINGCATEGORY</string></value>

<value><string>MYNEWCATEGORY</string></value></data></array></value></member></struct></value></param>

<param><value><boolean>1</boolean></value></param></params></methodCall>

Response:

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/xml
Server: Microsoft-IIS/7.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Thu, 10 Nov 2011 22:19:32 GMT
Content-Length: 440

<?xml version="1.0"?>
<methodResponse>
  <fault>
    <value>
      <struct>
        <member>
          <name>faultCode</name>
          <value>
            <i4>0</i4>
          </value>
        </member>
        <member>
          <name>faultString</name>
          <value>
            <string>Could not update post.</string>
          </value>
        </member>
      </struct>
    </value>
  </fault>
</methodResponse>

Hope this helps.

Great - looking forward to trying this in the next release (and no problem pretending blog is a Community Server so long as this is in the how-to). 

I don't know if you spotted my other thread, but I'm chewing on how to create a good company knowledge base with mojo, where some content is private and some public, and where we also have fast authoring tools. I'm considering blog vs pages or a combination of the two...

Blog = fast authoring with Word / WLW,  however content must be entirely public or private.

Pages =  structure + full control over access, but (relatively) clunky authoring in TinyMCE or CKEditor.

Ideally I'll go for a blog for the public point-in-time content,  plus pages for structured content (product documentation, how-to's etc) some of which will be public others not. But the lack of quick authoring is a big problem - staff are very busy and if it takes twice as long as doing it in Word docs they will not buy in.

In a WordPress site I can create and publish actual pages in WLW... you just create a "new page" (instead of "new post") then choose which existing page it should sit beneath (if any) + order, and away you go.

Is there any way this could work with mojoPortal, to create a page with an HTML content feature on it, using some default settings for page/content security? This would give us the quick authoring we need.  

This must come down to the manifest for the API, because with the metaweblog api the "new page" option is greyed out in WLW.

best wishes

PS I've just checked that link you posted about WLW capabilities, and I see that only the WordPress API supports new pages by default, but that you should in theory be able to include these methods as options into the WLW manifest for the others (just as you have been trying to do for new categories - is caching getting in the way here?).

Hi Joe

That's exactly what I was thinking - new "page" from WLW = page + html content in center panel, and like you say for existing pages.  I completely agree that something is better than nothing here, if you can find a way to achieve it, even though clearly there will be limitations.  It's all about fast user-friendly authoring.  I suppose the alternative is a) finding an HTML content editor inside mojoPortal that approaches the user-friendliness of WLW and handles images efficiently, and b) making it a little easier to create a new page (the page template idea being perhaps the best angle of attack here).

Incidentally, if you are working in this area, we have noticed that when we post with WLW the images go into a specific folder under the site; however when we post from Word, the images get dropped in the site root, which is less desirable. Are you able to catch these and park them in a suitable sub-folder?

And related, should all these be under the "media" folder?  I've only just realized the role of the media folder from Jamie E's post, and I'm now having to reorganize files in several sites.  Is there some documentation that I've missed about the purpose of the default folders under each site? 

Thanks Joe, great improvements and I look forward to implementing them.

2 q's:

I mentioned in previous post that images posted from Word go into site root folder - can you fix that? as for WLW?

I noticed today that publishing from WLW with the "post draft to blog" tool instead of the "Publish" tool makes no difference - the post is fully published in the mojoPortal blog. Any way of making this create a draft post in mojoPortal?