Thread

I am importing members into an ee 2.2.1 site from a 1.6.9. I exported the member data into a txt and converted it into an xml file. In the text file, the Join Date, Last Activity, etc, show as UTC dates. When I convert that text file to xml in my ee 2.2.1 site the dates change to: 2010-07-14 13:36

When I import this data the dates are messed up because it’s expecting UTC dates.

I tried to use the converter in the 1.6.9 site, but it defaults all the mapped fields to the accpt_admin_email field. And I don’t want to convert every single field, so I can’t really use this.

There is probably another converter somewhere, but it would be nice to have the ee one working.

Hi Kelly,

So I’m assuming you needed to export and import the members as opposed to just upgrading the EE 1.6.9 site to EE 2, correct? In that case, why not create a template that will output your members in the Member XML Format that EE2 will be expecting instead of worrying about converting a delimited text file?

Yes, I need to export and import the member data instead of updating the site.

This is a good idea about creating a template of member data, but then why is there even a CSV to XML converter? Isn’t this a bug?

I suspect there may be a bug in there that you’ve found, and we’d be more than happy to accept a bug report on it if you’d like to help us track it down.

In the interest of getting you up and running quickly though, I would personally just set up a template of member data. It’s not a clean solution, I know.

If this isn’t an urgent problem, however, and you’d be willing to help us confirm it as a bug, I’m all for it. Just let me know what you’d like to do!

Sorry, just getting back around to this. This works great. I did have an “&” character in a field that was giving me this error. So I validated and changed it to & and it works. This was the error if anyone runs into it:

error on line 343 at column 25: EntityRef: expecting ‘;’

Maybe that will help someone else.

So I think this will work for my purposes. Thanks for the idea.

Maybe I spoke too soon. I tried to import the validated xml and it give me this helpful error: Unable to parse XML.

So it appears that is it more of a memory thing and less of a parse thing. I can import 25 fine, but 30 gives an error.

Thanks for keeping us updated on your progress. Are you able to import more entries if you raise your PHP memory limit?

I raised it to 128m and it still didn’t let me do more than 25. I also wrapped the xml in the <![CDATA[ tag. I found another post that seemed to have a similar problem so I have been posting there too:
http://ellislab.com/forums/viewthread/196144/

Sorry I will just stay on this post for now 😊

Hi Kelly,

Banging off of what Brandon said here, could you perform an export and import of just the 15th through the 30th members and see if it borks there? If so, and we know an import of more than 6 members has worked before, then we will have narrowed the problem down to something in the records of one of those 6 members.

Sorry to have let this languish. Since it was a old ee site, I got around the issue by upgrading the old site and transferring over the upgraded member tables to the new site. Thanks for your help though.

kellypacker,

Just making sure you are all set now? Let us know if we can be of further assistance.

Cheers,

All set. Thanks for checking.

Closing this one out.

Cheers!