I would find it very helpful to have a way to import and/or subscribe to iCalendar event feeds from other systems/software.

For example, I have people using Apple's iCal or Microsoft's Entourage clients on Mac OS X, both of which can export iCalendar files. If they could upload those files as events, and retain as many characteristics of those events as possible (such as repeating schedules and more), it would make setting up a calendar much more quick and painless for them.

Several sites also post iCalendar data that can be subscribed to. If the Event module could subscribe to those calendars to add them in as events, tied into the taxonomy (sort-of like the way RSS feeds can be automatically assigned taxonomy keywords), that would be excellent.

Comments

jaharmi’s picture

jaharmi commented

Look at either of the following other products:

http://www.k5n.us/webcalendar.php

http://phpicalendar.net/

briandburnham’s picture

briandburnham commented

I think this is something worth integrating into the module itself. Sure there are other solutions. There are other CMS's out there too.

iCalendar is a standard I would like to see introduced to Drupal (via Event module). A more realistic beginning might be to supply an iCalendar feed for events in the system. I can see that import/export could be complicated.

If I knew more PHP, I'd do it myself. Anyway, my vote is for it.

killes@www.drop.org’s picture

killes@www.drop.org commented

Well, I'd like to see this feature included (although I'd prefer it as a module that hooks into event.module). But good wishes and no code don't make this likely. :-)

Anonymous’s picture

(not verified) commented

Okay, so are end users -- those who are not PHP coders -- not supposed to submit feature requests? If not, how are we supposed to enter our requests so that they get on the radar for someone who does have those capabilities, or so that they are seen as desirable by someone in the community? I was going on the assumption that we could submit feature requests so that they get on some list of priorities/requirements for the future.

I'm more than happy to adapt my feature request tactics to whatever method will make the most sense.

Thanks!

killes@www.drop.org’s picture

killes@www.drop.org commented

It is ok to add feature requests the way you have done. I just wanted to point out that new features are more likely to get added to the development (cvs) version than to a stable release.

If somebody picks up a particular feature request is entirely up to him/her and most likely triggered by personal need and/or a cheque. ;)

Anonymous’s picture

(not verified) commented

Okay, so it's better to pick "cvs" for the "version" field with respect to feature requests? I wasn't entirely sure how to fill out the form. Chalk it up to my newbie status.

Maybe we could get a link to quick instructions on the best way to fill out the "issues" comments, particularly for those of us who are using Drupal but not developing it? That would help me, I suppose. I've lurked on and off for a few years, but I guess I haven't entirely picked up the culture here yet ... :)

petearden’s picture

petearden commented

I'd also like to see this feature, if individual votes matter. If I weren't such a programming noob I'd take it on myself.

Still, it seems like it'd be pretty straightforward (famous last words?) so maybe it'd make a good learning project for my own site -- perhaps get it started for someone else to run with.

Sorry, I'm thinking out loud here. I'm also new to the OS community and trying (like Anonymous) to figure out the culture of request vs. participation. Thanks.

hba’s picture

hba commented

Minimal iCalendar support here: http://drupal.org/node/19381

crunchywelch’s picture

crunchywelch commented

this is a dupe of http://drupal.org/node/19381

I will add a comment on that post with a link to this one so it does not get lost