ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Windows Live Writer

July 01, 2011 3:31pm

Subscribe [2]
  • #1 / Jul 01, 2011 3:31pm

    alpcom

    5 posts

    Hello everybody,
    since I updated to EE 2.0 I have troubles with using WIndows Live Writer to post to my weblogs. Using version 2.1.x I often got error messages when editing posts from Windows Live Writer, but not that I updated to 2.2 I can’t even post anymore - I get a message that says “802 invalid access”. I know Windows Live Writer is a third party tool and probably not officially supported, but could somebody give me some pointers how I can debug these problems? Can I turn on logging for the metaweblog API, or for Windows Live Writer, so that I can submit a decent problem report?

    This used to work flawlessly on EE 1.x :-( I love the options that EE 2 has but this is a real drawback, because I also like the ease of use of Windows Live Writer…

    Thanks in advance for any pointers.

  • #2 / Jul 05, 2011 4:56am

    John Henry Donovan

    12339 posts

    alpcom,

    Ok downloaded Live Writer (XP version) and can confirm it working in 2.1.3 and not in 2.2.1. I created a bug report on your behalf here

  • #3 / Jul 05, 2011 4:55pm

    alpcom

    5 posts

    Thank you for your reply.

    However, yesterday evening I was with a family member that also uses live writer to post to the same website/EE instalation, and it worked at her computer. She uses an older version of Windows Live Writer, but at the same EE install (2.2). So I am not sure if the problem is with EE.

    Furthermore, I also tried with ScribeFire, and I got the same results. Could it be that remote posting through the metaweblog api somehow needs to be authorized? I really wish to be able to read some log files for this but I guess they can not be found?

  • #4 / Jul 07, 2011 5:45pm

    Kevin Smith

    4784 posts

    Considering the error message, it’s quite possible that this is an issue due to authentication. Since John Henry’s able to replicate the problem, we’ve got a bug report filed, and we can test it from here, I’m going to close this thread out. Let us know if there’s anything else we can do to help!

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases