unable to save openoffice report plugin during base_report_designer module configuration

[francois]

iceweasel 5.0 debian uname Linux erpbox 3.0.0-1-amd64 x86_64 GNU/Linux
client-web 6.0.3
server 6.0.3

Administration: Module : base_report_designer
schedule for installation or schedule for upgrade
apply scheduled upgrades
during wizard configuration: OpenObject Report Designer Plug-in <save as> button
and I get a webroser error:
Iceweasel can't find the file at http://localhost:8080/openerp/form/save_binary_data/openerp_report_designer.zip?_terp_field=plugin_file&_terp_model=base_report_designer.installer&_terp_id=False.

And from client-web log:
  File "/opt/erp/web/openobject/tools/_expose.py", line 182, in func_wrapper
    res = func(*args, **kw)
  File "/opt/erp/web/openobject/controllers/_root.py", line 90, in default
    return request.handler()
  File "/usr/lib/pymodules/python2.6/cherrypy/_cpdispatch.py", line 25, in __call__
    return self.callable(*self.args, **self.kwargs)
  File "/opt/erp/web/addons/openerp/controllers/utils.py", line 112, in wrapper
    return fn(*args, **kw)
  File "/opt/erp/web/openobject/tools/_expose.py", line 182, in func_wrapper
    res = func(*args, **kw)
  File "/opt/erp/web/addons/openerp/controllers/form.py", line 670, in save_binary_data
    return base64.decodestring(data[params.field])
KeyError: 'plugin_file'

127.0.0.1 - - [25/Aug/2011:23:53:07] "POST /openerp/form/save_binary_data/openerp_report_designer.zip?_terp_field=plugin_file&_terp_model=base_report_designer.installer&_terp_id=False HTTP/1.1" 500 19412 "http://localhost:8080/openerp/execute?payload=eJxdj8FuAjEMRH-FWy4IiZ5QP4AfKJwqFIXNsLIUnJVjWArafydxAbWconkZz9g3FzqlzO5zdnNnwuiPOaKqkztkObr5zGmQHmqIMTZiPv0Z_vsExYaT0X0o8IIhi_qIQj1DFsRFQ0qQVwrF6v5erpa71vSMJFn8rlXa60fimK05D2C0kY2cMFUQgwbbnWKxpJbTZVZc1HgK3Fsm2G-_WkaXCNw-3Yi9HXitYh1SQRWt94zXIW_40fKx-4uetmma7svGbck%3D" "Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 Iceweasel/5.0"
---------
I found a similar bug (https://bugs.launchpad.net/openobject-client-web/+bug/671362)
fix commited status.
---------
So is it an other bug? Or is it a problem with my installation?

Thanks

[Vishal Parmar(Open ERP) (vpa-openerp)]

Hello francois,

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)

[Stuart Longland (redhatter)]

I'm getting almost the exact same symptoms with a self-built module, and with the CalDAV plug-in.

Unfortunately, I am stuck with 6.0 for now… I can understand that the development team have limited resources, but they have the knowledge regarding the voodoo behind the scenes that I don't. In the interests of those who are new to this framework, what are we supposed to do to fix it?

The problem will not just magically go away just because you've put out a new release as some of us have this funny thing called migration, which is a far more long-term goal than the "lets get this part working for now" goal that I and others are faced with right now. "Won't Fix" might as well be "Don't care" if we cannot gleam enough information out in order to discover the cause ourselves.

Right at this point I'm trying to debug this by inserting some debug statements to trace where the Base64 blob gets lost. It clearly gets generated and passed through to the web client, as I see Base64-encoded data in the text field. From there, where does it go? Is there some document that I can follow which describes the sequence of events from someone clicking the "Save As" button, through to this magical application/octet-stream blob appearing in the browser?

So far I'm as far as understanding where the backtrace starts, which is in form.py, save_binary_data;
        if params.datas:
            form = params.datas['form']
            res = form.get(params.field)
            return base64.decodestring(res)

        elif params.id:
            proxy = rpc.RPCProxy(params.model)
            res = proxy.read([params.id],[params.field], rpc.session.context)
            return base64.decodestring(res[0][params.field])
        else:
     pprint.pprint(data)
            return base64.decodestring(data[params.field])

The pprint.pprint was my attempt at trying to figure out what is going on, and I note the output seems to go to /dev/null. If I can somehow extract some of this information in order to figure out what is going on, I will happily contribute a patch.