in the web client, raise osv.except_osv in an on_change field opens in a popup window but redirects to the same page as the parent window

[Randy Nivales]

To replicate this bug, use this function below:

def check_phone_number_input_format(self, cr, uid, ids, data1):
        result = {}
        compiled_regex = re.compile("(^[0-9]{2}\/[0-9]{3}\.[0-9]{2}\.[0-9]{2}$)|(^[0-9]{3}\/[0-9]{2}\.[0-9]{2}\.[0-9]{2}$)")
        if data1:
            matched = compiled_regex.match(data1)
            if matched:
                return result
            else:
                raise osv.except_osv(('User Input error'),('Please correct the format of the telephone number (it must be 00/000.00.00 or 000/00.00.00), it does not pass the check'))

 Then this one in the

_columns = {
        'work_phone': fields.char('Work Telephone Number', size=32, help="Employee's work telephone number"),
}

Then this one in the XML file

<field name="work_phone" on_change="check_phone_number_input_format(work_phone)" />

Problem is, in the web client, when the on_change is triggered, it opens in a popup window but redirects to the page with content same as the parent window.

Server: Ubuntu 10.04 Desktop 64bit
OpenERP Server: 6.0.3
Web Client: Chrome and FF

[Randy Nivales (randynivales)]

Any update on this?

[Jignesh Rathod(OpenERP) (jir-openerp)]

Hello Randy,

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!