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 All-In-One Event Calendar recurring conflict | Event Espresso - Staging Server
When using timely’s All-in-One Events Calendar, recurring events all display the wrong time unless I deactivate your plugin. I noticed in other threads about this that you’re fixing the problem in version 4. What is the release date for that? Is there a fix I can use in the meantime?
I installed the all-in-one event calendar on my test site, and couldn’t reproduce the failure. Can you give some more details? What version of each plugin are you using, etc.
EE version is 3.1.34.1.P
AI1EC version is 1.10-standard
I’ve deactivated all plugins, and the AI1EC calendar works just fine. In fact it works fine with all of the plugins except EE. Once I activate EE, all the times on the recurring instances are displayed wrong on the front end. The 1st instance is correct, but after that, it’s off by the difference of GMT to here (TZ America/Chicago).
For some reason, that section of code wasn’t on 237-239 in my file, but I found it nonetheless. Worked perfectly. Thank you!
Viewing 5 reply threads
The support post ‘All-In-One Event Calendar recurring conflict’ 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.