Open piotrekkaminski opened 6 years ago
From @jordanbrauer on June 30, 2017 17:23
Are you able to use the REST API? I do everything via backdoor with the API and Guzzle in a CLI application I made with the Symfony 3 Console Component which seems to work just fine.
From @MattDelac on July 4, 2017 15:54
Hello @jordanbrauer ,
Thanks for your reply.
I will get a look at the REST API. Which on do you think I should use in order to send the welcome email ? However, API is a bit long and to synchronize 7000 clients per day, it will take too much time. The csv import is just fine. I use a module that let me import any csv with a cli (==> easy to script)
Thanks in advance
From @magento-engcom-team on October 2, 2017 9:30
@MattDelac, thank you for your report. We've created internal ticket(s) MAGETWO-80547 to track progress on the issue.
From @jigar48 on December 14, 2017 7:25
Hello M2,
Is this issue is fixed.
@MattDelac is this issue solved? Did you get a solution? I have the same issue.
Thnx
After research with @sawebvisum during a contribution day we found that this is probably not as easy as just adding the send email call. The frontend, admin and webapi all end up in the class app/code/Magento/Customer/Model/AccountManagement.php
with the method sendEmailConfirmation(CustomerInterface $customer, $redirectUrl)
which takes the customer object filled with information.
For our opinion it would not be a good idea especially with large scale imports to load all the information for customers and loop through each to send the email. In this case I think I would good to either work on a method that can be called using the information we already have at import or a message queue system that we can push "Customer registration emails to send" which will then be processed via a cron at a later date.
I think it would be good to have a discussion from the architecture team as to the best approach here before we start working on this.
From @MattDelac on June 26, 2017 12:57
Preconditions
Steps to reproduce
Expected result
Actual result
Is there someone that knows how to bypass this ?
Copied from original issue: magento/magento2#10055