When loading an action using a specific url, with
a view_type different than the default view of the action
(e.g. Project > Project > Issues has as view order
kanban, list, calendar, form, graph, and try to load
this menu action from an url, but by specifying another view_type
than 'kanban', for instance, 'list'), the default loaded view was
always the first view, and then a switch was done to go to the view_list.
It caused issues when using a filter needing a field available in the list
view but not in the kanban view.
It also lead to an issue in the reporting, when trying to load a reporting
action with a view not being the first one of the action
(e.g. Reporting > Project > Issues Analysis, switch to the second view
'Graph', and then refresh -> Error).
This revision makes so the view from the view_type url arg is directly loaded.
opw-640289
Delete recurring invoice lines when their contract is deleted.
Otherwise, when a contract is deleted, the lines remain orphan with no way to
access it or may generate wrong invoice (should not happen in standard as only
accessed through contracts via recurring_invoice_line_ids).
Fixes#6801
and the render of the buttons.
The sibar menu can depends on the current view and fields
states.
We therefore have to wait for them to be loaded before loading
the sidebar.
Before this rev., loading a report view (in the reporting menu),
leaded to a crash, due to this revision: ac92551406.
opw-640409
A member can be a free member, but still have paid membership.
So we only should display member in a free membership_state and should
not get dupes.
closes#6805
opw-640440
A user (other than the admin) part of the group 'Manage QWeb views'
and the group 'Administration Settings' couldn't edit
any other view than QWeb views.
opw-640376
On the website, on an event track page having
multiple speakers, the image of the first speaker
was displayed for all speakers.
This is no longer the case with this revision.
opw-639915
fixes#6715
Was removed at 5b479e6 as no longer used (and was a wrongly used there as dit not
check if a "normal" BoM has an higher sequence).
However for stablility reason, we do not remove methods in version 8.0 (if was
used in community).
Will be removed in master.
Thamks to parent commit, `request.env` doesn't raise `AttributeError`
anymore for requests without session bound to a database.
This exception was bubbling up to `digits` property (and `__getattr__`)
This reverts commit 49cb46fb78.
This reinstate commit eeedd2d9f5.
The `rotate` flag introduced by 31d817e849
was initialized at the very end of the session init, after
the reset of the `modified` flag.
This had the side-effect of marking the session as modified
for every request, saving the session to disk every time
even without any change.
Closes#6795
Arthur Maniet