Moving from Posterous to self-hosted WordPress

Posterous  has refused to convert my video for the last time. It was bad enough that they started “Spaces” (adding extra clicks and not working in Firefox anymore), then they got bought by Twitter. But the whole point of my ds106 blog is posting my own audio and video creations, so this is the last straw.

I read at Lifehacker that the self-hosted WordPress plugin Posterous Importer didn’t work , but they’ve fixed it and it does, very well.

So to do this, I created a database on my hosted server and installed (another) WP blog from Then I followed the 5 minute install instructions. Then I made a mistake.

At this point, what I needed to do was create a plain text file called php.ini that had the settings I want so I can upload big media:

 max_execution_time = 300
 max_input_time = 600
 memory_limit = 60M
 upload_max_filesize = 200M
 post_max_size = 32M

Then I needed to upload this into the wp-admin folder before I imported my Posterous.

Next step was to get the plugin Posterous Importer and activate it, then give it the information to download my blog. It worked very well  (except that it linked back to Posterous for the files that were too big because I didn’t do the php.ini file first!).

Because I’m using Quicktime files, I also needed to get the QuickTime Embed plugin  and use its shortcode to create a player for the files I uploaded, so I did have to clean up a few posts, but overall this is going great.

5 comments to Moving from Posterous to self-hosted WordPress

  • This is really good info to know, especially about upping the PHP defaults for doing a temp big import job. Thanks 1,000,000

  • Additional note. The images moved fine, but they were scaled by Posterous within the posts. I’m finding it necessary to add them again from the Media Library, removing the URL link for each, to get them to show at their proper size, animated and not blurred.

    So actually, this is a pain, going through all the posts!

  • I don’t blame you–I used it last semester, only to find that the PCs in the campus computer labs used an old version of Firefox that wouldn’t work with Posterous. It gave me all kinds of headaches. It never occurred to me that Posterous wouldn’t work on an older browser, nor that our IT dept would put PCs into labs, lock them down to keep users from changing settings, and then NEVER update the software until the PC is replaced.

    • The new Firefox is terrible too, at least on Mac – I can’t edit in Moodle or edit in Posterous at all. Updating software in a lab is hard, but that’s why all that stuff should be done through virtual labs.