Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I'd like the module to allow more flexibility, both in terms of the data you can input, and the way in which it is presented. I'm guessing that some of this would need to be done in the module code, and some would be themeable hooks.
You can see an example of how I'd like my events list to look in the attached screenshot. The changes, in order of importance, are:
- Have an image for each event that can be shown in the theme
- Make the location a textarea with HTML tags allowed, so I can put in links to different parts of text for more venue information
- Allow the events list to be split into upcoming and past events (either in the theme function, or as a hardcoded option)
- Allow other nodes to be attached, as reviews / photos / etc. from past events
The last feature may be tied in somehow with Ber Kessel's clipper module. At the moment on our web site we use clipper to tie together source and remix nodes (e.g. this source node and this remix node). Or it could be a taxonomy thing...
| Comment | File | Size | Author |
|---|---|---|---|
| list.png | 123.52 KB | tomchance@www.remixreading.org |
Comments
Comment #1
progressnerd commentedEvent should depend on location. I understand why location is it's own independent module. But event should depend on location and presume it exists. That way, lists and calendars of events, like most calendar programs, can show the location as well. While you can certain have data that has a location but no time, it is extremely rare -- just improbable -- to have data with a time but no location. Events should always have locations!
Comment #2
simon georges commentedThis version of Event is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.