Metaweblog API returning an error if "Excerpt" filed is selected
Hello everybody,
here's my configuration:
Umbraco 4.0.2.1
tested on Standalone and 3 servers config (distributedCall=true)
ASP.NET 2.0
windows server 2003 R2 SP2 (ja)
Windows Live Writer (build 14.0.8089.726 en) OR Word 2007
If I configure the Content Channel without selecting the Excerpt field everything works like a beauty. I can create new posts and edit existing posts using both Windows Live Writer (WLW) and Word 2007 (BEAUTIFUL!).
If I set the Excerpt field then both WLW and Word fail with the following repro.
Description is mapped to a Rich Text field
Category is mapped to a Tags field
Excerpt is mapped to a TextString Field (also tried with a RichText and a Textbox multiple)
upon publishing i get a "Blog Server Error, Server Error 0 Occured, object reference not set to an instance of an object" (word gives a very generic "Word cannot publish this post" message)
no umbraco log entries are available
the node gets created, but it is not published
if I try to re-save, it does the same thing, but it creates a new node (i.e. it does not edit the previous node I ust created)
Could you please repeat your content channel/link rel...entry settings here?
I have the very same issue but am unable to fix it...I inserted the link rel into the master page of the document type being published via content channel/WLW...maybe it should be in the document type itself?!?
Metaweblog API returning an error if "Excerpt" filed is selected
Hello everybody,
here's my configuration:
If I configure the Content Channel without selecting the Excerpt field everything works like a beauty. I can create new posts and edit existing posts using both Windows Live Writer (WLW) and Word 2007 (BEAUTIFUL!).
If I set the Excerpt field then both WLW and Word fail with the following repro.
I couldn't find anything recent in our.umbraco.org or forum.umbraco.org and no bug in codeplex (I found only this http://umbraco.codeplex.com/WorkItem/View.aspx?WorkItemId=12089, but it is quite old, it has no details and it appears to be closed)
Anybody experiencing this issue?
Thanks a lot
Andrea
My mistake, I put a wrong url in the <link rel... entries in the <head> of the document... The issue lamented in this post is a non issue.
thanks
andrea
Could you please repeat your content channel/link rel...entry settings here?
I have the very same issue but am unable to fix it...I inserted the link rel into the master page of the document type being published via content channel/WLW...maybe it should be in the document type itself?!?
Any help would be appreciated.
is working on a reply...