• Resolved Jose

    (@giuse)


    Hello,

    in my opinion, when you export and import a website the plugin should not touch any email.
    For example, if the original website at https://sample-domain.com is migrated to https://sample-destination-domain.com, and you have emails like [email protected], they should not be converted to [email protected].

    In my case, after migrating the website to a local installation, the email was converted to info@localhost which is even a not valid email.
    If you have WooCommerce a not valid email triggers a fatal error.

    For me, this thread is really not urgent. I know how to solve it, but I thought you should be aware of this.
    Take into account that those who transfer a Woo website to a local installation, then they will have a fatal error on the destination website.

    In any case, then you very much for this amazing plugin.

    Have a great day!

    Jose

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Yani

    (@yaniiliev)

    There is an options available under advanced options on export:
    “Do not replace email domain (sql)”. If you tick this options, the email will not be replaced. Let me know if this solves the issue for you.

    Thread Starter Jose

    (@giuse)

    Hi @yaniiliev

    sorry, I didn’t notice it. Thank you so much for your support and the amazing plugin.

    Have a great day!

    Jose

    how did you fix this? I just ran into this issue.

    Thread Starter Jose

    (@giuse)

    Hi @brandon0814
    I’ve solved it by following the recommendation given by @yaniiliev

    There is an option available under advanced options on export:
    “Do not replace email domain (sql)”. If you tick this option, the email will not be replaced.

    @giuse I no longer have access to the original version. any suggestions?

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Emails should not be changed’ is closed to new replies.