Commit 89a4774c21 changed the kwargs
debug value of the FieldTextHtml controller to let it be equal to
"assets" instead of True or False. The problem is that an empty string
was considered True before the commit and False afterwards.
In fact, the original code was wrong and the debug value should equal
the already processed kwargs debug value in the HttpRequest object.
Indeed, the kwargs.debug value is equal to the URL value while the
request.debug value is already processed and is only one of the 3
values: None, True or "assets".
When positioning an element in an editable list view, that element is
temporarily forced to display: block thanks to the class o_temp_visible
The rule is written in LESS thanks to:
.o_list_editable .o_temp_visible { display: block!important; }
which is ok for normal invisible form fields because it is written as
.o_form_view .o_form_invisible { display: none!important; }
which has the same priority but is defined before the o_temp_visible
rule, so the display is properly forced to block.
However, for some reason, there also is the rule:
.modal .modal-dialog .o_form_invisible { display: none!important; }
which has a higher priority than the o_temp_visible rule.
This is why appearing invisible fields in editable list view in modals
are at a wrong position.
The solution introduced by this commit is the safest: adding a new
rule to force display block!important on the selector:
.o_list_editable .o_temp_visible.o_form_invisible
Fiscal position was setted by onchange before commit #55535a6
Now, we need to call the onchange_shipping_id to set the fiscal position.
In case where the owner of the sale order is the public user, instead to
use the fiscal position from public user, we try to guess it with the
geolocation.
This tries to be the smallest patch possible in order to avoid triggering
another display issues, so we only patch in the ms-hight-contrast section
which only applies on ie 10/11.
* The view-manager weren't displayed correctly; they didn't fit 100% of
the screen width. This is fixed by explicitely seting the top, right,
left, bottom attributes.
* The modals content were not displayed. This was due to 2 issues:
* The rule that we patch in the first point set the position of
`oe-view-manager` as absolute with an importang flag. Because of
this important, the rule that reset the position of the
`oe-view-manager` as static in modals.less was not honored. So
we also patch this rule with an important flag inside the same
file (so that all the fixes related to ie10/11 are in the same
place).
* Now that the modals are displayed, they do not fit 100% of the
screen. It's because the `max-height: 100%` of `.modal-content`
set in modals.less does not work in ie10/11, due to some bug
with the flex displays. We set the height to 450px so that the
modals are kind of correctly displayed on a 1366x768 screen
(their content are still scrollable).
related to rev 1ccd87a037closes#12929
The field symbol is not required on a res.currency (it should and will be
changed in master). In case it is not set, do not display the currency in the
rapport.
Fixes#11346
FIX 1
-----
If the partner_id is not allowed, we return the placeholder.
Before this commit, the status as undefined and raise traceback.
UnboundLocalError: local variable 'status' referenced before assignment
FIX 2
-----
Fix the defaultheader to avoid to have:
[[('Content-Type', 'image/png')], ('Content-Length', 43)]
And so, during parsing by werkzeug:
ValueError: need more than 1 value to unpack
Change default definitions of funds clearing accounts to be assets
instead of liquidity. Without this fix, reconciling to these
accounts during bank reconciliation is not generating the correct
journal, but is treating the process as a matching step (which it
is not).
For existing data, the accounts will need to be manually changed
from liquidity to current assets.
Closes#12996
Commit 977db823c7 refactored the web module so that it gathers
common features of community and enterprise. The problem is that the
web.webclient_bootstrap template content lost its groups attributes.
This had the effect to make the client crash when accessing the
template for calendar invitation for example, as the template was
trying to render menus without menu data.
The button does not recompute the cache, it removes it which will be recomputed
when you launch a POS.
Hide the button when there is no cache (e.g. after installation).
The main content of the web client was set to grow/shrink so that it
fills the window (thanks to flex). However, to be able to shrink as
much as necessary the min-height needs to be forced to 0.
Without this fix, the web client was overflowing on the bottom of the
page, making impossible to access some menu items.
The price of the delivery is incorrectly converted to the currency of
the user in the payment template (next to "Total").
Instead, it should be in the currency of the sales order.
opw-682306
Steps to reproduce:
-Create a first journal with a sequence
-Create a second journal with the same sequence
-Create a first SO, create the invoice for the fist journal and validate it
-Create a second SO, create the invoice for the second journal and validate it (the second invoice has the exact same name as the first one)
-Refund the second invoice (linked to the second SO)
-Go to the first SO => In the invoice button, you see 2 linked invoices (there is normally only one)
When searching the refunds corresponding to the invoices in function
_get_invoiced, the refund must take the journal of the invoice into account.
opw:684144
If you create a picking, with an owner, for qty x, and confirm it.
Next transfer x+1, it will raise a traceback 'cannot adapt res.partner'
Now, we pass the id, and not the browse record.
This commit closes#12978
In case of event not all day, the timezone has an impact.
So if we search for date >= 2016-01-31 (00:00:00) and that the current timezone
is +5, we should search for date >= 2016-01-30 19:00:00.
date_to_str will drop the time.
This commit closes#12878
This commit closes#12971
When creating a new exchange rate, the default date is always the date
of the last server restart.
This is because `fields.Date.today() + ' 00:00:00'` is a fixed string
and the field is instanciated only at startup.
opw-684622
In some cases, the "Sales total(Revenue)" of the report is different
from the sum of the payments. To reproduce:
- create a product with a sale price of 1.00
- sell 3 times a quantity of 0.333 of this product
- the "Sales total(Revenue)" will be equal to 1.00, while the total of
payments is 0.99.
This is because in the report, we first sum all order lines, then we
perform a global rounding.
The solution is to use the total amount calculated for each order, which
is rounded at the appropriate time.
opw-682782
Now, if the first post of a user is marked as spam, we remove 10x the karma.
(by default 10 * -100= -1000)
That will avoid to the moderators too many click to 'kill' a spammer.
This commit is related to #12803
Before this commit, a user was able to post withtout limit new post.
They was added to the modarator queue.
Now we only support 1 post by user.
This commit is related to #12803
The id of the user to browse has been omitted
during the below forward port revision:
95a2f8b121
We can see in the original revision that it was
correctly there:
cbb51610ee
This had as wrong side-effect to not display
views with a group set in the customize menu,
as it checked the groups of a null user browse
recordset.
opw-684326
Closes#12895
The module `sale_service` has been merged in the module
`sale_timesheet` in the revision
234f88a6af
We only remove the field from the view due
to the fact saas-11 is a stable. The field
has already been removed from the model
in newest releases (`saas-12`)
opw-682816
qsm-odoo