Feedback Form

Skip to content


Google Sitemaps creates error on WordPress

When attempting to post yesterday, I received an error from WordPress:

Something went wrong - -32300 : transport error - HTTP status code was not 200 wordpress

After a bit of troubleshooting, I noticed that my post was publishing, but it had no tags. And after a bit more research, I found that this error is in relation to pinging sites.

Remembering that I had a plugin that pings sites to notify them I have updated, I deactivated the Google Sitemap Generator WordPress plugin and posted again. No error. Something either in the plugin or in its communicating with other sites is not working right now, preventing full posting of my blog entries and causing errors. Just a heads-up in case anyone else runs across this.

Since I use my Feedburner Feed to notify sites that I have updated as well, the functionality isn’t necessary for me, so losing the plugin isn’t a big deal. Still, hopefully there will be an update to it soon to address this issue.

Share and Enjoy:
  • Google
  • del.icio.us
  • MySpace
  • Facebook
  • Digg
  • StumbleUpon
  • TwitThis
  • Slashdot
  • Technorati
  • E-mail this story to a friend!

Related posts:

  1. Correction: Google Sitemaps Does NOT Cause Error on WordPress
  2. Ending Crossposting
  3. MySpace Crossposting
  4. WordPress-MU 1.5.1
  5. Using a Second Sidebar for Different WordPress Pages

Posted in Technology. Tagged with , , , , , .

One Response

Stay in touch with the conversation, subscribe to the feed for comments on this post.

Continuing the Discussion

  1. Correction: Google Sitemaps Does NOT Cause Error on WordPress - SilverPen Publishing linked to this post on November 19, 2008

    [...] wrote some time ago that I encountered an error when using Google Sitemaps vis-a-vis pinging services and WordPress. Turns out, this was [...]

Some HTML is OK

(required)

(required, but never shared)

or reply to this post via trackback.