PC Training & Consulting Weblog

Glad to have found this fix (thanks!) and share it with anyone who needs it. mjh

WordPress › Support » Tweet This 1.8.3 giving HTTP 404

noapi1
Member
Posted 3 days ago #

The solution is:
Edit

/plugins/tweet-this/tweet-this.php

and change line 89 from

define('TT_API_POST_STATUS', 'http://twitter.com/statuses/update.json');

to

define('TT_API_POST_STATUS', 'https://api.twitter.com/1/statuses/update.json');

March 2013 they will again change something, to we will have to change to …/1.1/…
See: https://dev.twitter.com/discussions/10803

WordPress › Support » Tweet This 1.8.3 giving HTTP 404

For more than a year, I’ve been plagued by a set of problems with one installation of WordPress (but not on several others). Two symptoms were most frequent. First, most publishing new or edit posts resulted in a 500 Error. The posts were fine, despite the message. Second, I was unable to automatically upgrade with either WPAU (an automatic upgrade plugin) or the built-in feature added later to WP. I also could not delete posts, though that bothered me less.

Recently, I upgraded to WordPress 2.9.2. As you will read elsewhere, the most common problem with this upgrade is that it requires MySQL 5 support but doesn’t tell you that until it is too late and  you are stuck unable to go back to the previous version. Yes, that’s simply astonishing and casts a pall on a product I love dearly – what were they thinking? Why not build a test into the very beginning of the process. Do NOT begin this latest upgrade without determining you have MySQL 5.

Although I felt like a rat in a maze, I came through the upgrade after several days. I had to create a new MySQL database with version 5 support. I found I was unable to import my backup directly – not sure why. I ended up cutting and pasting chunks of the back (which consists of SQL instructions) into an SQL form in PHPMyAdmin. Slow, tedious, but it worked.

And yet, when I was done, boom – there was the same damn error message despite a brand new database and WP installation! Even after adding a line to allocate more RAM – the solution I found most frequently on the Web – I still had this error message. I’m writing this to warn those in the same situation of the true culprit: a plugin for Google Sitemap. I disabled that plugin, and all goes well.