Thread

I’m getting an error when trying to import members via the import utility. It is simply saying “Unable to parse XML”. Is there anyway I can find out WHAT is causing it to trip up. It’s fine in the normal XML validation tools.

Hi, buggles.

What I typically do is create a .csv file, and convert that .csv file to xml via the Member Importer. That way I know the content is valid xml.

Would that be a possibility? At least for a subset of these just to see if it gets you past the hurdle?

Not easily no, I’m using XML to avoid the nonsense with CSV formats. The validator I’m using is well tried and tested, and every other XML tool I have validates the file. I’ve done some testing, it imports fine in 2.1.5 and 2.1.2, just not 2.1.3 (latest build).

Hey buggles,

That’s interesting; I wasn’t aware of any changes to the XML importer other than this one (which sounds related). In any case, glad it’s working in 2.1.5. The final release will be out this month, so thanks for your patience.

I won’t be using 2.1.5 for some time to come, the site we need to go live with needs to go live with your currently released version. Is the response “sorry… you are out of luck we don’t back port fixes”?

I’m not sure what the relevance of that other issue is (perhaps I just don’t know enough about EE).

buggles, we don’t have any sort of xml checker that will go through and tell you what’s wrong with the file. Which is one reason I suggested going with a .csv file first, and let EE generate the xml file for you.

You could try with just a single xml record, does that work? Then a larger subset, does that work? Painful, but without seeing your file or testing it, we can’t offer a solution other than that.

I haven’t been asked for the file! Happy to supply it, but obviously not to upload to a public forum.

I’ll be happy to attempt to see what happens with your particular file. Can test in local 2.1.3 20110411 build. Check your email in a few minutes.