The comment added by Stephane above is a OPW request that was declined
as feature request, not a bug.
I still think it is a bug, as the field translate is present in
ir.model.fields, with a help text that indicates it's uses.
'translate': fields.boolean('Translate', help="Whether values for this field
can be translated (enables the translation mechanism for that field)"),
There is also a checkbox on the Administration - Customization -
Database Structure - Fields form.
But they don't work at all - the field is simply not filled when orm.py
initializes the models.
In my book, that's a bug.
Therefore I propose the fix as developed by xrg in the link in the post
above as merge request.
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/780584
Title:
Field definition translate=Yes is not stored in ir.model.fields
Status in OpenERP Server:
New
Bug description:
The field translate exists in the database, but it's not used, NULL in
all databases on all fields here.
Reading ir.model.fields over OpenObject doesn't work either, compare
http://www.openerp.com/forum/topic24970.html.
I compared two dumps: dumped database (with pg_dump), changed one field to
translate=True, -u modulename, dumped again:
diff shows no indication of translate= being stored anywhere in the database.
Same effect on removal of translate=True.
In ir_model.py, create and write are customized, handling model_props like
translate somehow, but I can't figure out where translate is stopped from going
into the database properly.
As read is not customized, though, I think this might be the problem.
So there is no way to detect from a function (action triggered) if a field is
translatable at all.
_______________________________________________
Mailing list: https://launchpad.net/~c2c-oerpscenario
Post to : [email protected]
Unsubscribe : https://launchpad.net/~c2c-oerpscenario
More help : https://help.launchpad.net/ListHelp
