|
Tammy Perlman
|
October 7, 2014 at 6:48 am
Purchased EE 4.4.3p yesterday. Migrated old EE3 events to new install.
Unable to add additional tickets to an event. Tried on both a migrated event as well as a new event. Help?
Would like to change “Register Now” to different wording. Do you have documentation for that on EE4?
The payment method is AuthNet AIM that is edited for the NMI gateway. Their instructions are:
VERSION (RECENT AS OF SPRING ’14)
…/modules/gateways/AIM/EE_Aim.class.php
Class EE_Aim extends EE_Onsite_Gateway {
const LIVE_URL = ‘https://secure.nmi.com/gateway/transact.dll’; //Authnet URL
const SANDBOX_URL = ‘https://secure.nmi.com/gateway/transact.dll’;
Is it really that simple? I’m not thrilled with this but it’s what we have to deal with so I have to make it work. Is there a better way to handle this than to edit the EE files?
Thanks!
|
|
Tony
|
October 7, 2014 at 7:59 am
Hi Tammy,
Unable to add additional tickets to an event. Tried on both a migrated event as well as a new event. Help?
Can I ask who your host is please? If you open up Chrome Dev Tool (Settings -> Tools -> Dev Tools) and go to Console, do you see any errors when you are on the Event Editor?
Would like to change “Register Now” to different wording. Do you have documentation for that on EE4?
The easiest way to do this is to translate ‘Register Now’ to whichever phrase you prefer. Theres a few methods to do this, we have a guide here:
https://eventespresso.com/wiki/how-to-change-wording-with-poedit/
Personally I would use either the Quick Localization plugin or the custom function at the end.
Is it really that simple?
Looks like the NMI gateway uses exactly the same setup just through another URL, this isn’t uncommon. I’ll do a little digging as there should be a way to save the custom versions of the gateways and override the defaults with these.
|
|
Josh
|
October 7, 2014 at 8:12 am
Hi Tammy,
If you are hosted on WPEngine, please open up a support ticket with WPEngine about the ticket editor issue. It turns out that WPEngine removes the Heartbeat API script from most pages (they say it’s for performance reasons). The unintended consequence is it breaks Event Espresso and other plugins that use the WP Heartbeat API.
I had the same issue on my personal site hosted on WPEngine where I use Event Espresso to organize group bike rides. I opened a ticket about this last week with them and they applied a fix on my site. It may help to expedite the support ticket if you mention you’re having the same issue as ticket #268405. That’s number of the support ticket that I filed.
Since it may take awhile before they get back with you, here’s an interim fix I can suggest. You add this code to your theme’s functions.php file (or you could add it to custom functions plugin as well)
|
|
Tammy Perlman
|
October 7, 2014 at 9:17 am
Thanks guys!
I’ve submitted a support ticket to WPEngine about the Heartbeat API.
I’ll give the “Register Now” documentation a look.
Looking forward to the NMI info.
|
|
Tammy Perlman
|
October 7, 2014 at 9:59 am
Tony, the Quick Localization plugin worked like a dream.
|
|
Lorenzo Orlando Caum
|
October 7, 2014 at 10:41 am
Hi,
The NMI service appears to be an emulator for Authorizenet. If that is the case, then you can swap in the updated URL for the service and save changes to the payment gateway file.
However, those changes will be lost on a software update. Also, we are updating an area of Event Espresso that handles payment processing so there is a chance that this change will need to be made again later this year.
—
Lorenzo
|
|
Tammy Perlman
|
October 7, 2014 at 11:05 am
Thanks Lorenzo. Appreciate everyone’s help.
|
|
Tony
|
October 8, 2014 at 10:29 am
Hi Tammy,
I was looking into allowing you to modify the AIM gateway and store the modified version within an update safe location but still have it load within Event Espresso.
As Lorenzo mentioned we will be updating how the payment methods work within EE4, this wouldn’t effect normal users but will effect custom gateways. As the changes needed here are minor, for the time being I would recommend altering the core AIM gateway (remember this change will need to be made after each EE update). Once the updated payment process is released we will also include documentation on how to save minor customisations like this within an ‘update safe’ location.
|
|
Tammy Perlman
|
October 8, 2014 at 11:14 am
Thanks Tony. I appreciate the extra effort.
|
|
Tammy Perlman
|
October 9, 2014 at 7:05 am
Josh – a quick update regarding WPEngine and the Heartbeat API. They can’t seem to make it happen. I gave them your support ticket #. Not sure what the problem is but I can’t wait for them anymore. I applied your “interim fix” and bingo!
Thanks!
|
|
Josh
|
October 9, 2014 at 10:48 am
Hi Tammy,
Thanks for the update. Some of their techs may be unfamiliar with the problem because WPEngine doesn’t have published documentation about how to fix this. I am supposed to get on a phone call with them to discuss this further and I am going to ask them to publish some documentation about this issue.
It may help to update the WPEngine support ticket and let them know who fixed the issue for me. It was Brandon Perry and Edwin. They wrote me back and said their fix tells their system to stop throttling the Heartbeat API.
|
