-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add leads 3 support #30
Conversation
Me and @aschempp floated a different idea a while back. iirc it might make more sense to store the duplicates serialized into the respective fields. So if you have a field called @koertho wdyt? Although I don't know how it should handle checkboxes (not sure how it is handled now). |
The current way is better for my case, if I understand correctly, since I store first and last names and keeping them together makes more sense :) |
Thank you @koertho |
This PR adds support for leads 3.
Since Leads 3 do not offer the storeLeadsData hook, I needed to use the processFormData hook, where I load the corresponding leads data set. I also needed to adjust some code to make it compatible with haste 5 and changed database field names. The code should be compatible with haste 4+5 and lead 1+3.