Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Merchant warrior and Multiple events | Event Espresso - Staging Server
When using multiple event registration addon and the Merchant Warrier payment gateway there is what I think is a bug.
EE does not seem to update the transactionProduct string that is required for Merchant Warrior to process the payment. Is there a work around for this?
I can verify that this is a bug in the Multi Event Registration component that slipped through in a recent update. I’m creating a high priority ticket with the goal of getting a fix out in the next release.
Hi Josh – Thanks for your help, great! When do you think the update will be released?
I am also noticing that with Merchant Warrior the contact phone and country are not automatically carrying across from EE to MWarrior like the rest of the input data. Can this be fixed?
I do not have a time estimate. When I have some code ready to test, I will post an update here.
With the phone info not carrying over automatically, you can add this line to event-espresso/gateways/mwarrior/mwarriorvars.php ~ line 38 to add the phone:
$mwarrior->addField('customerPhone', $phone);
I tried to send the country field to Merchant Warrior a few different ways, and regardless of what I sent it displayed a country selector and it was ignoring the country value I sent it. So I don’t think that is something we can change.
Viewing 4 reply threads
The support post ‘Merchant warrior and Multiple events’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.