[6.0 RC2] - strange and different behaviour of GTK and WEB client

Bug #699748 reported by Ferdinand on 2011-01-07
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenERP's Framework R&D
Odoo Web Client

Bug Description

the attached module allows (or should do so ) to change account_id of posted account move line (Journal Items)

Web - calls the account_move_line.write() twice
* once with the correct parameter update_check = False
* and a second time with update_check = True

GTK - seems not to do this, but does not refresh the display not showing the new account - this is shown correctly only after manual refresh

 I'd expect the same behaviour for both clients.

If it's not a misconception of my module it might cause very wired behaviour

Ferdinand (office-chricar) wrote :
Ferdinand (office-chricar) wrote :

a debugging aid to show the wired behaviour of the WEB client writing twice

Olivier DOSSMANN (odossmann) wrote :

Seems to be similar with a curious behaviour notified here : https://bugs.launchpad.net/openobject-server/+bug/698021

I have the problem of twice write() on all clients (web and gtk).

Ferdinand (office-chricar) wrote :

given that it seems to happen in standard modules too I assign it to Openobject Server too

Changed in openobject-server:
status: New → Triaged
Changed in openobject-client-web:
status: New → Triaged
xrg (xrg) wrote :

I think it is not the same case as 698021.

In the account.move.line.write() case, we are doing something extreme: we have a write() definition with more arguments than a standard orm.orm.write() function. This might be part of the problem, since some other object might be calling move_line.write() without clearing the 'update_check' flag.

In some sense, this bug may uncover a deeper problem of our framework:
sometimes we need to pass extra information through the "context" dictionary, but don't wish to expose that option to the remote (RPC) client.

/me thinks of a solution... To be continued..

Changed in openobject-server:
assignee: nobody → OpenERP's Framework R&D (openerp-dev-framework)
Changed in openobject-client-web:
assignee: nobody → OpenERP SA's Web Client R&D (openerp-dev-web)


Regarding description provided on this bug :-
I have checked scenario provided by you but it cannot reproduce this kind of stuff.

Regarding Duplicate bug:- lp:699748
I also checked lp:699748 bug. write method call multiple time b'coz In account module write method call each bank statement line and write sequence.

accoumt/account_bank_statement.py line #44
            for line in statement.line_ids:
                seq += 1
                account_bank_statement_line_obj.write(cr, uid, [line.id], {'sequence': seq}, context=context)

This code call write method for all bank statement line. I Create O2M line in another object but it work perfectly.


Changed in openobject-server:
status: Triaged → Incomplete

Thanks a lot for reporting this bug and contributing to OpenERP. Unfortunately the OpenERP Web Client project is not going to be developed further after the 6.0 series. As of 6.1 a newer and better web frontend known as the OpenERP Web project[1] will be available.
Our R&D developers normally work in Launchpad to fix bugs for the next release, but there will be no next release for the current OpenERP Web Client. As our resources are limited, all further R&D efforts from the Web team are dedicated to finish the new 6.1 OpenERP Web project[1].
This bug will be closed as "Won't Fix" to show that R&D won't be able to work on it.

Bugs affecting customers in production of course continue to be handled via the OpenERP Enterprise (OPW) maintenance service, and this is the recommended way to have them corrected directly in the 6.0 LTS stable branch.
You can find more details about all of this in the FAQ of our Bug Management Policy documentation[2].

If you are interested, you should soon be able to beta-test the new OpenERP Web 6.1 (this will be announced on OpenERP Community channels).

Thank you for your contributions and for your understanding!

[1] https://launchpad.net/openerp-web
[2] http://bit.ly/openerp-bugs-faq (FAQ #4)

Changed in openobject-client-web:
assignee: OpenERP R&D Web Team (openerp-dev-web) → nobody
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers