Hi, how many events have you in your db?If you have lots, that’s a problem with wordpress and ther way it handles hierarchical posts. Please update to 1.10.9 standard which fixes that. Otherwise the solution could be to use a cache plugin.
Hi Nicola,
I’m running the latest version of pro, and the site seems to bog down when I have the sidebar widget fetch events in the past “500” days. Changing this to only the last 30 events drastically helps, but obviously it’s a compromise.
I have 169 events in the DB with W3 Total Cache already running, so not that many at the moment. For the time being this seems to be a good stop-gap measure.
So it’s the widget and i guess it’s the next 500 days 🙂
Anyway the W3TC thing is strange as it should definitely cache the page and the widget like every other thing it caches. As of now i see no different solution to keeping it at 30 days.
Hi Nicola,
In this case that seemed to have been the issue – of course at the time i wasn’t sure, so I whipped out load-testing tools, PHP profilers and mysql debuggers lol.
But really all i had to do was to normalize the scope of the query from 500 days (might as well be infinite) to something reasonable like 50-100 event objects.
Thanks for your quickly reply, and best of luck.
Most of hosting providers are calculating started php processes. F.e. only two started processes are processed at the real time. All other waits till first two ends. At this case plugin makes site offline, both frontend and backend.
I have 3 eveents per week (period – year). This crashed my site.
So, problem is not solved. Plugin is practically unusable, if I can enter only few events (f.e. month forwarg) only.
How can I solve my problem? This is great plugin, but massive php calls on loading widgets crashes most of sites
@juozaswp i see no solution to this, until 2.0 comes out. The only solution is limiting the events on the widget.
