danfoy

Count me in too. Seems like a very common problem.

In my case I’m trying to export from a live site to a local development version running in a Vagrant box.

This thread is like the second result when you google ‘wpress file format’, so I suspect a lot of people are going to see it.

I came to this thread looking for a way to poke around inside the file and had the same gut reaction as @aguett, @alex310 and others. But also I appreciate that the plugin works fantastically well for migrating, and after looking at the plugin homepage it doesn’t actually seem to mention being used as a backup solution anywhere.

I agree that it would be fantastic if the files generated were more straightforward ZIP/tarball archives of the native WordPress directory structure. However, if using this format is the price we have to pay for being able to squeeze your entire site (including media!) into one huge file *and* have that huge file be able to bypass upload size restrictions *and* be very fast, personally that’s a tradeoff I’m willing to make. There are plenty of other dedicated backup plugins but none that make frequent migrations (as are often necessary when developing) this straightforward.

Amazingly fast response, thanks a lot! Great work on the plugin

esmi, based on your certainty I’m assuming you have experience with setting up servers, so could you let us know specifically what part of our servers (or php-config etc.) are badly-configured? This way we can add it to a trac ticket and everyone can benefit.

Closing the php ?> tag in my theme’s functions.php file fixed this for me too.

This doesn’t seem great practice, though. If someone finds out what’s causing the problem I’d appreciate it if it was posted here.