WXR uses conflicting file extensions

[scoop0901]

Similar to bug found in ​ticket 3840.

Using WordPress 2.1.2, if you export the xml and try to import the file -- unchanged, even using the default name -- the import fails without any reason given. The file shows up in the "uploads" page, but it does not restore the posts and everything to the new blog location.

The import page for importing from WP says it should be a *.wxr file (not the xml file that was exported), but even changing the file extension to wxr does not resolve the matter.

Nothing was imported to a NEW MySQL database. It was attempted with five new databases on three different servers by one person, and in a different country, on a different server, by another fear` (in #WordPress).

_

• ​Ticket #3840

[scoop0901]

Looking at 3840, this is not very similar. I may have not clearly written a note to myself when I was jotting down info for the bug.

I did send the actual WXR file to Lloyd Budd at Automattic, so he could look at the code and file to see if he could determine what the problem is. Since sending it, though, I haven't heard back from him, even to confirm that he received the file.

[foolswisdom]

I did receive your email the other day. I was waiting for some of the WXR patches be added to trunk to give me some comparison.

[rob1n]

So, I see two solutions:

1. Make the importer use .wxr instead of .xml

2. Allow .xml *and* .wxr to be imported

I'll attach patches.

[rob1n]

This one makes the exporter send a .wxr file.

[rob1n]

I could upload a .xml file (created straight from Export, same name) and it imported fine.