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 Database Throttling won't enable on calendar | Event Espresso - Staging Server
I’m building a website with Event Espresso. The calendar doesn’t display after i’ve added a certain number of events. If I “flip” database throttling on in the settings and save the setting doesn’t change. After the page reload it’s back to “off”.
Versions:
WP: 3.5.2
EE: Versie: 3.1.31.3.P
EE Recurring Events: Versie: 1.1.7
EE Calendar: Versie: 2.0.5.1
Thanks for letting us know about this, I will get a ticket raised. It is actually saving and enabling it, but if you save the settings again it will disable it as the selection is changing back to no.
Thnx! I have a site with weekly recurring events. If I turn on database throttling it seems it picks the first events but not the first week. So I get all events on monday and tuesday for the first couple of weeks. But not the wednesday.
Is performance such a problem for these kind of requests? It’s only like 300 events in the database in total…
Im not entirely sure how the throttling picks the events, i’ll take advice on that. It shouldnt cause an issue with 300 events, but of course it depends on your server and hosting as well. It’s more likely to struggle if you are on shared hosting with resource hungry sites.
Viewing 3 reply threads
The support post ‘Database Throttling won't enable on calendar’ 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.