Javier Carazo

Included the patch that solve this in the next release.

Sorry I cannot reproduce the problem.

I have been able to import the user with an email like this without problems.

https://s3.amazonaws.com/i.snag.gy/4fs0Ox.jpg

How can I throw the error?

SOrry for the error. Next version will fix this.

Melapress Login Security have changed the namespace and I have to adapt the internal addon.

Maybe you have not activated this option in “Mail options” tab:

Enable mail templates:Do you want to enable mail templates??If you activate it, a new option in the menu will be created to store and manage mail templates, instead of using only the next one.

But this link should not be shown if “Mail templates” are not activated.

Thanks for your feedback I will fix it.

• This reply was modified 3 weeks, 6 days ago by Javier Carazo.

We use this function to check the email validity: https://developer.www.ads-software.com/reference/functions/is_email/

I am going to ask to core developers about including this kind of addresses and also I will change the way we check emails to avoid this confussion.

I would also improve the documentation of the error.

Thanks for your help! I will answer you asap when I have it ready.

This action scheduler library was created by WooCommerce and is used by more plugins because it provides great improvements for automatic task execution.

Do you have any periodic user imports enabled?

Thanks for taking your time to help us with this review!!

No worries.

And well, of course the hashes can’t be decrypted. Imagine if they were, what security flaws there would be.

The hashes are exported and imported as they are and the password still works because the function that checks the hash is the same but the content as a good hash function cannot be decrypted.

@brousseau44,

So you haven’t even tried it? Please don’t try not to saturate support without first reading the documentation or without first seeing if it doesn’t work.

And of course, the hashed password is as it should be because that is how it is transferred and how it works.

Sorry for any inconvenience.

Version 1.27.6 should fix this problem. Please update when you see it available.

Yes this is possible without asking about their passwords.

You should use only user_pass column (not password column) and it should work.

Please you have to be sure the CSV is well formed (please use LibreOffice or OpenOffice) and that the column is named “user_pass”.

The last version is the one available here: https://www.ads-software.com/plugins/import-users-from-csv-with-meta/

The next version were released and this error was solved.

You should delete it.

In the documentation tab you have some sample in CSV.

Did you see it?