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
Issue with Custom Gateway Integration | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Issue with Custom Gateway Integration

Issue with Custom Gateway Integration

Posted: February 13, 2014 at 4:25 pm

Viewing 4 reply threads


Jason Piasecki

February 13, 2014 at 4:25 pm

I was having an issue with my custom gateway not being found. This was due to line 211 in EEM_Gateways.model.php. This is for an installation of EE4.

This is what it was:

<code>		foreach ($upload_gateways_glob as $upload_gateway) {
			$sub = basename( $gateway );
			$upload_gateways[$sub] = TRUE;
		}</code>

It should be this:

<code>		foreach ($upload_gateways_glob as $upload_gateway) {
			$sub = basename( $upload_gateway );
			$upload_gateways[$sub] = TRUE;
		}</code>


Anonymous

February 13, 2014 at 4:44 pm

Hi Jason,

Thank you for reporting this, I have issued a ticket for the developers to review.


Lorenzo Orlando Caum

  • Support Staff

February 14, 2014 at 11:35 am

Hi Jason!

We would like to verify this fix for you. Could you please send a copy of your payment gateway to my email so I can test this?

lorenzo@eventespresso.com

Many thanks


Lorenzo


Lorenzo Orlando Caum

  • Support Staff

February 14, 2014 at 11:54 am

Received, thank you.


Garth

  • Support Staff

February 14, 2014 at 3:25 pm

Hi Jason,

We’ve released an update today (4.1.3) which will accommodate your gateway. Let us know if you find any other issues.

Viewing 4 reply threads

The support post ‘Issue with Custom Gateway Integration’ 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