[TYPO3-project-formidable] Remebering previous entered form data.
Jerome Schneider
j.schneider at ameos.com
Wed Apr 18 13:11:49 CEST 2007
Hello tonni,
Your proposition for a datahandler:SESSION is a really good one
I'll give it a try when I have time ( about half a day I think ) in my
planning ( pretty full for the moment :D )
So it's officialy in the TODO's
BTW i'm going to create a thread TODO Requests in this list right now.
Can you post this first todo in it with little details about it ?
Regards,
Jerome Schneider
Tonni Aagesen a écrit :
> Jerome Schneider wrote:
>
>> 1 - Before sending the client to bank payment, record data in database
>> using datahandler:DB
>> 2 - Get the newly generated uid corresponding to this order using
>> $myForm->oDataHandler->_currentEntryId()
>> 3 - pass the uid of the current order to the "return url" you give to
>> the bank server ( if you can't do this, you can try to keep the uid in
>> session )
>> 4 - Send the user to the bank
>> 5 - When user returns from the bank server, get the order uid passed
>> before ( in the URL or in the session data )
>> 6 - In the PHP calling the init on your Formidable object, pass the
>> uid of the order to edit as the third argument, like this:
>>
>> $oForm = t3lib_div::makeInstance("tx_ameosformidable");
>> $oForm->init(
>> &$this,
>> "/path/to/xml/file.xml",
>> $uid // ==> this is the uid of the current order
>> // this ask formidable to *edit* the order
>> );
>>
>> Tell me if it works :)
>
> Back from Easter holidays, I finally had a chance to look into your
> suggestion - thanks.
>
> Seminars unfortunately uses datahandler:RAW for the time being, and
> transfers data using piVars/POST array.
>
> Have you considered creating a "datahandler:SESSION" to store values in
> a session? In a multistep it might be desirable to only save data to DB
> in last step.
>
>
More information about the TYPO3-project-formidable
mailing list