cannot open CRM cases

Bug #816835 reported by Aline (OpenERP)
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Web (MOVED TO GITHUB)
Confirmed
Medium
OpenERP R&D Web Team

Bug Description

in new web client, try to open lead or opportunity, phone call,....

cannot open the opportunityies and all other CRM view (lead, call, ...)
Client Traceback (most recent call last):
  File "/home/aline/openerp/web/openerp-web/openerpweb/openerpweb.py", line 307, in dispatch
    response["result"] = method(controller, self, **self.params)
  File "/home/aline/openerp/web/openerp-web/addons/base/controllers/main.py", line 430, in action
    req.session.eval_context(req.context))
  File "/home/aline/openerp/web/openerp-web/addons/base/controllers/main.py", line 295, in load_actions_from_ir_values
    for id, name, action in actions]
  File "/home/aline/openerp/web/openerp-web/addons/base/controllers/main.py", line 304, in clean_action
    session.evaluation_context()) or {}
  File "<string>", line 1, in <module>
NameError: name 'section_id' is not defined

Related branches

Revision history for this message
Vishal Parmar(Open ERP) (vpa-openerp) wrote :
Changed in openerp-web:
assignee: nobody → OpenERP R&D Web Team (openerp-dev-web)
importance: Undecided → Medium
status: New → Confirmed
Changed in openerp-web:
status: Confirmed → Fix Released
Revision history for this message
Aline (OpenERP) (apr-tinyerp) wrote :

this bug is not fixed

Changed in openerp-web:
status: Fix Released → Confirmed
status: Confirmed → Fix Released
status: Fix Released → Confirmed
Revision history for this message
Xavier (Open ERP) (xmo-deactivatedaccount) wrote :

OK, so problem is modules can (and do) add data to the user session context. As a result, right after installing some modules (especially the initial setup) OpenERP is debatably useable in that it will regularly pop up complaints about missing context keys (e.g. the leads search view uses `section_id`, which is installed by `crm`).

This issue can be "fixed" by logging out and back in, triggering a reload of the user session data. Not a long-term solution of course.

The GTK client and the old web client "solve" this issue by ignoring it altogether and returning an empty context (empty dict) when an evaluation fails (whether it's the evaluation of a domain, a context, or an arbitrary python expression). I don't think that's a solution either.

A good start would probably be to reload the user session after installation from the static home page, I'm not sure how to solve for installation from the "add more features" wizard the "apply scheduled updates" menu: since they're action, we don't really know they involve installing new modules.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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