Can you post a short example to reproduce the problem, and better, open an issue.
On Feb 16, 9:47 am, Joe Barnhart <[email protected]> wrote: > The new release 1.92.1 seems to work -- at least halfway! > > It now shows the value of the field in a read-only fashion, but the > field.represent is not triggered, rendering the field as an integer > instead of its reference (id) representation. > > We're getting close! > > -- Joe > > On Feb 16, 5:11 am, Massimo Di Pierro <[email protected]> > wrote: > > > > > > > > > This should be fixed in trunk. Get the nightly build from the download > > page. > > > On Feb 16, 1:58 am, Joe Barnhart <[email protected]> wrote: > > > > I have a simple CRUD "create" form that's driving me crazy. I want to > > > pre-load one of the fields in the form. I want the field to show up, > > > but be read-only so the user can see it but not change it. > > > > I've tried setting the "default" property of the field and then making > > > it "readable=True" and "writable=False". The field always shows up as > > > "None" in the form. I also tried setting the form.var.fieldname=value > > > after the form is created, but before it is rendered. Still no joy. > > > > In any case, if I make the field "writable=True" I can see the field > > > is properly set. I can also change the field, however, which is what > > > I'm trying to prevent. > > > > I am using the current version of web2py and going slowing > > > insane... ;-)
