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

    (@carazo)

    We use this function to check the email validity: https://developer.ww.wp.xz.cn/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.

    Plugin Author Javier Carazo

    (@carazo)

    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?

    Thread Starter sootsnoot

    (@sootsnoot)

    The error has been, and continues to be, solid for me. Perhaps it is plug-ins. I will dig in some more and try deactivating plug-ins. And send you a screenshot. Thanks for looking into this. But at this point, it is not resolved for me.

    Plugin Author Javier Carazo

    (@carazo)

    Did you try without any other plugin activated and with a default theme to avoid any interaction?

    I am going to release the new version now that fixes all the other problems.

    Thread Starter sootsnoot

    (@sootsnoot)

    I just upgraded to 1.27.7 and no longer see the problem. I didn’t try it again with 1.27.6 with other plugins deactivated.

    Plugin Author Javier Carazo

    (@carazo)

    I have not changed anything about it. But if it works, this is great.

    Thread Starter sootsnoot

    (@sootsnoot)

    Well, actually, I’m seeing the problem again now. Guess I didn’t have other emails like that: https://drive.google.com/file/d/1DrMihKrr8SipzLmapF8oYs1JE02MdAH9/view?usp=sharing

    This import basically worked, in that the user got created as a subscribner with the specified email address. However, they were not given the specified password of Please-Change, but rather a random password:

    <pre>
    Your data to login to this site is:

    URL to login = https://wp.freestylefarm.org/wp-login.php

    Username = TEST

    Password = iTAE*h2@Dj^^
    </pre>

    • This reply was modified 1 year, 7 months ago by sootsnoot. Reason: Show the email with login credentials
    Thread Starter sootsnoot

    (@sootsnoot)

    And it appeared to give all of the name fields, like Name, display_name, nickname, user_nicename, the value TEST, the user_login.

    Plugin Author Javier Carazo

    (@carazo)

    It seems your CSV is not well-formed.

    Are you using Libre Office Calc to be sure the CSV is well-formed?

    Thread Starter sootsnoot

    (@sootsnoot)

    Yes, I’m using Libre Office Calc. I open the csv file with Calc, which does not complain about its validity, edit a character or two, and then save it back to the same csv file. Here is the exact csv file I’m using. This produces the error Invalid email “user_email” on the Import page. I then go to Users on the admin panel, and see user TEST created with Username, First name, nickname, and display name all set to TEST. And the email delivered to [email protected] contains:

    <pre>
    URL to login = https://wp.freestylefarm.org/wp-login.php

    Username = TEST

    Password = NGm6qs3A4MwJ
    </pre>

    So the names and password specified in the csv file were all ignored.

    Plugin Author Javier Carazo

    (@carazo)

    This CSV is bad formed. The first row should not exist.

    Thread Starter sootsnoot

    (@sootsnoot)

    Oh my, very embarrassing! I don’t know how that got there. I thought maybe the export did it, but apparently not. Anyway, it got there very early on in my testing, and I didn’t think anything of it, and just tweaked the values starting at the 3rd row, like the email address, which did wind up getting imported.

    Sorry for being such a dope.

    OTOH, it would be nicer if the import tool would report an error for any csv file containing a first row that did not begin with “user_login”. I know you’re very busy making this free plugin even better, but detecting that error should be “really easy” :-)…

    Plugin Author Javier Carazo

    (@carazo)

    No worries.

    About your suggestion this is not a good idea because many users use “Nombre de usuario”, “Username”, “Login”… or any other.

    I have never had anyone try to upload a file with an initial line like this before. So seeing the rarity of the case, I see no reason to improve the bug reporting here.

    Thread Starter sootsnoot

    (@sootsnoot)

    I agree with you – I don’t even know how that line got there, so it’s hard to imagine anyone else doing something like that. The documentation clearly specify the field names to use, and that isn’t one of them.

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

The topic ‘Cannot import email with gmail “+” syntax, and poor error message’ is closed to new replies.