I propose the inclusion of a "previous events" link which would allow users to see all previous events (and then to filter the results using categories and date windows).
Many thanks,
Jack
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | event.theme_.patch | 732 bytes | dan_aka_jack |
| #2 | event.module_49.patch | 2.24 KB | dan_aka_jack |
| #1 | event.module_48.patch | 2.26 KB | dan_aka_jack |
Comments
Comment #1
dan_aka_jack commentedHi,
I've attached a patch which seems to do what I need. It was pretty simple!
Thanks,
Jack
Comment #2
dan_aka_jack commentedSorry, please ignore the patch posted in the previous message. I have included an updated patch with this message (this patch is against HEAD).
Comment #3
dan_aka_jack commentedand here's a patch for the theme
Comment #4
killes@www.drop.org commentedCan I get some opinions on the usefulness of this?
Comment #5
umonkey commentedI don't know about the filtering part, but I think it's a good idea to show (1) all upcoming events and (2) some recently passed ones. Perhaps "all" and "ones" should be configurable. I'm running a calendar of club nights, and the list of all upcoming events is very useful, users can see the full picture. Recently passed events are also useful for users to easily find where to send feedback, in just two clicks. Even on a small community web site the traffic is high enough to make tracker ineffective for that. See how I did that; it's just two simple queries and a few configuration options, I think something like that is definitely worth implementing. I could submit a patch with my implementation.
Comment #6
dan_aka_jack commentedHi there,
I should explain why a "previous events" link is useful for the website that I am building.
The website that I am building is a website for an academic organisation. They hold seminars, workshops etc. They use the website to publish powerpoint slides and minutes of meetings so it's really important that users can easily access old events.
Thanks,
Jack
Comment #7
davemybes commentedI have several clients who have requested this feature, and I usually end up doing it all manually. Having it built in would make things so much easier. The reasons given for wanting it, is so that the visitors can see what they have missed, and also go back to read more about it, possibly even to leave feedback.
There is one error in the #2 patch, though. In the
case 'previous'section,$rowsshould be$tbody, otherwise you get no output. Other than that, the patch works perfectly for me.Oh, one other thing, usually the clients like to have the most recent past event first in the list. In other words, is there a way to reverse the order of the past events? Maybe using a setting to allow people to switch between the two would be good.
Comment #8
japerryEvent for Drupal 8 is unrelated to older versions. If an issue similar to this one exists, please open a new issue with the 8.x branch.