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
EE4 Ticket end date won't "stick" | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › EE4 Ticket end date won't "stick"

EE4 Ticket end date won't "stick"

Posted: April 21, 2014 at 6:45 pm

Viewing 10 reply threads


Debby Kurti

April 21, 2014 at 6:45 pm

I’ve read through everything I could find here on the forums but not having much luck troubleshooting this issue.

I have a paid version of EE4 and for the most part, like how it is working. I set up 10 events. Each event had 4 ticket types (early bird, regular, on-site, lunch) with different opening and closing dates. The opening dates are working just fine. However, on two of the tickets (regular and onsite) I can’t get the end date to stick. All ticket were created identically except for the price and the dates. Regardless of how many times I change and save, on those two tickets, across all 10 events, the end date reverts back to match the start date. Seems odd, doesn’t it?

Here is a short video demonstrating what I am talking about. Any ideas?

http://www.screenr.com/X6xN

Here is the event in the video:

http://learningexploratorium.com/?espresso_events=conejo-valley-educators

Thank you,

DebbyK
http


Lorenzo Orlando Caum

  • Support Staff

    •

April 21, 2014 at 7:52 pm

Hi Debby,

Do you remember what version you were running prior to updating to the latest?

Also, if you create a new ticket for that event are the dates also changing on their own?

Are there any other plugins activated that use a datetime feature such as a calendar?

—
Lorenzo


Debby Kurti

April 21, 2014 at 8:06 pm

Hi Lorenzo,

Thanks for the quick response. I downloaded EE about 2 hours before the big server outage the other day (lucky, I know lol) and have it currently at 4.2.1. I did also purchase the calendar around midnight last night, but this was doing it before the calendar was installed. I haven’t messed with any of the calendar settings yet. I have this on a pretty minimal WP install (plugins: akismet, easy fancy box, exclude pages from navigation, page links to, photo gallery, and TinyMCE Advanced). The theme is Blocomo.

When I created the first event, I checked the “use this new ticket as a default ticket for any new events” box and then deleted/edited the ones I needed to on the next event. I thought it might be a problem with the default tickets, so I deleted them, and added a new ticket to the event… same issue happened. I just added a new ticket to the Conejo event linked above to test it, put in the start and end dates, saved, and it reverted the end to match the start.

Strange :(


Lorenzo Orlando Caum

  • Support Staff

    •

April 21, 2014 at 8:24 pm

Hello,

Thanks for that additional information. I tried to duplicate this on a test install but I have not been able to reproduce it yet.

Could you please create a temporary WordPress admin login so we can take a closer look at this issue?

Please share that temporary login through the secure link below:

https://staging.eventespresso.com/send-login-details/

I do want to mention that I’m out of time for today but a team member will be able to take a look at your site.

—
Lorenzo


Debby Kurti

April 21, 2014 at 8:49 pm

Done. Thank you.


Anonymous

April 22, 2014 at 3:38 am

Hi Debby,

I have taken a look at your site and can not reproduce the issue.

I tested on the event you mentioned within the form and had no issue when adding another ticket, I could select any date, update, then edit to any date and update once again.

I also tested the test event you have created showing the same results.

May I ask which browser are you currently using please?

I did not want to change you current ticket dates without checking if that was OK first. Is there a specific ticket I can test this on?


Abe Stem

April 22, 2014 at 9:35 am

I am now having the same issue on an event that I have posted. It seems that the ticket availability date keeps resetting to the same timestamp as the creation of the ticket.


Debby Kurti

April 22, 2014 at 9:36 am

Hi Tony,

Go ahead and try it on the Conejo Valley (Eductors) ticket. That’s the one in the video. I have used Safari and Chrome both to see if it was a browser issue, but it doesn’t seem to be. I don’t have a problem with a new ticket, but when I add one, set it, and then delete the problem ticket, the same thing happens again.

Thank you,
DebbyK


Michael Merrill

April 22, 2014 at 11:48 am

Hello! I am having this same issue. It’s resetting the time slots on every new event. Any help would be greatly appreciated.


Sidney Harrell

  • Support Staff

    •

April 22, 2014 at 12:01 pm

We are able to reproduce the problem now, and have raised a developer ticket to get a fix worked out and released in 4.2.3.
There is a work-around, but it involves looking at the ticket in the Data Base using phpmyadmin and manually editing the ticket end date. That may be the best way to do it until we can get 4.2.3 released.
I made a screencast of how to do it you can view here: http://eetesting.info/pics/editTicketDatetimes.ogv


Michael Merrill

April 22, 2014 at 12:03 pm

Thank you.
Viewing 10 reply threads

The support post ‘EE4 Ticket end date won't "stick"’ 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 Michael Merrill 10 years, 9 months ago ago

Topic Tags

Tagged: , , ,

Notifications

This topic is:
pending
Event Espresso - Staging Server