Migrated from Redmine #1358 | Author: Artem Panfilov Status: New | Priority: High, I’m very impatient | Created: 2025-02-11
When public book method used with client data prefilled with email, name and phone and booked lets say 5 events. 5 different client records created. Which is absurd. it’s a simple email check. We can send cientId if there is no other way to say that it’s the same client. PS we quite aware of client auth process, but we need to use public book method which is working fine, it’s just this side-effect which is overloading al the system you have.
this is correct behavior if Customer login plugin is not enabled
I would argue that its correct, since we obviously not providing the way for customer to login. Customer login feature will require customers to authenticate with login and password and we don’t use passwords, only Social Logins and OTP codes.
Is there a way for you to fix it, since multiple customer records with identical data created is wrong on so many levels. Customer login feature will solve that problem introducing requirements to store login and pass.