I just spoke with the hosting company tech support, and they (as usual) put me on hold and did the mysqldump while I waited, all in about 5 minutes. (That's why we stay with them. No excuses, no attitudes, just great service.)
I will ftp it and run the test again.

Thanks again. You explanation and assistance was great. Easy to understand, complete, and appreciated.

RC

There are rumblings internally of trying to do some improvements to the exporter, but given the problem here -- which amounts to resource issues that will naturally vary from host to host -- I don't know that there's really a silver bullet. In other words, any changes we contribute would maybe make the exporter more easily extended but not necessarily more useful on shared hosting for large sites, since you'd still run into resource issues. In those cases, a mysqldump is generally cleaner anyway.

Another option, by the way, would be to export by date range and do smaller chunks, though I believe this can leave file attachments behind (something we do hope to work on eventually). Since you'll be able to copy your file directory over, that may be a lesser concern, however.

Thanks. I'll bounce that off the hosting company.

1. Can you give me a hint as to which command line exporter you use?......

2. Any chance we can look forward to a better fix for this issue from WP in the near future?

Thanks again, you very fast reply is appreciated.

We also tried adding the fix of:
/**
* Dynamically increase allowed memory limit for export.
*
*/
function my_export_wp() {
ini_set('memory_limit', '1024M');
}
add_action('export_wp', 'my_export_wp');

As stated at: http://beerpla.net/2012/04/13/how-to-fix-incomplete-wordpress-wxr-exports/.

Didn't work. (Acknowledging we had a different error message.)

We are using WordPress 3.4.1

Or, perhaps the simpler thing if your hosting company is willing to help, would be to have them do what's called a mysqldump of the database, which they can then slurp into the new database on the new server. This in fact will provide a better snapshot of your old site, as it'll include things like options and any plugin data that the exporter itself won't grab.

We are also having the same problem.

We are not hosted on wordpress.com, but on a commercial hosting service.
They are a large, well-known hosting company, one of the largest, and we have had excellent tech services from them for over four years. In other words, they are extremely capable, and knowledgeable with WordPress.
We have had exhaustive discussions with them as we have been running a trial move of a domain from a shared account onto its own separate hosting account. The test has been marked and hampered many times by this same problem: the xml file is incomplete.

We have the same problems agrorama describes, as do a number of other WP users.

I would like to know what you did differently that allowed you to export agrorama's xml file and email it to them, that they were not able to do, or was not covered in the forums or codex.

I am leaning to the conclusion that if wordpress.com can do it, there is a solution, but the process is not evident in the wordpress.org forums.

Can your provide the process please???

I'll ask you once more to download the XML for me during the next couple of days.

Thanks a lot

During the next 2-5 days, just after the domain name transfer is completed, I'll need another, updated export . May I post again here to ask for it or should I contact you in another way?

Thanks again

Only 7430 posts (out of total around 9151 published articles) are included.

The latest article included in the file was published on 26th of December, 2011.

I'm exporting the content to my local server, having increased all necessary limits (download limit, max execution time etc) in php.ini configuration file. Everything seems to work fine from my side, so I think that it's a WP issue, as the downloaded XML is missing the closing <channel> and <rss> tags. For some reason, some WP posts are not included in the XML.

For example, I tried again 2 days ago and the last article included in the XML file was from July 16, which is a better result compared to my previous attempt, during which many thousand articles were missing (everything after January 2012).

I would appreciate it if you could provide me with some help in order to get a final & full XML export (sometime during the next couple of days, after the domain name transfer proxess is confirmed) or make it easier (WP server configuration?) for the whole process not to be interrupted during my next & final export.

OK, I'll be patient, thank you :)

Can I have some official support for this please??

Also, channel and rss tags are not closed at the end of the XML (probably because of the partial export).