[TYPO3-project-formidable] howto question

[Luc Muller]

You're right françois. in fact I didn't get the right purpose of those 
formular. the first one shouldn't add data in database, but only the second 
one, with a "user validation of data".

I think you should be able to do this with some standrads features of 
formidable :)

Luc :)
"François SCHOSSIG" <fs.nospam1 at a-e-r.org> a écrit dans le message de news: 
mailman.1612.1170928658.21067.typo3-project-formidable at lists.netfielders.de...
One pi is enough... And everything is there standard !

You can do it in several ways :

- 1st way :
   Step #1 is a standard form
   Step #2 is the same form, but readonly and playing with the
buttons...
   Step #3 is a standard lister form
More or less the steps directed by the php code of your extension.

- 2nd way : the validation button can be in several modes
   - one is a draft mode (stores the form, but do not activate the
<validators>)
   - the second is the validation mode (stores the form only if the
<validators> are ok)
And you use a specific field like a status, containing draft/
published, that you store depending of the button that has been
clicked on.
This possibility enables you to permit your visitors to save their
data during their work and to submit them once they have finished.

- 3rd way : again with the modes of the validation button...
If you absolutely do not want your visitors to save data without
validation, you can add a button that does only check the
<validators>, but without saving the form. And you give you visitor a
real feadback through the error messages shown.

   <renderlet:SUBMIT name="bouton_draft">
     <draft \>
     <label>LLL:EXT:aer_boitoutils/
aer_locallang.xml:form.bouton_draft</label>
   </renderlet:SUBMIT>

   <renderlet:SUBMIT name="bouton_test">
     <test />
     <label>LLL:EXT:aer_boitoutils/
aer_locallang.xml:form.bouton_test</label>
   </renderlet:SUBMIT>

   <renderlet:SUBMIT name="bouton_publish">
     <submit \>
     <label>LLL:EXT:aer_boitoutils/
aer_locallang.xml:form.bouton_publish</label>
   </renderlet:SUBMIT>

- more ?
--
F. SCHOSSIG, ICT Manager
Assemblée des Régions d'Europe
http://www.a-e-r.org


Le 8 févr. 07 à 08:53, Luc Muller a écrit :

> Hi tim... I think everything your're saying there is quite possible  with
> standard components.
> In fact it will mainly depands on which type of validation you need.
> Sometimes for doing some specific stuff you got to use some userobj to
> perform a specific action. but for this we have to know a bit more  about
> your form and renederlets.
>
> Well, quickly what I saw with your needs. I think that you'll need one
> extension with 2 pi
> the first pi will perform #1 and #2 and you'll need to redirect  (possible
> with formidable) to a second page where you'll have your second pi  which
> will list some data from another table...
>
> I I get right your problem I think you'll can achieve that like this!
>
> Try it, and give us your feedback.
>
> Best Regards
>
> Luc Muller
> "Tim Kleigrewe" <x27 at e27.com> a Ècrit dans le message de news:
> mailman.1.1170871623.15227.typo3-project- 
> formidable at lists.netfielders.de...
>> hi,
>>
>> i've just started using formidable in my own extension and had a  look at
>> the demo extensions. how to create a simple edit/create form is quite
>> easy to understand. but i would like to have a slightly different
>> behavior in data creation.
>>
>> i need:
>>
>> #1 create form, with validation as shown in the demos
>>
>> #2 review form data template, just another view of submited data
>> before storing it finally in DB if all data is valid
>>
>> #3 store it and show a resultlist of records allready stored  instead of
>> a form.
>>
>> is this possible with std components and do you have a short  brifing or
>> example somewhere for that?
>>
>> thank you very much!
>>
>> tim
>
>
> _______________________________________________
> TYPO3-project-formidable mailing list
> TYPO3-project-formidable at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project- 
> formidable