Yes, that would be it, thanks. We upgraded unintentionally in just
one environment and missed the API and default behaviour change
between 1.2.1 and 1.2.2. Our functional tests wouldn't have picked it
up - a scripted PUT works just fine and we haven't automated browser-
based testing. Oh well,
http://formencode.org/modules/htmlfill.html#formencode.htmlfill.render
The keyword argument force_defaults=True will remove values from the
html that are not given in the defaults dictionary. Maybe this is
what you were experiencing?
On Mar 31, 2:29 am, Mike Burrows wrote:
> Hi,
>
> Has anyone
Hi,
Has anyone seen formencode turn
to
?
After a lot of head-scratching (a lot of wasted time looking at
webhelpers) we reverted from 1.2.2 to 1.2.1 and the problem went
away. Are we doing something wrong?
Thanks,
Mike
m...@asplake.co.uk
http://positiveincline.com
http://twitter.com/as
