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
Customising Payment Gateway: hook for addField() | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Customising Payment Gateway: hook for addField()

Customising Payment Gateway: hook for addField()

Posted: February 5, 2013 at 10:36 am

Viewing 2 reply threads


Leland Zaremba

February 5, 2013 at 10:36 am

There was another post about how to add fields to payment gateways that was closed. Is there any detailed docs for this? Or could any EE dev drop in a short tutorial for adding a text field to the “check” gateway for example to show up in the admin and frontend during checkout?


Josh

February 6, 2013 at 12:13 pm

Hi Leland,

The check gateway doesn’t display any additional fields, when someone chooses that option, there isn’t any additional info that gets filled out.

What you can do is add your question to the standard registration form, which will also show up in the admin automatically.


Leland Zaremba

February 6, 2013 at 2:07 pm

Thanks Josh. I have escalated this to priority ticket for assistance and will post my findings here.
Viewing 2 reply threads

The support post ‘Customising Payment Gateway: hook for addField()’ 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.

The original Forum description...

Status: closed

Updated by Leland Zaremba 11 years, 11 months ago ago

Topic Tags

Notifications

This topic is: not a support question
Event Espresso - Staging Server