* dashboard did not display properly kanban in ie
* kanban did not extend to the bottom of the available screen
* custom filters did not display anything different when they were
public (not private)
* some small css problems
The new action manager only destroyed viewmanager widgets instead of
any old widget. It now checks for the widget class.
Also, minor improvement to clear_widgets: vms used to stand for
view_managers, but it can destroy any widget.
vertical text in folded kanban groups did not have a correct
orientation in IE.
Also, stupid sass compiler insists on normalizing color codes. No idea
why
This is a small change if measured in lines of code, but is a large
change: it removes the table structure from the web client and use divs
instead. It will likely break a lot of things (some css selectors
will not work), but it should simplify our lives in the future:
closer to being responsive, easier layout computations for the browsers
(and hopefully less discrepencies between the results), simpler html, ...
Restrict the property_stock_journal to the main company only. This avoids errors in multicompany when the stock journal of the main company (getting an error company mismatch) is used instead of a more useful message explaining the missing stock journal.
Fixes#3251
Non-stored fields created with the new API are not converted to old
fields and added in `_columns` (and thus `_all_columns`). This forbid
them to be used in qweb views.
A fix will be commited in 8.0 to address this issue.
When accessing an existing record in form mode directly (enter the url or refresh a page), the daterecord has not been initialized yet. This means that the value of actual_mode will be set to 'edit' before loading the current record (method _actualize_mode() called from do_show()).
This was problematic for one2many fields that we loaded in edit mode, showing add/delete icons/buttons in readonly views. (opw 607910)
This method trigger the focus event when clicking inside the modal, causing a blur event on other widgets resulting in unwanted problem. Typical case is for the jquery datetimepicker where we try to open a select element which will close right after.
The goal is to fill the page with at least 20 products and to fill all grid lines
Thus, the page should be filled with products until there are 20 products and all lines of the grid are full.
- fixed voting, karma check could be avoided
- fixed posting comments, now correctly checking karma (not for
notifications)
- fixed bootstraping of users, now not allowed to ask questions by default;
added validation email that gives the first karma points required to
participate
- added tests
Géry Debongnie