Any plans of updating this for 5.0?

Yes!

User Import module will be updated to Drupal 5. Can't say how soon, depends on my having free time, or someone comissioning the update, whichevr comes first.

+1: I could use this too.

[great work Robert! Every time I need a module, you're there!]

+1

I'm new to drupal, but since I need the module now, I would dig into the code if someone could point me to the relevant sections.

How about someone else scratching that itch? :-)

Attached is a patch to upgrade to 5.x.

The only changes in behavior are where in the menu tree user_import falls (moved it under admin/user/user as local tasks) and it automatically deletes files from fully imported processes. I couldn't conscience leaving files with usernames and passwords available to any spidering script kiddy. :-)

Otherwise, I believe this behaves identically to the 4.7 version. (I have noticed one bug: all accounts are active by default.)

Great module! Super useful.

Cheers,
-Mark

patch fails. I just downloaded the 4.7 version and it looks a lot different from what you have in your patch file. Are you using a different version to patch from?

Yes. HEAD. There were changes to HEAD (according to the CVS logs) that did not make it into the 4.7 branch.

For us Drupal 5 Users. Is it possible to import User data through phpMyAdmin?

I think we'll set up a 4.7 site, import the users then upgrade it to Drupal 5.

Sounds good will that work?

I've updated the patch originally posted here by mfredrickson. This is against 4.7.x-1.x-dev, and only contains two real changes. First, one of the function name changes was missed, and has been fixed. It now also allows the characters "@_.-" in usernames, to allow email addresses as usernames.

User Import module has been updated to Drupal 5.

I didn't use the patch because I had already done some of the work, and am coding towards some new features. Thank you anyway, was useful for reference at several points during the update.

New version allows the characters "@_.-" in usernames.

Haven't implemented automatically deleting files from fully imported processes, will do that in near future, but want to make it an option (on by default) and change the user interface to accommodate the new behaviour.

This new version was tested a bit, but not extensively, so I'll leave it as a 'dev' release and wait for some feedback before releasing it as 'stable'.

Hi there,

I tried it today in Drupal 5 and it did not work. I tried to eliminate all my mistakes but I am not sure if I did it right because I never used the module before. Anyways: I can upload and define the fields just fine. When I hit the Test (or Import) Button though, I get a table saying that my users were processed but could not be imported - instead I get errors. It is not reported what kind of errors.

Does anybody has an idea? I tried it with an import of aprox. 4000 users, when it did not work I tried it with 10, which didn't work either.

ron_

Could you try importing the sample.txt file that's included with the module.

Also can you post a screenshot of the errors page (when you click on the errors numbers).

Never mind! It actually was my fault! It didn't seee, that our email adresses weren't valid. I did not see this right away because the error-log did not work with more then 3000 errors. (I don't know if this ist because od our default ini_set and a process time limit, but it died just quietly) With lesser entries I saw that the email adresses weren't right. Thanks for your quick reply.

Thanks for the feedback.

It's a good point, the errors page needs pagination - I'll create a separate issue for that.