skipped rows feedback?

@markbildner,

In the page with the import result, you have in every row the error or problem of every user (if there were an error).

Did you see it?

No, I see the following when the import runs:

Importing users

Ready to registers

First row represents the form of sheet

Inserting and updating data

And then I see the list of imported users. The skipped users (duplicate userID) don’t show up. This particular output is from the front end page, but I got the same result from the admin console. There is a button to see the results, but that is just the user screen. Am I missing a setting or perhaps looking in the wrong place?

In case it was not clear, I am NOT updating existing users.

• This reply was modified 4 years, 7 months ago by markbildner.

@markbildner,

What you see is what we show now.

Duplicate user ids should have some kind of title like “This user was called before like: “User already exists as:”

Any reason this message is not showing?

I just did a default install of WordPress 5.4.2. I ran the following file through twice, with Update Existing Users set to “no”. The first time it imported all 3. The second time it imported nothing, but it displayed no errors. The only plugin other than yours is Loginizer.

Username Email display_name first_name last_name
bobsmith [email protected] bob smith bob smith
susansmith [email protected] susan smith susan smith
alicesmith [email protected] alice smith alice smith

• This reply was modified 4 years, 7 months ago by markbildner.
• This reply was modified 4 years, 7 months ago by markbildner.

@markbildner,

Where is the error there?

You are importing existing contacts with update to no. It does not import (because exists) nor update (because you set it to no udpate).

I don’t know which error are you trying to find.

If you are importing new users, and some of the list is rejected because the username already exists, there is no notification. The only way to find the people that you missed is to manually compare the file with the screen output. I would think this should show up as an error: “username already exists” or “email address already exists”.

@markbildner,

No because most of users, use this plugin to update periodically their users so if we show a message always, it has no sense for them.

Yes it should be conditional on whether you are updating existing users. But nevertheless it makes sense to be there. it is difficult to check to see if a new username is going to collide with an existing one!

@markbildner,

We can create an option to show always if an user exists.

We have to prepare a new UX so now it is complicated to include it but in the future we will do.

Thanks for the idea.