Hi all,
I'm focusing on event managment because I'm setting up a site that will advertise events.
In the previous versions of event.module the structure of the module was fixed, and so it was simple to create a newsletter that will print out the title, teaser, date and location informations.
With the new version, event is more and more flexible, so any flexinode-type node can become an event.
This is REALLY powerful, so I can create several flexinode-based node types (with different informations, based on the type of event you need).
Now, the problem.
Suppose I have different event types (everyone with its location and teaser field); how can I write a GENERALIZED newsletter module that will recognize that in 'flexinode-1' based events (suppose a stage), location field is named 'flexinode_15' and teaser field is named 'flexinode_16' while in 'flexinode-2' based events (let's say a concert) location field is named 'flexinode_24' and teaser field is named 'flexinode_23' ??
I wouldn't like to write everytime a specific module that everytime must be tailored in order to print out the right fields, and I'm thinking of a universal solution.
The only simple way I found would be to put location informations and the teaser into event table, so that data structure would become fixed, and every other module could benefit of it.
What is your opinion on this matter ?? Does it sound interesting ?? Is anyother working or thinking of something similar ???