Archive

Archive for the ‘Windows Live Writer’ Category

WLW Post Fails With Error “The underlying connection was closed: An unexpected error occurred on a receive.”

September 27th, 2013 1 comment

When trying to upload my last blog post from Windows Live Writer (WLW) to WordPress (WP) I received the following error:

————————————————————————-

Network Connection Error

Error attempting to connect to blog at:

http://blog.danskingdom.com/xmlrpc.php

The underlying connection was closed. An unexpected error occurred on a receive.

————————————————————————-

WLWNetworkConnectionError

 

I had no problem uploading to my blog a couple weeks earlier and hadn’t done any updates or changed anything, so I thought this was strange.  After waiting a day, thinking maybe GoDaddy (my WP host) was having issues, I was still getting the error.  After Googling I found many others reporting this error with varying degrees of success fixing it.  So after trying some suggestions that worked for others (change WLW blog URL from http to https, edit the WP xmlrpc.php file, delete and recreate blog account in WLW, reboot, etc.) I was still getting this same error.

So I decided to try posting a new “test” post, and low and behold it worked.  So it appeared the problem was something with the content of my article.  So I started removing chunks of content from the article and trying to post.  Eventually I found that the problem was being caused by the string “In that post” in the first paragraph of the post.  I thought that maybe some weird hidden characters maybe got in there somehow, but after reviewing the article’s Source I could see that it was just plain old text.  I deleted the sentence and retyped it, but it still didn’t work.  If I just removed “In that post” from the sentence then everything worked fine; very strange  After more playing around, I found that if I just added a comma to the end and made it “In that post,”, that also fixed the problem.  So that’s how I’ve left it.

I don’t know what is special about the string “In that post”;  I created another test article with that string in it and was able to post it without any problems.  Just a weird one-off WLW-WP problem I guess.

 

Moral of the story

If you run into this same error, before you go muddling with config files and recreating your blog account, just try posting a quick “test” article.  If it works, then the problem is somewhere in your article’s content, so start stripping pieces away until you are able to get it to post successfully and narrow down the culprit.  Also, if you don’t want to publish a half-baked article while you are tracking down the problem, you can do a Save Post Draft To Blog instead of a full Publish to see if you are still getting the error

Happy coding!

 

— Update —

I’ve ran into this problem again when trying to post this article.  3 different spots in the article were causing the problem.  Here is the source of the article with what broke it, and what worked:

1. This broke:

<li>Click Yes when prompted to < strong > Run With UI Access < / strong > . </li>

(I had to add spaces around all of the 3 characters <, >, and / in the strong tags to get it to post here)

This worked:

<li>Click Yes when prompted to Run With UI Access.</li>

 

2. This broke:

<p>Today I stumbled across <a href="http://www.autohotkey.com/board/topic/70449-enable-interaction-with-administrative-programs/">this post on the AHK community forums < / a > .&#160;

(I had to add spaces around the each character of the closing </a> tag to get it to post here)

This worked:

<p>Today I stumbled across <a href="http://www.autohotkey.com/board/topic/70449-enable-interaction-with-administrative-programs/">this post</a> on the AHK community forums.&#160;

 

3. This broke:

the <a href="http://www.autohotkey.com/docs/commands/RunAs.htm">RunAs command < / a > .</p>

(Again, I had to add spaces around each character in the closing </a> tag to get it to post here)

This worked:

the <a href="http://www.autohotkey.com/docs/commands/RunAs.htm">RunAs</a> command.</p>

 

I can reproduce this issue every time on that article, and also on this one (which is why I had to change the problem code slightly so I could get it to post here).  So unlike my first encounter with this problem, these ones all seem to be problems parsing html markup tags; specifically the </> characters.  I’m not sure if this is a problem with Windows Live Writer or WordPress, but it is definitely a frustrating bug.  I’m running Windows 8 x64 and the latest versions of WLW and WP.

If you have any thoughts please comment below.

Why I Chose WordPress Over Geeks With Blogs, And Moving From WordPress.com To A GoDaddy Hosted Solution

May 17th, 2013 2 comments

A while back I wrote about some reasons why I didn’t like GWB (Geeks With Blogs) and was attracted to WordPress.  6 months later and I am confident that I made the right decision.  GWB was good to me, but their UI and features are just too dated and can’t keep up with what WordPress has to offer.  They said that they had hired some developers to improve the site, but it’s been 6 months and I can’t really see a difference.  When I wrote my last post the one thing that I didn’t like about WordPress.com was that I couldn’t find a theme that would stretch the content area to the full screen width; which is pretty essential for me since a lot of my posts involve long code snippets.  I never did find a theme to do this on WordPress.com (although I gave up after a few hours or searching).  Instead I decided to move to hosting my own WordPress instance.

I have a few other websites that I was hosting on my own personal server at home, but decided to move to GoDaddy for my hosting since they had a half price special and it would cost me less than my power bill to keep my server running (and I already had my domains registered through them).  I opted for the Deluxe package since I have a few websites, and GoDaddy offers up to 25 free WordPress installations with this package, so I have moved my blog from my deadlydog.wordpress.com site to my GoDaddy-hosted blogs.danskingdom.com site.  The migration process should have been painless; just export my deadlydog.wordpress.com site to an xml file (this part was very easy and painless), and then import it into my new blogs.danskingdom.com site.  For some reason when trying to do the import I would often get a “Connection was reset by the server” error.  So it took me probably about 15 tries before it actually imported everything properly; a few times it died half way through the import, but most of the time it would die before the import even started.  Luckily blowing away and recreating an WordPress instance with GoDaddy is easy and only takes about 30 minutes.  Another reason I chose GoDaddy were that their base prices are pretty competitive, plus I consistently receive coupon codes in my email from them for an additional 25% or 30% off (hint, use referral code WOWdeadlyd to get 35% off orders on new products).  Also, their customer service is wonderful.  The support I’ve received via email has been only ok, but anytime I’ve actually called in to their support they’ve been awesome and very helpful.

So once I finally got all of my posts migrated to my own hosted instance I could fix some of the things that annoyed me about my wordpress.com site.  First, I’m able to modify the theme’s css directly without paying anything.  This allowed me to go in and stretch the content area to fit the user’s screen.  You can probably tell while reading this that it isn’t perfect; there is some extra space on the right-hand side, but meh, it’s much better than it was.  Second, it allowed me to add advertisements to my site, which help pay for the hosting costs.  You might be thinking, “What? I don’t see any ads”, but that’s because I’ve placed them at the very bottom of the page to be as non-obtrusive as possible.  Third, it allowed me to hook up Google Analytics to my site so that I can get even more information about my site’s traffic and visitors, and see what search terms were bringing people to my site.  And by hosting my own WordPress instance I can now install any WordPress plugin that I want, instead of only the ones that WordPress.com has allowed.  One thing that I’ve noticed however is that accessing and navigating links on my GoDaddy hosted WordPress site is often slower than it was on WordPress.com.  I’m not sure if this is a temporary thing or what (since I’ve only been hosting with GoDaddy for about a week), but I often notice myself waiting for a webpage to load now, where I never noticed this before with deadlydog.wordpress.com.  However sometimes a page is super quick to load, so it’s not consistent.

One thing that does sort of suck about moving from WordPress.com to my own hosted solution is that I couldn’t figure out how to transfer my site stats across, so my stats for blog.danskingdom.com only start from the day I setup the new blog on that domain.  Another thing that I didn’t realize until after I had setup my new WordPress account was that I would have to pay to have traffic from my old deadlydog.wordpress.com redirected to the new blog.danskingdom.com; it was only $13 for a year though, so that’s not too bad as I’ll likely delete my old wordpress.com site right before that expires.

One other change I had to make when moving from WordPress.com to my own hosted solution was that in order for my code snippets to show up properly I had to install SyntaxHighlighter Evolved on my WordPress instance, which was super simple to do, and I can still use the Source Code Highlighter Plugin for WordPress.com plugin for Windows Live Writer which is great.

GWB users may have noticed that I still post to GWB with a “Read more at” link that points to the post on my new domain (in fact I went and updated all of my old posts to “read more” at my new domain. GWB doesn’t offer any way to forward my blog with them to a different domain (not even a paid solution like WordPress.com), so updating my old posts with a link to my new domain was the best I could do).  This is because the one and only thing that I’ll miss about GWB is the community.  While double posting (bad I know, but at least I’ve switched to the “Read more at” method rather than double posting the entire post) I found that I would still get more comments on my GWB posts than my WordPress posts.  Did this mean that my GWB posts were getting more traffic though? I can’t tell because GWB doesn’t offer any sort of information or stats about how many visits my site receives, and I can’t hook up Google Analytics or other 3rd party services to it either.  I’m going to continue double posting with the “Read more at” links so that GWB users can still see my post titles on their feeds and don’t miss out on anything I post that they might find useful, as I too often monitor the GWB main page feed to see other code-related posts that I don’t want to miss out on.  Also, by changing to using the “Read more at” convention it allows me to only have to update my one website when I update an old blog post, rather than having to update multiple; this was a major pain point, especially when I needed to use different Windows Live Writer (WLW) plugins depending on which site I was posting code to.

Anyways, these are my thoughts on my blog’s move.  Hopefully it helps you with making a decision about going with GWB or maintaining your own hosted WordPress solution, and whether you choose GoDaddy or not.  Again, use referral code WOWdeadlyd to get 35% off your GoDaddy order.

Migrating My GWB Blog Over To WordPress

November 20th, 2012 3 comments

Geeks With Blogs has been good to me, but there are too many tempting things about Word Press for me to stay with GWB.  Particularly their statistics features, and also I like that I can apply specific tags to my posts to make them easier to find in Google (and I never was able to get categories working on GWB).

The one thing I don’t like about WordPress is I can’t seem to find a theme that stretches the Content area to take up the rest of the space on wide resolutions…..hopefully I’ll be able to overcome that obstacle soon though.

For those who are curious as to how I actually moved all of my posts across, I ended up just using Live Writer to open my GWB posts, and then just changed it to publish to my WordPress blog.  This was fairly painless, but with my 27 posts it took probably about 2 hours of manual effort to do.  Most of the time WordPress was automatically able to copy the images over, but sometimes I had to save the pics from my GWB posts and then re-add them in Live Writer to my WordPress post.  I found another developers automated solution (in alpha mode), but opted to do it manually since I wanted to manually specify Categories and Tags on each post anyways.  The one thing I still have left to do is move the worthwhile comments across from the GWB posts to the new WordPress posts.

The largest pain point was that with GWB I was using the Code Snippet Plugin for Live Writer for my source code snippets, and when they got transferred over to WordPress they looked horrible.  So I ended up finding a new Live Writer plugin called SyntaxHighlighter that looks even nicer on my posts Smile

If anybody knows of a nice WordPress theme that stretches the content area to fit the width of the screen, please let me know.  All of the themes I’ve found seem to have a max width set on them, so I end up with much wasted space on the left and right sides.  Since I post lots of code snippets, the more horizontal space the better!