Works mostly

Importing a couple dozen posts including attachments: ✓

Importing a couple dozen pages including attachments: ✓

Importing ~100 media files including attachments: ✗ HTTP 503.

I’ve tried disabling leech & hotlinking protection on the source domain. I’ve tried increasing the PHP memory_limit to 512MB, max_execution_time to 0 (unlimited), max_input_time to -1 (same as max_ececution_time), post_max_size to 128MB, upload_max_filesize to 128MB. Note that the media files I was attempting to import were less than 100MB combined. But I kept getting a HTTP 503.

The way I eventually got around it was as follows: start the import of media, including attachments. When it fails, do it again, but this time without attachments. You will get a list showing you which media files were actually imported already and which haven’t been imported. Now edit the xml file and remove all entries (delimited by <item>…</item>) that have already been imported.

Start the media import again, with the edited xml file and include attachments. If it fails again, repeat the import but without attachments. Note files already imported, remove from xml file, rinse and repeat.

Tedious? Perhaps. This plugin’s fault? I honestly don’t know. My cheap hoster’s fault? Entirely possible. My skills not being as good as I think they are? Definitely an option.

But was it the quickest way to get the job done? Yes, for me it was. Hopefully this information can help someone else. Or perhaps at least it’ll help the plugin author to make this plugin more foolproof ??

• This topic was modified 4 years, 8 months ago by Bart Kuijper.
• This topic was modified 4 years, 8 months ago by Bart Kuijper. Reason: typo's