Experiencing memory problems or timeouts ? Check the following:
Are your default wordpress and php memory settings up to handling all that you have added to the site?
Over time, as you add change themes, and add plugins, your wordpress setup starts needing more and more memory. Sometimes the last plugin added is the one that ‘tips it over the threshhold’. It may not be the main memory hog (or it may see below.) Please check your wordpress and php memory limits. Here are some helpful posts:
How old is your ics file and how many ‘old’ events does it have ?
If it’s a google calendar, the ics feed does not at time of writing offer a way to request future events only. This means your ics file will grow. The plugin has to parse ALL the events in the file, hold them in memory to check for a possible modifying VEVENT with a later sequence number that modifies the date. More info on google calendar ics files – and how to bulk delete old events.
In the list type settings, and as shortcode parameters, you can set the maximum number of events and the maximum number of days or months that the plugin will attempt to list. It also uses these to limit the recurring events it has to generate.
It is important to set a balance between number of days/months and number of events, particularly if you have recurring events and in particular for those people using ics files. An event, especially a recurring can be made up of multiple VEVENT definitions, additional definitions for each excluded date, or modified instance. So for each recurring event, the plugin has to
generate the possible instances, hold them all in memory
check for any modifications, exclusions etc and apply those to the instances, before it can start limiting.
Modifications of instances can change an instance date and time – pushing it out of the desired time range or WORSE, pulling an instance that is currently out of range, INTO the time range.
Try to balance the two parameters: the time period and the number of events based on your knowledge of the types of events and their frequency.
For example: If you specify 10 events and 1000 days, the recurring events have to be generated out to 1000 days and all held in memory, until all events generated and modifications applied, and then the number can be cut back to 10.
As a guideline, If you want to show 5 events and usually they’d be in the next two months, then maybe 90-120 days would be suitable.
Note also that there is a difference between how hours, days, months thresholds are treated.
hours start from current hour
days start from current day
months start from current month
So if you say months=1 and the list is running on the last few days of the month, you will not see many of ‘future’ events ie: next months day. Bette to perhaps either use: days=30 or months=2,
If you are using a google calendar ics file as event input you should be aware of the following:
At times the ics feed is slow to update – check what the actual feed contains if you think events are missing . Open the ics file in notepad, and check if your events or your changes are there. Note that an instance may have multiple VEVENTS with incremental SEQUENCE numbers later in the file.
the ics file may get rather large over time. At time of writing there is no way to get the feed to only show future events, so it will have ALL your old data. This all has ti be parsed, turned into event data and held in memeory to see if there any any modifications, or exclusions. If you don’t need the old events, try deleting them. You may need a bulk delete tool. I have used this GcalToolkit, not ideal but it does work.
On the other hand, using an amr-events feed in a google calendar:
Again google can be slow to refresh reading the feed, sometimes it will do the first one fine, then you make a change and expect google to show in instantly. It will not. Not much we can do about that.
Google calendar has always been slightly more particular about ics feeds and frustrating in the lack of information it gives if it rejects a ics url. Thanks to Toby Hage, a couple of oddities to do with blank lines in descriptions and in repeating dates (RDATES) in the ics feed were been identified. These are now resolved in version 3.11. This version is up at http://test.icalevents.com/ and all appears to be stable so far. It is available for download at http://icalevents.com/downloads/amr-events/
If any of you have any feature requests, please contact me at email@example.com.
Version 3.6 of amr-events is available for download.
It should be used with the free listing part: amr-ical-events-list version 4.30. Several improvements have been made in the way that event meta data, taxonomies etc were being retrieved. This has reduced the database queries made when producing an event list from events in wordpress.
If you have a fairly recent version, and your access to the automated updates from icalevents is still current, then it should appear in the normal wordpress plugin updates.