Hi, I'm setting up a community driven site, where many of the events are managed by the community members, including registration. So, just to simplify the idea, every time a user registers an account in the site, a poll is created and members vote to approve or decline the application. Currently application form is no more than a set of cck fields in a specific content type. This node is created in the "applications forum", so members can cast their votes.
Now, the question is, should this kind of functionality require a single module or not?
I've found several approaches here..
1st - I'm just querying to the "notification" modules developers about this kind of functionality, but "notification" modules should not care about approving or denying the application, so in the end I would have to include a glue module to finish approving the user.
2nd - Another approach will be to create a poll type for the advance poll module, and perform an action when the poll is closed to approve or deny it, but then I will have to develop the glue with the registration process.
3rd - making a glue for these two modules (notification and poll) and hope they don't change their mind to avoid so many module dependencies..
4th - create a module to just glue registration process (instead of notification) and programatically create a node, and again programatically perform the action of approving or denying when the poll gets closed..
Could you please share your ideas on this?
Thanks in advance!
ilo--