* `disabled` on the country select tag instead of `readonly`
* `create a new address` selected when the user set an invalid shipping
address and must correct it. Else the user was correcting the shipping
address but the option "ship to the same address" was selected.
Implements the UoS TODO items on stock.picking.do_partial() to fix#1432.
Add a new method _compute_uos_qty() on product.product to computes
product's invoicing quantity in UoS from quantity in UoM.
The created invoice will use the product_uos of the stock.move, meaning keeping
the quantity specified on the partial picking and the unit of measure of the
original stock.move (e.g. recieving 1 dozen from a 12 unit picking should either
get uos=dozen, uos_qty=1 or uos=unit, uos_qty=12, not a mix of both)
Fixes#1432, opw 611479
various fixes (code bugs and UI problems). some notable changes:
* lots of css fixes
* it should work with IE9+
* tooltips, confirmation dialog when removing filters
* improve main client layout (remove table structure)
* better modal windows
problem was that the pager was not displayed/hidden at the correct moment
Result is that when switching views, the header sometimes takes an extra
line. The pager is now hidden just before creating the view
the bouncing is supposed to occur when clicking on the area in view list
with no content. Problem was that the Create button was separated from
the import button while bouncing. This commit fixes the issue in a not
really subtle way: it instead bounces the whole row. I tried to find a
better fix, but I don't like jqueryui and i don't want to spend too much
time on this.
problem is that they sometimes collapse to a single line, making it
difficult to operate the search view. Other problem is that content is
not displayed sometimes (when sub view manager). Other problem is that
it does not have a scrollbar. Sidenote: modals will be properly
reworked soon (tm).
breadcrumbs incorrectly assumed that they were made with views inside
viewmanagers. But client actions can be used in breadcrumbs, so the
action manager should play nice with these widgets.
* 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
The dsn may contain the connection password of the database when not accessed from a psycopg connection object.
Replace the unfiltered logs to use cxn.dsn avoiding password leakage in logs.
Fixes#1433
General totals were not computed at all, due to the condition "if not self.ids" which was always true as self.ids wasn't set.
Besides, a parameter allows to display only partner with balance greater than 0, which was completely ignored by the totals computation methods: The totals always included all partners, even those having balance equals to 0
When generating the report 'Timesheet Profit', got a warning "The domain term '('user_id', '=', [...])' should use the 'in' or 'not in' operator."
This warning is due to the use of the '=' operator to compare the field 'user_id' while the reports sends a list of ids.
Fallback to still accept a single id in case of customised reports.
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.
Because some parameters of a field may be determined during its setup, we have
to update the corresponding column after the setup, and recompute _all_columns
to make it consistent.
Jamin Shah