Need to reload session after installing addons

[Xavier (Open ERP)]

There's a long-standing problem in OpenERP: 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`).

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.

[xrg (xrg)]

On Tuesday 06 September 2011, you wrote:
> Public bug reported:
>
> There's a long-standing problem in OpenERP: 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`).
>
> 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.

IMHO, the "reduced functionality" approach (current behavior) is more
appropriate.
Now, we can have the Admin performing maintenance tasks (such as module
updates, installs) while users of the system keep their clients running etc.
It is important that they can keep a form open and not lose the temporary data
they enter until the 'Save' button.

Depending on the nature of update/modify, the user may continue, need to close
and re-open a form or (worst case) need to logout and login again. If we had
forced a session reload, we would definitely interrupt the users and thus
reduce the Admin's ability to hot-maintain the db.

Note also that client-side expressions only come at Form loading time, so new
expressions will come with new context, won't they?

My 0.00 cents (rounded by decimal_precision)

[Xavier (Open ERP) (xmo-deactivatedaccount)]

> Note also that client-side expressions only come at Form loading time, so new
expressions will come with new context, won't they?

That's incorrect. There are a number of actions which use context values to e.g. setup search views. The Leads view, for instance, can not be used right after being enabled/installed in the new web client, it will error out.