Correctly use the email_from tag from template.
This partially reverts commit 0f82346167.
"[FIX] email_template: keep email_from and outgoing server"
Remove the email_from part that was incorrect, keeping the one on mail_server_id
Instead of assigning an non-evaulated email_from in the context, specify the
email_from in the onchange method. This way the created email has an evaulated
from value. This was an issue for templates using email_from like
"${(object.user_id.email or '')|safe}"
In the _notify method method, the email_from is partially respected as it will
be used a fallback only. However changing that would introduce a modification of
behaviour not suitable for 7.0 branch.
Fixes#8409
In e-commerce, on a product page. If the product has some attributes
("product.attribute.line" model) with several values for at least one attribute
(which means several variants for one product), the display of these attributes must
respect the sequence defined in:
Sales > configuration > products > attributes("product.attribute" model)
opw:648634
The recomputation should not be necessary, as we normally don't change the
record referred by an ir_model_data record. This speeds up the creation of
ir_model_data records by 33%, which should be noticeable during module
installations.
Before this commit, you had to click on "Add a line", then select
a value in the m2o which appeared, then click on "Add". Now, the m2o
is always there in edit mode and you just have to click "Add" once.
When a new line was added, all the others changed their value to 0.
This was because of a property : the sheets propertywas read thanks
to a get('sheets') but as it is an array of object, modifying those
object will modify the sheets (without calling any handler attached
to the 'change:sheets' event). It appeared the form_view set_values
method changed those objects.
A simple solution from a timesheet point of vue was to deep clone the
sheets property before using it.
The test was not stable enough since listview editable and onchange
API changes.
+ Some step were wrong (test of the wrong element)
+ Minimize differences with enterprise version (so that the two tests
are testing the same things)
(backport of enterprise version)
Fix various problems with list view editable :
* Click outside which should discard/save the line in edition
* Warnings which should not appear when line is being discarded/saved
* JS test
+ JS code refactoring
The css of a mail is inlined as best as possible for the mail sending.
Previously, if there was a selector like .ch[onclick="ga(this,event)"]
the simple splitting would split in the middle and get one erroneous
selector (which then would trigger an error).
With his commit, rules containing " or ' are ignored.
opw-643548
note: forward port of 6316bce
In Accounting > Bank and Cash > Cash Registers, when clicking in "More" button
on 'Put Money In' or 'Take Money out', the date used for the bank statement line
created must be the date of the bank stattement(same behaviour then when clicking
on "Add item" in edit mode). It's forbidden to put/take money in/out for a bank
statement which is not open.
opw:647631
Postgresql has a limit of 64 characters for tables, columns names
as well as for aliases names.
When generating an alias name, e.g. for group by and order
by clauses, if the alias is longer than 64 characters,
use hashing to force the alias length to be within this
64 chars limit.
Fixes#8094Closes#8142
the link to the Apple app store was missing and the other links were bogus
These link now send to the odoo.com website with some GET parameters; that way we can redirect from our end to the correct app
To compute the intervals of working time, the function interval_get_multi
used 'hour_to' and 'hour_from' from "resource.calendar.attendance" model. 'hour_to'
and 'hour_from' are not in UTC timezone. All the dates in odoo are compared in UTC.
Then 'hour_to' and 'hour_from' must be converted.
To take into account the minutes in this computation, the minutes from the start date
are added in the variable todo (number of working hours).
opw:648349
In e-commerce, on a product page. If the product has some attributes
("product.attribute.line" model), the display of these attributes must
respect the sequence defined in:
Sales > configuration > products > attributes("product.attribute" model)
opw:648634
Complement of the fix 6f355623f0
Adds the button for cash registers as well since the base view is
different than the one for bank statements.
Closes#8410Closes#8342
- New calendar dashboard with the leaves of every employee
- New "Leaves to Approve" menu with to-approve department leaves
- Renamed and reorder menus
Odoo Task 12913
Closes#7292
Yannick Tivisse