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
Fatal Payment Error | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Fatal Payment Error

Fatal Payment Error

Posted: July 3, 2012 at 4:10 am

Viewing 3 reply threads


mpurse

July 3, 2012 at 4:10 am

I upgraded to the latest version of EE this morning (using 1-click updates from the dashboard).

Now anyone trying to register and pay for an event is getting the following error message:

Your registration is not complete until payment is received.

Amount due: £0.10

Warning: require_once(/home/thegoodl/public_html/wp-content/plugins/event-espresso-3.1.24.P/gateways/invoice/init.php) [function.require-once]: failed to open stream: No such file or directory in /home/thegoodl/public_html/wp-content/plugins/event-espresso.3.1.24.1.P/gateways/gateway_display.php on line 47

Fatal error: require_once() [function.require]: Failed opening required ‘/home/thegoodl/public_html/wp-content/plugins/event-espresso-3.1.24.P/gateways/invoice/init.php’ (include_path=’/home/thegoodl/public_html/wp-content/plugins/wordpress-backup-to-dropbox/PEAR_Includes:.:/usr/lib/php:/usr/local/lib/php’) in /home/thegoodl/public_html/wp-content/plugins/event-espresso.3.1.24.1.P/gateways/gateway_display.php on line 47


Josh

July 3, 2012 at 7:33 am

Hi mpurse, can you try deactivating and reactivating the invoice payment option?


mpurse

July 3, 2012 at 7:35 am

Hey Josh,

We fixed by de-and-re-activing the paypal option. Do we need to do that with each upgrade?

As long as I know, that’s ok.

ta.


Josh

July 3, 2012 at 7:45 am

Not usually. Some new invoice gateway code had committed into 3.1 that wasn’t ready yet, so they pulled it out. What happens is if Event Espresso can’t find an active gateway file, in this case an invoice file, it could throw an error. Since there was still an original set of invoice gateway files there, all that needed to be done is reset the gateway settings by deactivating and reactivating a gateway. Normally, we don’t remove gateway code in a new release, so this wouldn’t typically happen.
Viewing 3 reply threads

The support post ‘Fatal Payment Error’ 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 Josh 12 years, 6 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server