This seems to be a case where you would create a custom behavior that generates the form, then a controller it can post to.  Of course, you would have to change the routes file as well to handle the special controller.  Radiant is designed with the content as the core and it does that very well.  Good luck finding what you need!

Sean Cribbs
seancribbs.com

On 8/10/06, Adrian Madrid <[EMAIL PROTECTED] > wrote:
I've been following the development of a few Rails CMS/blog engines
and so far I really like Radiant but I can't quite figure out the best
strategy to implement dynamic pages like contact/registration forms.
Maybe I'm missing the obvious but how would you go about generating a
registration form (with validation errors, thank you message and all):

* Generate a clean registration object and save it into the session.
* Create tags that pull the registration info from the session.
* Process the post in a controller outside Radiant and return
processed data to the session.

Is that how you would do it? Or do I need another pure Rails site
(forms.domain.com) to process dynamic data?

Sorry but I'm confused. Most of the site I would use Radiant for are
mostly content but always have one or two forms that are always
around. I would really apreciate your ideas on getting the best of
both worlds.

Thanks in advance,


--
Adrian Esteban Madrid
_______________________________________________
Radiant mailing list
[email protected]
http://lists.radiantcms.org/mailman/listinfo/radiant

_______________________________________________
Radiant mailing list
[email protected]
http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to