Actually, this is more likely to belong in Products.PloneFormGen. But in order for the solution to be usable with collective.megaphone, we can't just set a Z MySQL Method as afterValidationOverride, because collective.megaphone uses that to call its @@recipient_multiplexer.
My question is: Would it be valuable for PFG to have easier MySQL storage? Kees On 08/31/2010 11:33 AM, Kees Hink wrote: > A question for collective.megaphone developers: > > A client of ours wants to store collective.megaphone data in a MySQL database. > One could do this by following the steps at > http://plone.org/products/ploneformgen/documentation/tutorial/sql-crud/tutorial-all-pages. > That's a lot of manual work, and it requires some ZMI/MySQL knowledge [1]. It > would be nice to enable editors to create an Action Letter with a MySQL > extension using the wizard. > > I'd like to create either some kind of extension to collective.megaphone > itself > or a separate add-on product, which will do the following: > * on installation/activation, a create "Z MySQl database connection" is > created > - host, username, database are supplied by admin user at this moment > * When an Action Letter is created, the user can checks the box that says > "Save > also to MySQL database". If checked, this happens: > - a table is created (name derived from the Action Letter's id) > + add columns for all form fields are added > + maybe later allow users to select which fields are added > + maybe later allow updates when fields have changed > - a "Z MySQL Method" for storing is added > + maybe later add other "Z MySQL Methods" > - this method will be called after saving the form > + for example, an after-validation script calling this method > * each time an Action letter is deleted, its table is deleted > > What i'd like to know: > * Are there currently solutions available that i may have missed? > * Is it feasible to do this in collective.megaphone? If I created a branch, > would someone be willing to merge it if the quality is good? > * Or is this out of scope, and/or are there reasons why a separate package is > better suited for this than collective.megaphone? > > Kees > > [1] Also, I'm currently pondering about a way to use _two_ after-validation > scripts: collective.megaphone has one already filled in > (here/@@recipient_multiplexer), which i currently replace with my Z MySQL > Method. _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
