Feature request - Cache/Import external calendar data
Reported by dleffler | February 21st, 2013 @ 01:39 AM | in 2.3.9 (closed)
Though we currently allow connection to an external ical or xml calendar source, it can be slow since the data must be processed every time the page is updated. It might be worthwhile to have a one time import to add the events to the existing calendar.
Could be:
- either by url or file?
- one time process to preclude having the external calendar source
Comments and changes to this ticket
-
dleffler March 17th, 2013 @ 11:22 AM
- Milestone set to “2.2.0beta2”
-
dleffler March 29th, 2013 @ 08:00 PM
- Milestone changed from “2.2.0beta2” to “2.2.0beta3”
-
dleffler April 20th, 2013 @ 10:17 AM
- Milestone changed from “2.2.0beta3” to “2.2.0release-candidate”
-
dleffler May 1st, 2013 @ 10:22 AM
- Milestone changed from “2.2.0release-candidate” to “2.2.1”
-
-
dleffler August 7th, 2013 @ 06:05 PM
- Title changed from “Feature request - Add import external calendar data” to “Feature request - Cache/Import external calendar data”
We also want to cache external xml/ical data in either a serialized object file, or the database (new table(s). The cache could/would be refreshed by cron job, or possibly by user access.
If stored as a database table, it would be easier to quickly parse vs loading the entire file (into memory) and then filtering the object array. It could mirror the event/eventdate tables but would require a 'url' or similar field to point to the calendar being cached
Then importing becomes much easier, as simply copying from one table to another.
-
dleffler August 16th, 2013 @ 06:22 PM
- Assigned user set to “dleffler”
- Milestone set to “2.2.3”
Likewise we'll need to add multi-day recurring processing.
-
dleffler August 30th, 2013 @ 03:46 PM
Note: this work is taking place outside the 'develop' branch but should be integrated before 2.2.3 is released.
-
dleffler August 31st, 2013 @ 06:16 PM
This will require some new settings on the 'pull' tabs and we may only cache future events (next 365 days or user configurable on google calendar).
-
dleffler September 11th, 2013 @ 02:28 PM
Current (working) iteration is to cache future events (~1 year), but not erase past events from the cache. Also NOT using any module setting as the cache either exists or doesn't exist as a result of the 'build_cache()' call.
-
dleffler October 31st, 2013 @ 04:36 PM
- Milestone changed from “2.2.3” to “2.2.4”
-
dleffler November 19th, 2013 @ 01:57 PM
- Tag changed from “calendar” to “calendar, events”
-
-
dleffler March 27th, 2014 @ 10:23 AM
- Milestone changed from “2.3.0” to “2.3.1”
-
-
-
-
dleffler March 27th, 2015 @ 07:29 PM
- Milestone changed from “2.3.4” to “2.4.0”
-
-
-
-
dleffler June 4th, 2016 @ 08:27 PM
- State changed from “new” to “resolved”
- Milestone set to “2.3.9”
implemented in pre-2.3.9 code already release in 238patch
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bug Tracker for Exponent CMS
dleffler
expNinja