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
tickets not saved | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › tickets not saved

tickets not saved

Posted: April 17, 2014 at 7:51 pm

Viewing 1 reply thread


Daj Oka

April 17, 2014 at 7:51 pm

Hi,

I am using the demo on demoee.

Upgraded to 4.2.reg.

Now when I add datetimes or tickets, when I click update to update post/event, it asks me leave page or stay. If I hit stay, it churns and the update button is greyed out (unclickable). If I hit leave, tickets are not saved.

In other words, I lose all the work whether I click stay or leave.

I was about to pull the trigger on purchasing the 4 beta… Is this a bug or is it just me?

Thanks,
Daj


Dean

  • Support Staff

    •

April 18, 2014 at 1:51 am

Hey Daj,

Thanks for your interest in Event Espresso.

It is not you.

The popup is an issue we are currently looking into fixing, but in our tests (including demoee.org), clicking either leave or stay should not affect the saving of the tickets or other information.
Viewing 1 reply thread

The support post ‘tickets not saved’ 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 Dean 10 years, 9 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server