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 Why are there TWO event registration expiration dates? I can't change one... | Event Espresso - Staging Server
I have a comedy club (JokeJointComedyShowcase.com), with six weekly recurring events for each of our shows (Wed night, Thursday, 2 x Friday and 2 x Saturday).
I can edit the event registration start and end dates (and times), but I can’t change (or get to STAY changed) the event registration expiration date that I used to create the recurring events, unless (it appears) I am changing the registration expiration date in the entire SERIES of recurring events.
If I do that, then I have to re-edit every upcoming event that I’ve created details for (the next several weeks, for example). Also, I’m afraid that I’ll be changing the event ID numbers, which will affect all of the events that are currently actively selling.
As a result, if someone wants to buy an event this weekend, they HAVE to purchase it by clicking on the event in the calendar. I used to have links that would allow them to purchase the event directly from the weekend POST page, but when users clicked on those links, they got a message that this event was EXPIRED.
Is there a way to fix this without rebuilding the entire event database again?
The support post ‘Why are there TWO event registration expiration dates? I can't change one…’ 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.