[TYPO3-project-formidable] On submitting a form

[François SCHOSSIG]

OK even I do not really see the security problem: OK, I have not  
really thought about this. It does not really matter now.

But then how could it be possible to make the user aware of this  
"functionality" because it leads to a loss of data: I have lost two  
registrations because of this!

Is it possible to check if the user has used the back button ? Is it  
possible to prevent him to do this ?
--
F. SCHOSSIG, ICT Manager
Assemblée des Régions d'Europe
http://www.a-e-r.org


Le 14 nov. 06 à 11:03, Jerome Schneider a écrit :

> Hi françois, sorry for didn't answering faster, but we got lot's  
> and lot's
> of work :)
> In fact the point you've noticed is just the way Formidable is  
> working...
> When you create a record with formidable, it keeps the id of the  
> record,
> when it's created, so when you come back to the "creating page" in  
> fact
> you
> can edit, the item you've created.
> it's a security to avoid mistakes in creating items.
>
> Luc Muller
>
> François SCHOSSIG a écrit :
>> I do not know if it is great for most of the use cases. But in the  
>> way I
>> have understood FORMidable working it looks for me like a bug :  
>> normally
>> FORMidable re-edits the same record if it's uid is given as last
>> parameter to the instance of FORMidable. If this is not given, a new
>> record is created.
>>
>> So if somebody has to submit several different forms but with
>> information that is close together, this person will not be able to
>> reuse the same form (with the go back of the browser), but needs to
>> reload a new empty form each time and put again all the  
>> information. Why
>> not, but then how could it be possible to prevent users to do the go
>> back in the browser in this case ? If not, if they use it, they  
>> will not
>> know about it and we loose information that they think we have should
>> have received...
>>
>> On another side, to modify the last information sendet, you have the
>> possibility to use the save button on a form that re-loads the  
>> same record.
>>
>> Thanks for ideas.
>> -- 
>> F. SCHOSSIG, ICT Manager
>> Assemblée des Régions d'Europe
>> http://www.a-e-r.org
>>
>>
>> Le 13 nov. 06 à 10:32, Ingmar Schlecht a écrit :
>>
>>> François SCHOSSIG schrieb:
>>>> Good afternoon,
>>>>
>>>> I have just noticed something in the submitting phase of  
>>>> FORMidable.
>>>>
>>>> 1. Open and type the information in a form.
>>>> 2. Submit the form (my form makes a redirection).
>>>> 3. The record appears in the MySQL table. -> this is OK!
>>>> 4. Go back to the page with the navigator's back arrow.
>>>> 5. You get the form back and modify it.
>>>> 6. Submit again
>>>> 7. No new record is created : the fist one is juste modified.
>>>>
>>>> Do you get the same thing ?
>>>
>>> That's great for most of the use cases, isn't it?
>>>
>>> cheers
>>> Ingmar
>>> _______________________________________________
>>> TYPO3-project-formidable mailing list
>>> TYPO3-project-formidable at lists.netfielders.de
>>> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3- 
>>> project-formidable
>>>
>>
> _______________________________________________
> TYPO3-project-formidable mailing list
> TYPO3-project-formidable at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project- 
> formidable