check out this thread - it may give you some ideas
    http://www.mail-archive.com/[email protected]/msg08323.html



2009/2/22 gdhurst <[email protected]>

>
> This is going to sound dumb, but how do you implement a simple
> customer facing form in a farcry cms website?  All of the tutorials
> are so focused on the admin interface, I don't know how to approach
> something this simple.
>
> Let's say I am creating a website for the Rotary Club.  I have a tab
> that says 'Membership Application'. If you click on the tab you get a
> page with a blank HTML form to enter in all the pertinent details such
> as name, address, etc.  You submit the form and the info gets stuffed
> into the database for later approval or review of some kind by an
> administrator.  Simple enough in the normal world of HTML or CFML, but
> how do you do this in a farcry cms website?
>
> Inside the admin interface, I can create a member content type and
> admin interface to the member type.  This would allow me working in
> the webtop to create, edit, and delete member objects.  I could then
> develop a list or display webskin to show the world who our members
> are.  All this is great, but this whole paradigm of information
> creation and management is centered on the administrative editor
> working within the webtop where everything is kind of automatic,
> prebuilt and preconfigured.  Very nice for the admin.
>
> If I want to build a form that faces the customers/visitors of my
> Rotary website and allows them to create a member object themselves,
> how do I do this?  Where is this form stored?  How is it called?  How
> is it processed? I could obviously do an end-around on the whole CMS
> system and do a normal CFML approach that talks straight to the
> database, but that doesn't seem appropriate at all.
>
> Overall, it seems like the developer docs mention the broader concept
> of a web application framework, but spend all their time talking about
> the CMS plugin.  I don't know if I'm supposed to buld my form inside
> the CMS and expose it somehow with a webskin and specific permissions,
> or build it outside of the CMS and simply utilize some of the features
> of the CMS database, or avoid the CMS altogether and simply implement
> the form as a separate 'neighbor' to the CMS system of views and
> content.
>
> gdhurst
>
> >
>


-- 
AJ Mercer
Web Log: http://webonix.net


Once you come to the realisation that everyone is crazy,
You will never be surprised or disappointed ever again.
AJM 2008

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"farcry-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/farcry-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to