Daily updates from Odoo
Navigate
Branch
Friday, December 6, 2019
21 changes
New functionality added to Odoo
Website editors can now add charts directly to pages using a new Chart snippet. This makes it easier to present business data visually with common chart formats such as bar, line, pie, doughnut, and radar charts.
Original PR description
Introducing a new snippet called Chart. This snippet uses the lib https://www.chartjs.org/ 6 types of graph are possible: Bar vertical Bar horizontal Line Pie Doughnut Radar -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website editors can now add a customizable countdown block to pages for launches, promotions, and events. The block supports different display styles and end-of-countdown actions such as showing a message or redirecting visitors.
Original PR description
This commit introduces a new snippet: Countdown. The countdown snippet is composed of 4 circle countdown, one for every time unit: seconds, minutes, hours and days. On countdown ends, 3 possible…
This commit introduces a new snippet: Countdown. The countdown snippet is composed of 4 circle countdown, one for every time unit: seconds, minutes, hours and days. On countdown ends, 3 possible actions: 1. Nothing 2. Show message: show a message once the countdown ends. The message will be displayed bellow the countdown (stopped on 0). The message can be edited through the website builder. 3. Redirect: redirect the user to the chosen URL. If the user is on the page at the exact moment the countdown reach 0, the user will be redirected automatically. If the user lands on the page after the countdown has reached 0, there will be no redirection and the link will be shown bellow the countdown (stopped on 0). The countdown layout can be customized in multiple ways: 1. By choosing to hide some time units. For instance, seconds can be hidden or only days shown. 2. By changing its design (plain background, thin circle etc). 3. By changing its size between small/medium/large. task-2093081
Enhancements to existing features
Surveys can now use a specific question to collect or update the participant's email address, with existing invitation emails prefilled to reduce retyping. The change also corrects a user-facing typo in survey validation messaging and improves related survey behavior.
Changing a product's standard cost now automatically updates the related inventory valuation records in most costing setups. This removes the need for a separate manual wizard, making product cost updates more direct and reducing the risk of missed valuation adjustments.
Original PR description
Overwrite the method ``write`` of the model ``product.product``. When we write on ``standard_price``, if - the context key ``disable_auto_svl`` is not set - the ``cost_method`` is not "fifo" We automatically compute ``stock.valuation.layer`` (before we needed to manually call ``_change_standard_price``) Task #2031422
The website editor’s left panel is now easier to use, with cleaner input layout and support for confirming entries with Enter. These changes make editing website snippets smoother and more predictable for content editors.
Resolved issues and error corrections
The Mail settings wording was updated to better describe what the External Email Server option does. This helps users understand that disabling the option does not stop external email servers from being used, reducing confusion in configuration.
Original PR description
The wording was "Use" but when you disable it the option, they don't stop being used. opw-2152288
This fixes an error that could appear when users clicked an input in the website editor's left panel. The change removes an outdated event hookup so editing controls behave reliably again.
Original PR description
I removed a handler without removing the event binding by mistake...
This fix removes an unnecessary style that caused color icons in the website editor to appear inconsistently. Users choosing colors in the editor now see clearer, uniform square icons, making the editing experience more predictable.
Original PR description
Description of the issue/feature this PR addresses: Task : https://www.odoo.com/web#id=2151416&action=327&model=project.task&view_type=form&menu_id=4720 I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Maintenance requests now show a more focused list of equipment when both an employee and department are selected. This avoids offering unrelated equipment that is not assigned to any employee, making the request process clearer and less error-prone.
Original PR description
If a department & an employee are set on a maintenance request, we select an equipment linked to the department *or* the employee **or no employee at all** (regardless of the department). Removed the last clause. It does remove the ability to select an employee and then select an equipment linked to the employee or no employee at all, but I think it makes somewhat more sense than being able to select any equipment not linked to an employee when setting both employee and department. ping @oma-odoo Also technically we might want a helper to apply a field's domain on a record somehow: onchange_department_or_employee_id has to pretty much duplicate the domain do do its thing, and it's likely bugged given the domain it defines (see above).
Code cleanup and technical improvements
Stock validation wizards now better support handling several transfers at once by showing which transfers may be affected and letting users choose the relevant ones. This makes bulk warehouse operations clearer and reduces the risk of applying immediate transfer or backorder decisions to the wrong records.
This change streamlines how website information is passed during theme installation. It is an internal cleanup that helps ensure theme setup steps apply to the correct website and supports more consistent future behavior.
Original PR description
Before this commit, the website was given as a parameter of the
_post_copy function which is called after theme install. It was then
transfered through the context when calling the theme sub' post_copy
function.
It makes actually more sense to directly call the _post_copy function
with the right website in the context instead of a parameter. This will
also allow to call enable_view/disable_view in the default post_copy
common to all theme, with the right website.Miscellaneous changes
followup of rev [0] If these wizards are called on multiple pickings, display the list of the pickings that could be impacted and allow to select which one should be impacted. We also adapt the sanity checks at the start of `button_validte` in order to specify the concerned pickings if needed. We do not enable the multi behavior for batch at the moment, so it's only enabled for the validate multi in the list view. [0] 6ab4b0d4967490ed1ee0559ec296da6637705125 task-2069646 Forwar
Original PR description
followup of rev [0] If these wizards are called on multiple pickings, display the list of the pickings that could be impacted and allow to select which one should be impacted. We also adapt the sanity checks at the start of `button_validte` in order to specify the concerned pickings if needed. We do not enable the multi behavior for batch at the moment, so it's only enabled for the validate multi in the list view. [0] 6ab4b0d4967490ed1ee0559ec296da6637705125 task-2069646 Forward-Port-Of: odoo/odoo#41475
Parallax elements are overflow:hidden so that their moving background does not overflow. This introduces a limitation: no dropdown can overflow the snippet either. While a better solution should be found in master, this allows overflow for the "fixed" parallax which does not use an overflowing background. opw-2091324 Forward-Port-Of: odoo/odoo#41471 Forward-Port-Of: odoo/odoo#41455
Original PR description
Parallax elements are overflow:hidden so that their moving background does not overflow. This introduces a limitation: no dropdown can overflow the snippet either. While a better solution should be found in master, this allows overflow for the "fixed" parallax which does not use an overflowing background. opw-2091324 Forward-Port-Of: odoo/odoo#41471 Forward-Port-Of: odoo/odoo#41455
Writing barcode on a template will only write it on the variants if the variant count is 1. Make the field readonly on the view according to this condition. Forward-Port-Of: odoo/odoo#41462
Original PR description
Writing barcode on a template will only write it on the variants if the variant count is 1. Make the field readonly on the view according to this condition. Forward-Port-Of: odoo/odoo#41462
You can use has_group(employee) instead + fix enumerate_page: when you search a page with visibility constraints, you never seen it even if force was set to True. task-2091365 again Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#41459
Original PR description
You can use has_group(employee) instead + fix enumerate_page: when you search a page with visibility constraints, you never seen it even if force was set to True. task-2091365 again Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#41459
- Go to Contacts - Search by 'Tag' with a non existing tag A crash occurs. This is because of an incorrect SQL: `WHERE "category_id" IN ()` In case of an empty list `ids2`, we fall back on `(None,)` Note that it appears only in v13 because `child_of` was added at [1], but the issue also exists in v12. [1] https://github.com/odoo/odoo/blob/b6325ae45b830a725f6ab6706b70f65c809be4a7/odoo/addons/base/views/res_partner_views.xml#L471 opw-2151129 Description of the issue/featu
Original PR description
- Go to Contacts - Search by 'Tag' with a non existing tag A crash occurs. This is because of an incorrect SQL: `WHERE "category_id" IN ()` In case of an empty list `ids2`, we fall back on `(None,)` Note that it appears only in v13 because `child_of` was added at [1], but the issue also exists in v12. [1] https://github.com/odoo/odoo/blob/b6325ae45b830a725f6ab6706b70f65c809be4a7/odoo/addons/base/views/res_partner_views.xml#L471 opw-2151129 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#41451
MAke sure to always set the expiration date of a coupon. opw-2151284 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#41448
Original PR description
MAke sure to always set the expiration date of a coupon. opw-2151284 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#41448
OPW 2151580 There is a needed font for the swiss IRS report: OCR-B. This commit ensures it is used. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#41428
Original PR description
OPW 2151580 There is a needed font for the swiss IRS report: OCR-B. This commit ensures it is used. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#41428
Search bank account with company to handle the case where the res.partner.bank is defined in several companies. Without this commit, a Value error was raised because we expect only one record returned. Description of the issue/feature this PR addresses: opw-2128323 Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#41441
Original PR description
Search bank account with company to handle the case where the res.partner.bank is defined in several companies. Without this commit, a Value error was raised because we expect only one record returned. Description of the issue/feature this PR addresses: opw-2128323 Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#41441
Create a new contact (just open the create form) The "Language" field is missing, because active_lang_count is not computed before the record is saved, but it is necessary to display the language field opw-2149324 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#41162
Original PR description
Create a new contact (just open the create form) The "Language" field is missing, because active_lang_count is not computed before the record is saved, but it is necessary to display the language field opw-2149324 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#41162
A method was renamed in the accounting module and the change was not mirrored in this module. Forward-Port-Of: odoo/enterprise#7099
Original PR description
A method was renamed in the accounting module and the change was not mirrored in this module. Forward-Port-Of: odoo/enterprise#7099