Daryl L. L. Houston (dllh)

Not sure why this would happen, and I can’t imagine it’s related to the changes I pushed today. The plugin specifies that it requires WP 3.0 (so 3.1 should be ok), and the two function calls I added (wp_nonce_field() and check_admin_referer()) date to way before even 3.0. At any rate, it sounds like you’re having trouble with the plugin installation process and not the plugin itself. You’ll probably need to work with your hosting company or consult error logs to figure out what’s happening. You could also perhaps try downloading the plugin zip file, unzipping it, and uploading the resulting folder (named blogger-importer) into your wp-content/plugins folder.

You can still import into wordpress.com, but the media won’t come over automatically because Posterous has actually shut down the media hosting service. Your backup file contains all your media, but you’ll need to upload the files manually. Unfortunately there’s no way around this.

Another option, if you’re savvy enough, would be to just upload the files from your backup. The html export (vs. the xml file you use to import into WordPress) contains entries with references to the images. So you could put the html files and media folders in a subdirectory on your web server and at least have the content hosted, though it would then be static content (no comments).

Looks to me like wp_mail() is getting called without a valid email address, which suggests that somehow, maybe the user doing the edit has a null or empty email address. Plugins trying to do clever things with posts could cause this to happen, I suppose, but I think you’d have to check with the WP_Types vendor to further troubleshoot this, as the code doesn’t seem to be available for me to peek at.

Great, thanks for following up!

Sorry, was unable to look at this for a while. I peeked tonight and have shipped a new version of the plugin that I believe should resolve the issue. I’d be grateful if you’d test and let me know how it works.

What WP version are you running?

Hey, @teemutalja, that’s great! Thanks for sharing.

@wzinet, the importer doesn’t do anything to filter out .mov files, so it’s hard to say what’s going on here. Maybe check that your site settings aren’t preventing .mov files from being uploaded?

I’ve answered this in a few other Posterous threads. Please browse around for the answer. The quick answer is that the importer has no idea what video players you may have installed in your site and so can’t know what code to use to insert a player. I wrote a plugin to help one guy, and he wrote the process up in detail.

@stephendavidp, it means that Posterous is rejecting your login credentials.

I really recommend backing up your Posterous blog using their Backup option, importing into wordpress.com, and exporting from there to import into your .org blog.

I don’t know the GPP slideshow, but you ought in theory to be able to edit a single post manually to make it use whatever you’d like. ??

The issue with videos is that the Posterous plugin can’t make assumptions about what video player your site may have. If it assumes you have foo.swf for playing videos and you have bar.swf instead, the videos’ll be just as broken as if they still point out to the Posterous site.

I made a plugin for helping a guy fix video links for his import, and he documented the process here.

I think the failure to fix up image urls is because that part of the process doesn’t happen until after everything has been imported. So if you keep importing until all the content is there, the backfill should happen at the end (if I remember correctly).

@hofjes, you’ll need to contact wordpress.com support to get your issue resolved. Even if you post in the forums over at https://en.forums.wordpress.com/, someone should take note of your request and call it to the attention of the support staff there.

All I can say is that it’s worked for me with big sites and very few issues, and that your mileage may vary with respect to how responsive the Posterous API is. Between that and bugs that surely exist in this beta plugin, results are bound to be inconsistent.

I suggest you download the backup that Posterous makes available, import into a blog at WordPress.com, and then export from there. You may still run into issues, but that style of import is more easily testable/supported.

It’s pretty much impossible to debug the sorts of things you’re encountering because even if I had access to your Posterous site, the API may suddenly become responsive, my php settings might be different, or any number of other things may change that would keep me from experiencing the same issues you experience.

Great, I’m glad it worked for you! Guess we’ve just proven the old adage “if at first you don’t succeed…” ??