[TYPO3-project-formidable] Remebering previous entered form data.

[Jerome Schneider]

Hello Tonni,

Here's a simple way to achieve this.

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 :)
Cheers, Jerome


Tonni Aagesen a écrit :
> Hi,
> 
> I'm still working on integrating paymentlib in seminars using formiable 
> (0.7.0).
> 
> My problem is that in the registration flow, I need to switch away from 
> the formidable generated form/page, so that the users can enter their 
> payment details.
> 
> A little illlustration of the flow:
> 
>   [registration begin]
>           |
>           |
> [Choose payment method] ++++++
>           |                  +
>           |                  +
>           |           [Commit payment]
>           |                  +
>           |                  +
>    [Registration end]+++++++++
> 
> 
> The "+" line in the flow indicates where browser leaves the users site 
> for entering their payment details in a page/form provided by the 
> payment gateway.
> 
> So what I need is a way for formidable to remember previous entered form 
> data and where in flow the user left off, so no data is lost when the 
> user returns to finalizing the registration.
> 
> Any hints on that ?
>