Created by Chirag Patel (OpenERP) on 2013-01-28 and last modified on 2013-04-30
Get this branch:
bzr branch lp:~openerp-dev/openerp-web/7.0-opw-584668-cpa
Members of OpenERP R&D Team can upload to this branch. Log in for directions.

Branch merges

Related bugs

Related blueprints

Branch information

OpenERP R&D Team

Recent revisions

3730. By Chirag Patel (OpenERP) on 2013-01-28

[FIX] Fixed o2m or m2m in the form definition does not pass the context to the function fields.

3729. By Launchpad Translations on behalf of openerp on 2013-01-27

Launchpad automatic translations update.

3728. By Launchpad Translations on behalf of openerp on 2013-01-26

Launchpad automatic translations update.

3727. By Xavier (Open ERP) on 2013-01-25

[FIX] avoid storing new admin password in browser history on database creation, courtesy of Holger Brunn

3726. By Xavier (Open ERP) on 2013-01-25

[IMP] set_content_full_screen code, avoid duplications

3725. By Xavier (Open ERP) on 2013-01-25

[FIX] aggregates not being displayed in list o2ms

A template alteration previously used to remove the bottom pager of
listviews in o2ms now matches aggregate field displays.

3724. By Launchpad Translations on behalf of openerp on 2013-01-25

Launchpad automatic translations update.

3723. By Fabien Meghazi (OpenERP) on 2013-01-24

[FIX] Can't open records in form view from grouped kanban

3722. By Xavier (Open ERP) on 2013-01-24

[FIX] domain returned by onchange

The "new" form engine performs a bunch of conversions on the form arch
from json to xml to text to json again (or something), thus the
``node`` attribute on form fields might be json but it's got no more
relation to the form's own arch (and the fields defined therein).

Meanwhile the domains processing for onchange recursively traversed
the *form*'s arch trying to find a node matching the key it had to set
its @domain to what it was given. It long predates the "new" form
engine, and since it alters the *original* arch not a copy the "new"
form engine broke it. And since that's untested, it's been broken for
a bunch of months (probably).

Fix by looking up the field according to the domain key (in
form.fields), and setting the domain in the node of the field, rather
than the node of the form's arch.

3721. By Olivier Dony (Odoo) on 2013-01-24

[FIX] session: properly handle exceptions with unicode messages during dispatching

String formatting with an Exception param will use
str(Exception), raising an error if the exception
has non-ascii characters in the message.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
This branch contains Public information 
Everyone can see this information.