|
Dairywomensnetwork
|
November 12, 2019 at 6:17 pm
The system seems to create two IFS contacts when registering for an event. One contact for full details and the other ONLY contains the email address.
It looks to be related to having both “Event Espresso – WP Users” and InfusedWoo by InfusedAddons.
Here is the some system details…
WordPress 5.2.4
WooCommerce 3.6.5
InfusedWoo 3.11.8
Event Espresso 4.10.0.p
Event Espresso – Infusionsoft (EE4.4+) 2.2.3.p
Event Espresso – WP Users (EE4.6+) 2.0.17.p
|
|
Josh
|
November 12, 2019 at 6:50 pm
Hi,
If you temporarily deactivate InfusedWoo 3.11.8 (and leave everything else activated), then test a registration, is only one IFS contact created?
|
|
Dairywomensnetwork
|
November 14, 2019 at 1:27 pm
Hi Josh,
Yes, either deactivating InfusedWoo 3.11.8 or Event Espresso – WP Users will result in only one IFS contact being created.
I have also contacted InfusedWoo and they say it is how a WP User is created by EE. Here is what the said about the issue…
”
– When wordpress plugins process user registration, many of these plugins register first the user with an email address and after that, they update the user manually (via user update) other information like first name, last name, etc. So it looks like this
User Submit Registration Forms –> Email is used to register in WordPress (triggers the registration hook in wordpress) –> Update other information like First Name and Last Name.
– With InfusedWoo, it can only sense that first part where email is registered, but the second part doesn’t have a hook (or it has a custom hook) and therefore InfusedWoo would be “blind” to the extra information updated by the plugin.
– This said, the field is not the issue, but the timing of the update which can be freely controlled by the registration plugin.
”
Thanks
|
|
Josh
|
November 14, 2019 at 1:39 pm
I wonder if the InfusedWoo plugin can skip sending an API request when the new user registration happens via the WP Users Integration add-on. Is there a place where I can download a copy of InfusedWoo so I can check its code?
|
|
Dairywomensnetwork
|
November 14, 2019 at 8:00 pm
What is the best way to provide you these files?
|
|
Tony
|
November 15, 2019 at 2:22 am
You can send a copy to support[at]eventespresso.com
I’d recommend uploading the files somewhere and sending a link rather than the files themselves as they will often be rejected so something like WeTransfer is ideal.
|
|
Josh
|
November 18, 2019 at 10:16 am
Hi,
You can actually use a hook to prevent InfusedWoo from creating an IS contact when the request happens on EE’s single page checkout. Here’s a code snippet that makes this happen:
add_action(
'AHEE__EE_Single_Page_Checkout__process_attendee_information__end',
'my_custom_user_register_action'
);
function my_custom_user_register_action() {
remove_action('user_register', 'ia_new_user_reg',10,1);
}
You can add the above to a functions plugin.
|
|
Dairywomensnetwork
|
December 1, 2019 at 2:48 pm
Thanks Josh, this code snippet worked like a charm.
|
