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
Pay by Check: where do I store customized files? | Event Espresso - Staging Server

Support

Home › Forums › Custom Files › Pay by Check: where do I store customized files?

Pay by Check: where do I store customized files?

Posted: August 13, 2012 at 8:06 pm

Viewing 2 reply threads


Jill

August 13, 2012 at 8:06 pm

I am customizing the pay by check gateway, specifically the file check_payment_vars.php. I have the custom-files plugin installed. Where should I move this file so that it over-rides the defaults, but stays protected from upgrades?

It would suck to re-edit this file after every EE upgrade :->


Josh

August 14, 2012 at 9:29 am

Hi Jill,

Copy over the entire /check directory from the /gateways directory to /wp-content/uploads/espresso/gateways. Then deactivate and reactivate the check payment option.


Jill

August 14, 2012 at 9:55 am

Thank you, Josh!
Viewing 2 reply threads

The support post ‘Pay by Check: where do I store customized files?’ 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.

Status: closed

Updated by Jill 12 years, 5 months ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: resolved
Event Espresso - Staging Server