c2c-oerpscenario team mailing list archive

[Numérigraphe <645172@xxxxxxxxxxxxxxxxxx>]

Closing vor 5.0 as it can't be changed of course, and marking opinion so
as not to interfere with the release of 6.0.

** Tags added: long-term

** Summary changed:

- readonly="1" works only for some types of fields
+ readonly="1" in views does not work when object state makes the field readonly=False

** Description changed:

- In the current 5.0 client, it seems that you can't make all field read-only just by adding readonly="1".
- It seems to work for char and float.
- It seems NOT to work for one2many, many2one, date and selection.
+ When a field has a "states" attribute that makes it writable, you can't make it read-only in a view by using the XML attribute readonly="1".
  Lionel

-- 
readonly="1" in views does not work when object state makes the field readonly=False
https://bugs.launchpad.net/bugs/645172
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject GTK Client: Opinion
Status in OpenObject GTK Client 5.0 series: Invalid
Status in OpenObject GTK Client trunk series: Opinion

Bug description:
When a field has a "states" attribute that makes it writable, you can't make it read-only in a view by using the XML attribute readonly="1".
Lionel