Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By Hybernaut on
I've begun a project for syndicating events from Upcoming.org here.
I am interested in requirements from the Drupal user community:
- How would you like syndicated events to appear in your Drupal site?
- summary block
- events node
Currently the scope is for one way syndication, but when the Upcoming.org API is fleshed out, it will be possible
to push events from Drupal to Upcoming.
Comments welcome.
Comments
Look at the events module
Ideally, the events would be syndicated directly into the events table. That way, they could be treated like every other
They could be entered as "Anonymous" owners with the username and URL link being filled in from the Upcoming.org membership information.
event.module updates for 4.6.0 ?
I'm encountering this error with event.module under 4.6.0 candidate:
Fatal error: Call to undefined function: node_access_join_sql() in /home/bdv/build/drupal-cvs/modules/event/event.module on line 611
It looks like this is function in node.module is now private.
Does anyone know if updating event.module for 4.6.0 is under way?
I'm new here and still learning my way around, so any hints on where
the usual places to look are welcome.
Brian Del Vecchio | bdv at hybernaut dot com | http://hybernaut.com/
Found the latest version
I found the latest version in cvs which works under 4.6.0 candidate.
Brian Del Vecchio | bdv at hybernaut dot com | http://hybernaut.com/
yes! upcoming as events! but...
it would also be cool if they were controllable and distinguishable from other events, optionally of course.
Ultimately it would be great to build a community site that communicates with upcoming (and del.icio.us and flickr) and exchanges information, so that things that get posted on one site get synchronized with the other. It would be possible with the awTags module or perhaps folksonomy to mimic what the tagging sites do, it would just need to interface with the API.
Btw, there is news of an API for upcoming here: http://upcoming.org/news/archives/2005/03/28/huge_cha/index.php
bidirectional syndication
I'm excited to get syndication working in both directions between a Drupal site and Upcoming.org. I think some people will want to republish their event list on their blog--I use it to syndicate Boston area music events on mine. That's a pretty straightforward syndication.
However, organizations like The Boston Cure Project will want to define events locally and have them pushed into Upcoming.org automatically. This will save time, reduce errors, and help get the word out for organizations which sponsor events frequently.
chromatic, I hear what you're saying about using tagging as a common thread to link together events, bookmarks, and images. Let's do it!
Brian Del Vecchio | bdv at hybernaut dot com | http://hybernaut.com/
events needs some work for 4.6
theres a lot of changes to events in 4.6. I just spent the whole day messing with CSS and things. It adds a lot of new divs, and some NOBR tags - which mangle any xhtml/css tableless site designs. worse than the admin tables. and it's not cross browser compliant. plus as far as i know the timezone issues are still a headache, which would be crucial to this.
4.6 updated
There should be no timezone issues afaik, I have done extensive testing on this. There is a lot confusion about how timezone handling works, but it does work. You can take a look at http://civicspace.advomatic.com/node/15 which has a table of timezone input and output, as well as an explanation on how it works. If you find a bug I'd be very interested to hear about it since this was one area of the event module that was completely reworked.
Also, the themable functions have been cleaned up tonight, hopefully you have less problems. I'm wondering what cross browser issues you encountered?
In terms of this upcoming module, you could do some trickery where you enter the timestamp values and nid for events you syndicate into the event table, and use your own node type that is enabled for event display through nodeapi. Let me know if you want to talk about how maybe there can be tighter integration with the event module itself. Already there is a call to retrieve a rendered calendar with an array of nodes. The event 'api' is documented here: http://civicspace.advomatic.com/api/list