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
WooCommerce and USA Epay conflict | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium WooCommerce and USA Epay conflict

WooCommerce and USA Epay conflict

Posted: January 17, 2014 at 7:37 pm

Viewing 3 reply threads


tmcmahan

January 17, 2014 at 7:37 pm

I know I can’t expect support for two different plugins but does anyone have any experience resolving a conflict with WooCommerce and USA epay. I’m running a store and an event registration on my site. I get the following error

Fatal error: Cannot redeclare umVerifyCreditCardNumber() (previously declared in //wp-content/plugins/woocommerce-gateway-usa-epay/usaepay.php:1229) in //wp-content/plugins/event-espresso/gateways/usaepay_onsite/EE_Usaepay.class.php on line 1302


Josh

January 17, 2014 at 8:48 pm

Hi there,

What you can do is open up /event-espresso/gateways/usaepay_onsite/EE_Usaepay.class.php
and add one line of code before line 1229:

if ( ! function_exists('umVerifyCreditCardNumber' ) ) {

Then be sure to add a closing bracket just after the closing bracket that closes the function that’s around line 1302.

}

This will check and make sure the function isn’t defined elsewhere before it tries to define it.


tmcmahan

January 17, 2014 at 9:12 pm

Thanks!

I also had to do the same for the _uePhpLibPrivateXMLEntities function on line ~1307


Dean

  • Support Staff

January 20, 2014 at 1:32 am

Thanks for the feedback! We will raise a ticket to look into this for future updates.

Viewing 3 reply threads

The support post ‘WooCommerce and USA Epay conflict’ 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.

Event Espresso - Staging Server