Good overall, but had some issues

@euphemism,

Good morning, thanks for your review and for your comments. Anyway, please ask first in the support forum if you have any problems before posting here. As you can see there we answer ASAP.

Anyway I tell step by step.

If you check the box to send out the email and do NOT allow it to reset the password, it will send out an email that says “Your password has not been reset.” I wish I had known this ahead of time.

If you do not allow to reset the password and you in the email place the **password** tag, we have to write it.

This is not an error.

How would you improve it?

I had already imported the users, before re-importing them in order to send them the email, not believing their password needed to be reset. This created a lot of confusion on the recipient’s part.

But the question here is: why did you include the **password** tag in the email?

This plugin nor WordPress nor anyone, know the password saved in database. You can only check the password is correct (hash function) but you will never know which password is stored in the database in a safe way.

Also, the system crashed part way through and did not import all the users; the resulting page went to a 404 and imported only 2/3 of the users. Importing a few at a time was fine but 140 seemed too much.

This a problem from your hosting. It cut the execution. We are working in a solution based in JS to avoid it in import (in export this is already done).

It also wouldn’t work if I had any default role set.

Sorry I don’t understand this last point.

Thanks for your reply. I did include the **password** tag in the email, but if you don’t click the box to allow the password reset, it doesn’t include the password in the email. I didn’t know this ahead of time, and wish I had. I know it’s not an error, it was more not being aware of the logic involved in storing passwords.

The import has an option to include a default role. If I had any role selected, the import failed. Perhaps because I had a role defined in the spreadsheet? No big deal, once I figured out that deselecting the default role made it work.

Thanks for working on a solution for the issues with importing/hosting.

@euphemism,

When you tell me that the import fails here:

The import has an option to include a default role. If I had any role selected, the import failed. Perhaps because I had a role defined in the spreadsheet? No big deal, once I figured out that deselecting the default role made it work.

What happens exactly?

Well this is odd – I’m not able to replicate the error! I’m so sorry. I tried – the error it gave had something to do with roles; once I unchecked the default role in the import interface, the import worked.

OK, this is great. Maybe something in your site fails and affects this plugin.

If this does not fail, please consider updating the rating.