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
New event defaults to closed and changes end registration time | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › New event defaults to closed and changes end registration time

New event defaults to closed and changes end registration time

Posted: March 24, 2014 at 12:35 am

Viewing 6 reply threads


Clear Group

March 24, 2014 at 12:35 am

Hi,

EE: 3.1.36.4.P
WP: 3.7.1

When I create a new event and save it, the end registration time automatically changes to the actual time (eg 5:33pm).

I’m entering an end registration date of 2030-12-31 and an end registration time of 11:59 pm.

Also, the new event defaults to status of CLOSED. Seems like the same issue as this: https://staging.eventespresso.com/topic/new-created-event-shows-closed/

Thanks,
Tania


Dean

  • Support Staff

    •

March 24, 2014 at 1:52 am

Hi Tania,

The end time should not change, if you have set it.

Can you advise your time zone and time format from the WordPress Settings > General page.

Can you also provide a screenshot of the date/times form the event that has the issue?


Clear Group

March 24, 2014 at 6:12 pm

Hi Dean,

These defaults have only started occurring since we upgraded to 3.1.36.4 (about 3 weeks ago).

Time zone is Melbourne, Australia. UTC time is 2014-03-24 23:38:45 Local time is 2014-03-25 10:38:45

Time format is 10:41 am

I’m also concerned about the new event defaulting to CLOSED.


Clear Group

March 24, 2014 at 6:13 pm

Screen shot of default time is here: http://i58.tinypic.com/2ii9zlx.png


Josh

March 24, 2014 at 9:04 pm

Hi Tania,

While the other you linked to did not include the part of the discussion that led to finding out what ended up causing the same issue you are reporting, I looked into this and found out that it was a conflict with another event plugin. Once the other event plugin was deactivated, the Event Espresso date functions worked as expected. Can you try deactivating all other plugins except for the Event Espresso add-ons and see if that makes a difference when you create a new event?


Clear Group

April 8, 2014 at 7:29 am

Hi Josh,

I deactivated all the non-EE plugins and the same errors occurred. I reactivated them and the same errors occurred again.

Hope you have another suggestion.

Thanks,
Tania


Josh

April 8, 2014 at 8:48 am

Hi Tania,

Of course. Can you try installing the theme test drive plugin and test drive creating an event with the twentyfourteen active for the admin? Another alternative to this troubleshooting approach would be to temporarily disable JavaScript in the browser.
Viewing 6 reply threads

The support post ‘New event defaults to closed and changes end registration time’ 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 10 years, 10 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server