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
Confirm Navigation | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Confirm Navigation

Confirm Navigation

Posted: February 27, 2014 at 9:04 am

Viewing 5 reply threads


MAGentix

February 27, 2014 at 9:04 am

Hello,

We have a problem with the payment when we are using Chrome. At the end of the registration process, when we click “complete purchase” there is this popup message:

Confirm Navigation
Warning!!! Using the back button will overwrite your existing registration.
Are you sure you want to leave this page?
Options Stay on this page or Leave this page.

My web designer has tried EE suggestion of deactivating Authorize.net AIM Settings, but we still have the popup issue. The programmer doesn’t want to use that other forum user’s suggestion of taking out lines of code because that will cause issues with upgrading.

Any other suggestions/solutions for us?

Thanks


Anonymous

February 27, 2014 at 10:45 am

Hi MAGentix,

The submit button needs to have the class ‘allow-leave-page’ assigned to it.

The latest version of the gateways included within 3.1.36.4 all have this class so will not thrown that popup.

Firstly I would check if you have any custom gateways within /wp-content/uploads/espresso/gateways/?

If not then the best way would be to update to the latest version of Event Espresso (as you are currently on 3.1.36.2.B)

I would recommend performing a full site backup first (both files and database), we have a guide posted here:

http://staging.eventespresso.com/wiki/how-to-back-up-your-site/

Then updating Event Espresso which uses the updated gateways.


MAGentix

February 27, 2014 at 12:02 pm

Hi

Working on that. Keep you posted!
Thanks


Anonymous

March 3, 2014 at 6:14 am

Hi MAGentix,

Just checking in to see how you got on?

Everything working as expected?


MAGentix

March 4, 2014 at 10:05 am

Hi,

We updated the latest version of EE3.
First, the programmer tried with EE 4, but it is not compatible with Beanstream. So went back to EE 3.1.36.4. It’s working fine now.

We can close the case!
Thanks!
Have a good day!


Anonymous

March 4, 2014 at 12:32 pm

Great!

I’ll mark this thread resolved, please open another with any issues/questions you may have :)

Viewing 5 reply threads

The support post ‘Confirm Navigation’ 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.

Event Espresso - Staging Server