The other day I posted an entry about a bug that I had ran into using the Twitme plugin for WordPress, and as I mentioned in my post the only thing that had changed was that I had recently upgraded to 2.8.1 on WordPress.
I also mentioned that I was getting this error when I used Windows Live Writer to publish my content, which I do a majority of the time. This is the error that we were getting back while troubleshooting:
PHP Fatal error: Cannot use object of type stdClass as array in /var/www/vhosts/cottonrohrscheib.com/httpxdocs/blog/wp-content/plugins/twitme/twitmeShortUrl.php on line 37
I use the Twitme plugin on my site and several other of my clients sites so I have been pretty persistent in trying to find a workaround for this. If you are not familiar with what Twitme does, it basically pushes your posts directly out to Twitter when they go online. Granted there are a lot of other solutions to accomplishing this, including the manual method that a lot of people like to use but I prefer the automation as do a lot of my clients.
If you have ran into this same issue, or seen this warning message after you publish a post with Live Writer:
The response to the metaWeblog.newPost method received from the blog server was invalid:
Invalid response document returned from XmlRpc server
You will want to first make sure that you have RPC publishing enabled inside of WordPress, this can be found under Settings >> Writing inside the dashboard. If you have this enabled then try going to the Twitme >> Settings page and unchecking the box that says Use Short URL’s, this fixed the issue for me and as you can see Twitter still managed to shorten the URL before it went out.
Lena says
THANK YOU! I didn't really think about this being an issue with the shorten URL feature, but you fixed my problem! Thank you! I just turned off the shortening as suggested and it works great. WP to Twitter has the same problem. I bet it takes the same fix!
Cotton Rohrscheib says
Hi Lena – something else you might look into, that I have started doing instead of Twitme, is using Feedburner to actually send your posts into Tweets. It's not too hard to setup. I have found it does a better job. Twitme has been problematic for me.