• Resolved twmoore3rd

    (@twmoore3rd)


    First, thank you, thank you, thank you. I have a set up a private password protected website for nearly 1000 users. “Import users from CSV with meta” saved me hours of error-prone tedium as I typed in the users information. “Import users from CSV with meta” worked out of the box, minimal learning on my part, and I was free to continue developing the rest of the site. Thank you, thank you, thank you.

    But some cracks have appeared. 🙁 User name collisions are apparently now well handled. If John.Doe is already a registered username and a second John.Doe is encountered, the import of the second John.Doe apparently fails but no warning/exception is noted. Yes, I know that exceptions are irritating to deal with but it would be nice if failure conditions were email or otherwise listed at the end of an import.

    Note: This would not be an issue if one is taking a CSV formatted file of current users and importing to another site as WordPress wouldn’t allow for the duplicate username. I am encountering this condition as I am importing a CSV formatted file of users from an external non-Wordpress data source and not a current WordPress site.

    With out the collision detection and flagging, “Import users from CSV with meta” rates 4/5 as collision detection and flagging is important. With collision detection, “Import users from CSV with meta” is a 5/5.

    Thank you for the work that you do. Much, much appreciated.

    https://ww.wp.xz.cn/plugins/import-users-from-csv-with-meta/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Javier Carazo

    (@carazo)

    Thanks for your words twmoore3rd.

    I want to improve this plugin to have another 5 stars rating 🙂 so tell me, what would you do exactly to manage username or user-email collisions?

    Thread Starter twmoore3rd

    (@twmoore3rd)

    If I had the expertise to expand your plug-in, I would:

    1) Display a warning message indicating that the following users have not been added due to collision in username or email address (extra points for stating the exact reason, i.e., username John.Doe already exists);

    2) Offer or just automatically email the above message to the admin address.

    Again, I may have been using your plug-in in ways that you may not have imagined. If I was merely importing a CSV from an export from another WordPress site, I wouldn’t have this issue as WordPress doesn’t allow duplicate usernames or email addresses. However since I am importing from an non-Wordpress source, I am opening myself up to collisions. Do not know if “Import users from CSV with meta” was designed specifically to import from other WordPress sites or from all external data sources. If the latter, the collisions issues are my problem.

    Plugin Author Javier Carazo

    (@carazo)

    Thanks for the idea, I would implement 1) as soon as I can.

    This plugin was developed to help us in Codection to import lots of users easily, later I release it and we are really satisfied with the result, but yes, I have to improve it.

    When I do it, you will receive an automatic update, I expect doing it soon.

    Thanks!

    Thread Starter twmoore3rd

    (@twmoore3rd)

    THANK YOU. Let me know if you want help in beta testing, etc.

    Plugin Author Javier Carazo

    (@carazo)

    twmoore3rd,

    I have just done it, read it in the readme:

    = 1.2.2 =
    * Thanks to twmoore3rd we have created a system to detect email collisions, username collision are not detected because plugin update metadata in this case

    In a future version we would include some checkbox to test if you want to update or to detect collisions between usernames.

    Plugin Author Javier Carazo

    (@carazo)

    There is no new message in this thread, so I would close it, if you need something more tell me.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Collision Log’ is closed to new replies.