I spoke with Gary today. (The author of the Tiki Event feature in CVS
We discussed how Tiki could eventually become an event management system
(eventually with registration, participants list, track or meeting
selection confirmation, contacting participants, payment gateway, etc).
I now understand better where Gary is going with this and I welcome
these new possibilities. There is also a goal of making event items
stand out in the calendar (make it clear you can register, as it now
As Gary wrote to me quite eloquently: Newsletter IS A subscription list.
Event HAS A subscription list.
Gary will look into a way of adding a newsletter link to calendar items
while forking as little code as possible. While it would be one extra
step for admins (and users?), we think there is a way to do it nicely
and to make it more maintainable, code-wise. Gary & I discussed and
agreed on the importance of determining and sticking to a database
structure for within the 1.9 series... Keep an eye on CVS mailing list
for updates on Gary's work :-)
On a related note, this week-end I spoke at a conference in Rosario,
Argentina with Martin Sarsale (aka Runa). One of my main selling points
for Tiki was to - Fight back against "Frankensite" - . Tight
integration of our features is what makes Tiki so powerful.
So possibly, in the future, the event registration feature could come to
life by a tighter integration of the calendar feature, the newsletter
and the trackers (for participant information tracking).
I look forward to 1.9 !!
Marc Laporte wrote:
> There are some features that need to be ready or removed before
> 1.9.0. For example, the Tiki event newsletter. AFAICT, this is a
> 'fork' of the newsletter feature with just a bit more integration with
> the calendar. I don't see a big future for this feature, especially
> with the nice work Sylvie has done to the newsletter feature since.
> Therefore, as of now, I think that feature should be removed of 1.9
> Anyway, it should have been a newsletter type such as article types.
> If so, it would have still leveraged Sylvie's recent work. My concern
> is that once 1.9.0 is released, we can't (strongly prefer not to)
> modify the database structure for the whole 1.9 series. Once our
> userbase has data in those tables, it'll be difficult to backtrack.
> There will be other features that will have to be completed or
> removed. If we choose to leave the db tables in even as the feature is
> incomplete, we need to have have a big warning notice in the admin
> panel. (feature incomplete in 1.9.0 but will be available in 1.9.1)