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 Issues after update to 3.1.33.3.P | Event Espresso - Staging Server
I’ve just updated Event Espresso and the event I had been working on in the previous version isn’t showing at all within Event Overview. I see the last event from June 2012, but nothing for the upcoming event. The Select Month/Year pulldown shows a blank entry and June 2012. I assume that the blank entry represents my missing work. Curiously, the event page and forms are all available from the front-end… just not in the WP Admin.
It sounds like the Event status filter needs to be changed to view All/Inactive events (the newer versions of Event Espresso will default to the status that lets you view only Active events)
I don’t think that’s it. This is what I see for Event Overview where there should be 2 events showing. One is a past event from 2012 and one is a future event:
Events : All Events (0) | This Month (0) | Today (0)
Dates have always been required in order for Event Espresso to function as expected, but the newer versions will autofill a date if it’s left blank to avoid issues like this one.
Viewing 5 reply threads
The support post ‘Issues after update to 3.1.33.3.P’ 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.