
Online event registration has always proved tricky for website developers. Even with the rise of social media, capturing information from participants has always been subject to the nuanced details of organizing events in the real world. How many people are allowed to attend? Do people have to pay to get in? Where am I storing the information we collect so it is most useful to event organizers? These kinds of questions lead to very specific, focused solutions within open-source event management systems, and make it difficult to address the needs of general audiences.
Here at Trellon we have been dealing with event management solutions for a long time. Drupal is a great platform for promoting events, but there are no general, one-size-fits-all solutions for capturing registration information. EventFinder was an early stab at a complete solution, which had its own benefits and drawbacks, and eventually was scrapped in favor of Event- and Location-based solutions. e-Commerce added the ability to have paid event attendance, but even this created some challenges in terms of how the data was stored. Signup and Signup Pay brought developers closer to a general solution, but there are some common use cases that these tools have yet to address:
Trellon spent some time dealing with these challenges. While we are still far off from having a single solution that handles all things events, we added some significant capabilities to the Drupal platform through the development of several new modules:



By leveraging the existing technology and Drupal's extraordinarily extensible module system, we were able to keep the client's costs down, and build upon the existing Signup Pay module to exceed expectations with a suite that comprehensively covered all their requests.
2 Comments
It has pretty much all the
It has pretty much all the above pieces in one integrated system and a few other things also. It is definiely one of our most used components and we've focussed on improving it significantly over the past few releases
Hi lobo, we didn't use
Hi lobo, we didn't use CiviCRM on the particular project, and it would have been a bit of overhead just for the Events parts.
However we are using CiviCRM for some other sites which will also make it into later posts.
Post new comment