← Back to team overview

openerp-dev-web team mailing list archive

[Bug 733089] Re: when nested o2m are there. `New` for o2m does not work when o2m-level>1 in first go (when parent is not saved yet)

 

Hello NOVOTRADE RENDSZERHÁZ,

Yes you are right, your patch is correct. 
Current code creates problem and we have already sent merge proposal for the same.

The fix for web-client has been committed to lp:~openerp-dev/openobject-client-web/6.0-opw-5073-sma
with the following revision.

Revision-info:
4575 sma@xxxxxxxxxxx-20110408111430-6v2n8ze0v8185llv

Soon it will be merged into stable web-client branch.

Thanks for reporting!



** Changed in: openobject-client-web/6.0
       Status: Incomplete => Fix Committed

-- 
You received this bug notification because you are a member of OpenERP
SA's Web Client R&D, which is a bug assignee.
https://bugs.launchpad.net/bugs/733089

Title:
  when nested o2m are there. `New` for o2m does not work when o2m-
  level>1 in first go (when parent is not saved yet)

Status in OpenERP Web Client:
  Fix Released
Status in OpenERP Web Client 6.0 series:
  Fix Committed
Status in OpenERP Web Client trunk series:
  Fix Released

Bug description:
  Hello,

  When we have nested o2m in an object, and assuming we are not saving parent record manually and no o2m is inline-editable.
  on click of `New` for first-level o2m (say X) works fine, and opens empty-X-form in frame dialog
  now in X's form, for second-level o2m (say Y) when we click on `New`, it saves X(means its parent) but could not open Y's form in first click. but once X is saved (manually or indirectly), we can create Y successfully.

  Some fields of DOM could not be find in `edit` function of `One2Many` javascript class in first go when o2m-level>1.
  you can test this in Human Resources -> Configuration -> Payroll -> Salary Structure (to test no o2m should be inline editable)

  Note: this bug exist in web-client-trunk