summaryrefslogtreecommitdiff
path: root/addons/document/wizard/document_configuration_view.xml
diff options
context:
space:
mode:
authorAaron Bohy <aab@odoo.com>2015-06-10 15:03:12 +0200
committerAaron Bohy <aab@odoo.com>2015-06-10 15:34:41 +0200
commita7ecb9d6ca89be009d3c0b9f33c8ed572257ab07 (patch)
treee37c8d9849d9d3ed187dc502d1e3272f2b324ddf /addons/document/wizard/document_configuration_view.xml
parenta5f0198f9c8feb814b5a80f6817ec95b118fc2b7 (diff)
[FIX] web, web_diagram: load correct view on direct access/refresh
!! THIS SHOULD NOT BE FORWARDPORTED TO MASTER !! When loading an action with a specific url (e.g. when refreshing the browser), the view displayed before refreshing should be loaded directly (except for form views, for which we need the default view to be loaded first to keep the breadcrumbs intact). Before this rev, it automatically first loaded the default view for the model (i.e. the first view in the views' list), and then switched to the previously displayed view. This sometimes produced an error when using a filter needing a field not available in the default view (e.g. Reporting > Project > Issues Analysis, switch to the second view 'Graph', and then refresh -> Error). This revision introduces a new key in the View widget: multi_record. This key distinguishes views that aim to display several records (e.g. List, Kanban ...) and those that display a single record (i.e. Form and Diagram). We use this key to decide whether or not the view stored in the url should be directly loaded (yes for multi-record, no otherwise).
Diffstat (limited to 'addons/document/wizard/document_configuration_view.xml')
0 files changed, 0 insertions, 0 deletions