Events calendar pro slowing down site drastically

[Robert]

I had 3.9 with pro installed locally and working fine. uploaded to server and calendar functions won’t work when Pro is activated.

I tried this with both versions updated to 3.9.1, then reverted to 3.9 and neither is working.

I’m running a child theme on Twenty Twelve, have disabled all other plugins and put it on Twenty Twelve (no child) with same exact symptoms. Now I have 3.9.1 for the core and 3.9 for pro and the calendar view page opens in about 7 seconds, in twenty fourteen, twenty twelve with no other plugins, totally stock.

I really need help with this,
thanks

[Jo]

Hello Robert,

I just want to add myself to this thread. I have the exact same problem. My site was working find and the suddenly the speed went down dramatically. I’m using the Espresso theme from themeforrest.

best regards,

Jo De Maeyer

[Barry]

Hi Robert:

I’m really sorry to hear you are experiencing difficulties. I’m not quite clear though if the problem is just with PRO 3.9.1 or also impacts 3.9 – can you confirm?

Looking at your site I estimate you currently have around 1,400 events (many of which are long running recurring events). I don’t know how many regular posts and pages you have, but the total volume could be a factor here.

Can you confirm what sort of hosting package you are currently using?

(Jo: please do feel free to monitor this thread, but if you need any assistance that relates specifically to your own site please do create a fresh thread — thanks!)

[Robert]

This issue is happening with both versions, 3.9 and 3.9.1, I have tried both.

More info about my situation:

when I made this site, I used a copy of another site. In other words, the calendar was populated with events, lots of them. In the new copy, I just deleted the events and thought that would work.

In trying to find out what is going on to slow the site down I have uninstalled and reinstalled the core and pro plugins more than once. One thing I noticed is that events I added for this site remained in the database, because they appear when I reinstall.

I have set recurring events to go forward 12 months and to be deleted after 6.
Also found a super huge error file created because the bug logging was checked, so I deleted the error files (2) and unchecked the logging option.

This site is on Godaddy shared hosting, cheapest option. But it runs great when I disable the calendar. If I disable pro it runs ok, but the calendar is still slow to open.

Having Pro activated slows everything down including the WP admin.

Anything I can do?

[Robert]

I noticed that my recurring events are showing out to 2017, so am now activating Pro so I can edit them and pull them back to a max of 12 months.

Since it didn’t seem to make a difference which versions I ran, I’m keeping with 3.9.1

looking forward to hearing from you.

thanks

[Robert]

Just tried to edit an event to end recurrence in 12 instead of 24 months. Wishful thinking.
Can’t do it. It’s just frozen.

[Barry]

Hi Robert,

When you create, update or delete a recurring event a potentially large number of posts need to be created, amended or destroyed (there is a post for every single instance in each chain of recurring events). Unfortunately, that can result in timeouts – which may be what you are hitting up against when you describe things as frozen.

There are two angles to the problems you are describing. One is that you need a hosting package that is sufficiently powerful to tolerate the volume of data (and traffic) you are dealing with – and perhaps your existing package isn’t quite at the right level.

The other is that our current approach to updating and managing recurring events is in need of some adjustments to help avoid timeout issues and to provide a friendlier user interface that lets you know how things are progressing. This is, in fact, in the works as we speak and all things being equal we’ll seem some changes roll out in our very next release.

In the meantime you can try this experimental plugin which bolts on some of the planned changes without requiring you to change any core plugin code; please do bear in mind that at this point it is not itself something we can offer further support for and it’s very much a case of “use at your own risk”, but it may provide some temporary relief until our next release arrives.

[Robert]

Ok,

I’m going to work on my local copy since the live one is too slow to do anything with. Then I’ll upload a new version.

I’m going to:
reduce the length of time that recurring events endure forward and backward.
test the site on a better hosting platform.
test with the plugin you sent.

Question:
Because I am working with multiple sites that use your calendar (I recommend it) and I often use a copy of my last site as a starting point for my next one, (I’m part of an org that has small centers all over the world, each site is owned individually, but I support them), is there stuff on the server that I need to be cleaning out when I start a new site from a copy of one that already had events calendar installed?

Is this even an issue? or is it just something I don’t need to worry about?

This particular site happens to have more recurring calendar entries than most, but I do have another site running that is adding a lot of entries right now too, so I want to fully understand this so I (we) can avoid more trouble.

Thank you for your help I really appreciate it.

[Barry]

That’s a good question.

So you’re also duplicating the database, in addition to the plugin/theme files, when you’re creating these new sites?

Other than clearing out the actual event, venue and organizer data, so long as you are happy for the same settings to carry across to the new site I don’t really think there is anything in the database you’d need to clean out (at least not in the current release).

However, you will also inherit other bits of the original site’s ‘state’ and, in future releases, that means you may also end up with a queue of events that are still to be created, etc, which could create odd side effects on the new site (though I’m speculating a little here), so longer term it may not be the ideal approach.

I hope that helps 🙂

[karen]

I am also having issues with recurring events. they never did save properly. I am on a VPS, with 1gig RAM, 4 gig burstable. For some reason my past events were not deleting as they should and my SQL server came to a halt at about 5000 events. I am now down to 1600 by manually deleting all of the past events and many that had never really saved right in the first place for some reason we have never quite nailed down. Things are much better. currenty I am only saving 4 months in advance and 2 months in the past, but I am not convinced that they are deleting the past events. Is this a cron or something? Anyway, I don’t mean to hijack this ticket, just an FYI and to follow this thread. thanks

[Barry]

No problem, you’re more than welcome to follow the thread (though if you need help specific to your site, please do post a fresh topic) 🙂

[Robert]

I ended up moving the site away from the cheap godaddy shared account it was on. Now that it’s on something better it runs very very well. The calendar functions perfectly in a better hosting environment.

Thanks for all your help!

[Barry]

Happy to hear it – and thanks for sticking with us 🙂

I’ll go ahead and close this topic out, but please don’t hesitate to post new questions if anything else crops up.

Thanks again!

[Author]

Posts