Support

June 21, 2017 at 8:38 am

Hi there,

You do not need to edit Event Espresso core files to change the URL.

You can use the example here:

https://gist.github.com/Pebblo/9d0921b2373f47de311fad88d112a215

or

https://gist.github.com/joshfeck/5646e8900ac6de96854aa21c720a3a21

You just need to set that function to return the correct URL you want to use and EE will use it, please remove your modifications to EE and use one of the above functions.

You can place the function within a Custom Functions Plugin on your site and can confirm it is working from the payment logs within:

Event Espresso -> Payment methods -> logs.

When you attempt a payment you will create log entries there (likely at least 3 for AIM) if you view those logs you can see which URL is being used there within the ‘Server URL’ field.

—

Whilst the AIM payment method supports changing the URL we support the Auth.net payment method when connecting to auth.net, we do not have any information on NMI or any other emulator currently.

You’ll need to contact NMI and confirm if the URL is correct and see if they can provide any additional information on why your payments are returning errors.

June 21, 2017 at 8:59 am

Then you are doing something different to me 🙂 are you adding the function to a custom functions plugin or your theme’s functions.php file?

Here is an example payment I’ve just made with and without a custom plugin with one of the above functions – http://take.ms/cdcW1

The server URL is updating and I’m not editing any of EE’s core files.

Have you confirmed if the ‘Server URL’ field has updated in the logs for a new payment after adding one of the above functions?

June 21, 2017 at 9:16 am

Did you add the code to a functions.php file in the theme or into a custom functions plugin? The latter will work but the former will not. When you modify core files you’ll lose your modifications every time you update the software.

June 21, 2017 at 9:52 am

Adding it to functions.php will not work?

No, functions.php runs too late.

Any idea why I am still receiveing a Code 92 error than?

You’ll need to contact NMI and have them investigate. Here is what Auth.net show for error 92:

https://support.authorize.net/authkb/index?page=content&id=A627&actp=RSS

However your not posting to auth.net you posting to NMI (who basically copy auth.nets setup) so you’ll need to check with them what is cause the error.

June 21, 2017 at 1:35 pm

Instead of putting your code in functions.php (which is probably running too late, can running your code too late can cause the error you’re seeing) you can put the code into a plugin for custom code. We have a guide that shows how to put the code into a plugin:

https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/