c2c-oerpscenario team mailing list archive

["Jay Vora \(OpenERP\)" <jvo@xxxxxxxxxxx>]

Thanks VMT and OLT,
It has been fixed over stable 6.0 by revision 3451 jvo@xxxxxxxxxxx-20110624085053-m4myhf1mx1j7cui0.


** Changed in: openobject-server
   Importance: Undecided => Low

** Changed in: openobject-server
       Status: New => Fix Released

** Changed in: openobject-server
    Milestone: None => 6.0.3

-- 
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:
  Fix Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/780584/+subscriptions