http://code.google.com/p/web2py/source/detail?r=5ce727c88ab7e99f5d16c26a45facc539679c40b


On Thu, Sep 27, 2012 at 9:34 PM, Massimo Di Pierro <
[email protected]> wrote:

> Strange. I see the effect (the manifestation of the problem) and I
> understand your explanation but I do not see the nested textarea.
>
> Can you point a particular version that broke this?
> The strange thing is that widget= SQLFORM.widgets.text.widget should be
> the default.
>
>
> On Thursday, 27 September 2012 08:29:27 UTC-5, Marin Pranjić wrote:
>
>> This happens with custom widgets.
>>
>> Minimal code to reproduce:
>>
>> def t():
>>     f = SQLFORM.factory(Field('leave_**empty', requires=IS_NOT_EMPTY()),
>>                         Field('something', 'text', widget= SQLFORM.
>> widgets.text.widget))
>>     return f.process()
>>
>> It works without widget=... inside Field.
>>
>>
>> @Massimo
>>
>> Values dissapear in line 1294 in sqlhtml.py (latest trunk).
>>
>> I'll attach two images which may help with this issue.
>>
>> First one is before line 1294 is executed. There is a nested TEXTAREA
>> inside TEXTAREA and I think this is a bug we're looking for.
>> Second image is after execution of line 1294. Nested TEXTAREA is gone but
>> the value 'xxxxxxxxx' is missing.
>>
>> Marin
>>
>>
>> Dana subota, 22. rujna 2012. 17:25:15 UTC+2, korisnik Massimo Di Pierro
>> napisao je:
>>>
>>> Check the Chrome JS console. It could be you have an extra redirect on
>>> error.
>>>
>>> On Saturday, 22 September 2012 05:09:22 UTC-5, encompass wrote:
>>>>
>>>> I am trying to fix a bug in InterestID.  http://interestid.com
>>>> The issue is that the form looses the data you enter if there is an
>>>> error in the form.
>>>> Any ideas why?  In particular the invitation and event texts are not
>>>> staying if there is some kind of error.
>>>> You can try it on out testing server all you like.
>>>> http://testing.interestid.com
>>>> Hope you can help.
>>>> You can use this use if you like.
>>>> U:testing_user
>>>> P:testinguser
>>>> BR,
>>>> Jason Brower
>>>>
>>>>  --
>
>
>
>

-- 



Reply via email to