Hello folks! okay the scenario is a CForm form that goes over several pages. Wizard or Registration like. Here I was wondering what people are using out there for this common task and what are the options and best practise for that?
As far as i know there are 2 major ways to do this: 1 - on big form def. and a on big template... from fields are hidden and displayed via JavaScript and CSS (e.g. via <fi:styling type="tabs"/>). The problem here is that validation occurs "on submit" and that could case many errors and many "!" will get displayed which the user have to "find" first (some are hidden via JS)! right?!?!?!? Another problem could be the heavy use of client-side Javascript and CSS. 2 - split-up form definitions and templates and a submit button pointing to the next page via the contuniation. The big problem here is that when i go back and change values and submit again the fields on the 2nd (and so on) page are empty! right?!?!?!? Also having one form definition and calling the widgets from several templates doesnt work according to the developers, huh? MY QUESTION: any other options i didn't think of (with CForms and Cocoon 2.1.5.1)? What are people using out there and what is good and bad about it? Let's talk about it! Thanks in advance... phil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
