Bulk add user registrations to a WordPress site using a variety of methods.
Lots of things, mostly inspired by user feedback. More options for specifying column order on imported data, custom user role support, just about every meta data option you could need, plus a pretty big rewrite of most of the standard functionality.
AMU is designed using only WordPress standard functions with no direct database insert code. This is a slower but safer option. As such, each user processes separately, running checks along the way to make sure there are no conflict with current users or any bad data. If you're adding lots of users, just be patient. If you get time-out errors, check out the next question.
In testing, adding over 500 users at a time can cause issues with memory in WordPress and in your browser - please try the method explained at http://addmultipleusers.happynuclear.com under Usage - Known Issues for a few workarounds. The simplest method is simply to split your CSV data into groups of about 300 or so, if its feasible for you to do so.
Yes. Version 2.0.0 introduces the ability to choose from all Roles you have defined in your site. AMU does not, however, create Roles for you. You should use a plugin such as User Role Editor to first create the roles you wish to use when bulk adding users. You can then use a 'role' column in your CSV data to specify a role for a user, pick a default role in the Settings, or pick one from the drop-down list on the Form interface.
Access the Add Multiple Users plugin from the any site within the network to use its functions. Users added in a subsite are added to the network and assigned a role for the subsite they were added through. If you're a Super Admin, you can also change some settings for your Network (look under the Users tab in Network Admin) to limit accessibility to the plugin from subsites, plus receive copies of user registration details when the plugin is used on any of your network sites.
These functions work by taking your data (whether you upload a file or paste data into the your CSV Input info or Email List functions) and translating it to user accounts. You can either send them all to a Form, which lets you review each line of user information piece by piece before adding the users, or simply just go ahead and register them using the Skip button.
This function automatically creates new user names from the first part of the email, generates a password, and uses this information with the provided email address to create a new user account. You can even send this information to the Form interface to add additional information before processing your new user accounts.
In the Settings you can choose to predefine your column order, use the first line of your CSV file as the column order, or define it after uploading your file either with the Manual Entry on Upload or Dynamic Sorting on Upload functions.
For standard WordPress user and user_meta fields, you must use the exact name of the column in the database (eg user_login or display_name). To define a role, use the column name "role" to define where the user's role appears in a line of data. For custom user_meta information, just use any name that isn't standard and it will be added as a new meta field for each user.
If you want the plugin to skip a column of information, just use the column name "ignore" (multiple times if necessary) and the plugin will skip this column of information.
A user_login, user_pass and user_email is the base necessity of adding a new user. Passwords can be generated in left blank, and emails addresses can be created for you if you use the Force Create Email option.
Force Fill Email Addresses works by creating a fake email for users whose email address field is left blank, utilising the new user's Username and a .fake extension to create a non-functional, dummy email address. This is NOT a function I recommend using unless absolutely necessary. User email addresses in WordPress are highly recommended if only to retrieve a password if it is forgotten. In a particular real-world scenario I found I had to add a user who had no email address due to their lower socio-economic circumstance and it was unrealistic to deny access to a potential user because of this as the site was targetted specifically for that demographic of user. The function is there if you need it, but its not a recommended solution (try getting your users free Gmail accounts or something in the first instance!).
Not yet. This seems trickier than I hoped, and any suggestions on how to achieve this are more than welcome. I'm working on this for inclusion in version 2.1. However, this function does exist when using the Add Existing function (if you're running Multisite).