return {'type':'ir.actions.act_window_close'} don't close view form in o2m relation

Bug #798563 reported by Carlos
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Odoo Web (MOVED TO GITHUB)
Invalid
Low
OpenERP R&D Web Team
Odoo Web Client
New
Low
OpenERP Publisher's Warranty Team

Bug Description

I add to sale.order new a field o2m to custom object B(osv.osv) . In view form of B, I add:
<button name="methon_my_close" type="object" string="Close object" icon="gtk-ok" /> or
<button name="methon_my_close" type="object" string="Close object" icon="gtk-ok" special="cancel"/>

In class B:
def methon_my_close(self, cr, uid, ids, context):
.
. custom code
.
return {'type':'ir.actions.act_window_close'}

GTK client close the popup windows, but NOT the web client (web client show empty grey windows).

My platform and browser:
- Ubuntu 10.04 LTS 32 bits.
- Firefox 3.6.16.
- Web client: 6.0.3 updated with bzr 17 jun 2011.

thx, Carlos.

Tags: maintenance
Revision history for this message
Amit Parik (amit-parik) wrote :

Hello,

I have faced the same problem in web-client So I am confirming this issue.

I have attached a video for more reference.

Thanks.

Changed in openobject-client-web:
assignee: nobody → OpenERP R&D Web Team (openerp-dev-web)
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Amit Parik (amit-parik) wrote :
Revision history for this message
OpenERP Majordomo (openerp-majordomo) wrote : OpenERP Majordomo Message

**automated message**
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:
status: Confirmed → Won't Fix
Revision history for this message
A. Schmid (aschmid) wrote :

As this problem is still present in OpenERP 6.1, I added the current project to the list

Changed in openobject-client-web:
assignee: OpenERP R&D Web Team (openerp-dev-web) → OpenERP Publisher's Warranty Team (openerp-opw)
status: Won't Fix → New
tags: added: maintenance
A. Schmid (aschmid)
description: updated
Revision history for this message
Amit Parik (amit-parik) wrote :

Hello,

I have checked this issue on latest trunk as well as 6.1 and faced the same problem, So I am assigning this too RD team also for the trunk version.

Thanks!

Changed in openerp-web:
status: New → Confirmed
importance: Undecided → Low
assignee: nobody → OpenERP R&D Web Team (openerp-dev-web)
Revision history for this message
Nicolas Vanhoren (OpenERP) (niv-openerp) wrote :

Hello, and thank you for reporting bugs in OpenERP.

In 6.1, the web client was not designed to act like this, the x2x relation popups were not created to respond like normal popups, they have their own behavior. I can understand that you think this is an error in 6.0, but from the 6.1 version, the web client has precedence over the gtk client. So any behavior difference between those two clients is not considered a bug in the web client. This could be considered a bug if that behavior caused a problem in an official addon, but as far as I know it's not the case. Plus, if we encountered that problem in an addon, we could choose to solve it in a completely different way.

So, since this is not considered a bug in 6.1 and above, I mark this bug as Invalid.

Changed in openerp-web:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.