Yes, the nightly built works fine. Thanks.
On 7 feb, 15:44, Massimo Di Pierro <massimo.dipie...@gmail.com> wrote:
> Should be fixed in trunk already. Try the nightly built.
>
> On Feb 7, 4:46 am, Juan Antonio <juanr...@gmail.com> wrote:
>
> > I have
>
> > db.define_table('article', Field('name'),....,format='%(name)s')
> > db.define_table('lote', Field('name'),...., Field('article',
> > db.article)
> > db.lote.article.requires = IS_IN_DB(db, db.article.id, '%(name)s')
>
> > AndSQLFORM(db.lote,..,readonly=True) shows 'None' in field articulo
>
> > I think it is the same proble discussed here, or what am I doing
> > wrong?
>
> > I am using 1.91.6
>
> > Cheers,
>
> > Juan.
>
> > On 4 feb, 13:46, Kenneth <kenneth.t.lundst...@gmail.com> wrote:
>
> > > I´m having the same problem. In aSQLFORMI have a Field that is
> > > sometimes writable and sometimes not. If you are admin you can modify
> > > this field but not as user. Field is a reference to and other table,
> > > so admin gets a dropdown but the user gets None but he should get the
> > > selection that admin has made.
>
> > > Kenneth
>
> > > On Jan 26, 11:48 pm, Pawel Jasinski <pawel.jasin...@gmail.com> wrote:
>
> > > > Hi,
>
> > > > > Are you sure you want the formreadonly?
>
> > > > Yes
>
> > > > > What if you removereadonly?
>
> > > > The 'None' changes into drop down with ids or whatever is in the
> > > > format argument of the field.
>
> > > > > If you wantreadonlyyou do not need accepts
>
> > > > Good point, changed. It does not help with the main problem.
>
> > > > I also have another use case, where form is used on the confirmation
> > > > screen. Kind of "are you really sure ..."
> > > > All fields are maderead onlywith db.table.filed.writable=False.
> > > > Thereferencesare also rendered as None.
>
> > > > Cheers,
> > > > Pawel
