Daily updates from Odoo
Thursday, November 14, 2019
33 changes · master
New functionality added to Odoo
Israeli invoice PDFs now show whether the document is the original or a copy directly beneath the title. This helps businesses and customers clearly distinguish official originals from duplicate documents for compliance and recordkeeping.
Original PR description
Description of the issue/feature this PR addresses: Pt. 2 of [this task](https://www.odoo.com/web#id=2052707&action=327&model=project.task&view_type=form&menu_id=4720) Current behavior before PR: PDF doesn't state if it's the an original or a copy beneath the title. Desired behavior after PR is merged: PDF states if it's the an original or a copy beneath the title. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
This change lets businesses archive custom records using an active status field, improving lifecycle management without deleting data. It also updates the web interface so custom records can use the same archive behavior as standard records.
Original PR description
Towards solving #26162 Maintained replacement of: https://github.com/odoo/odoo/pull/26163 **Description of the issue/feature this PR addresses:** - Improve record lifecycle management - Allow archiving **Current behavior before PR:** - Custom record could not be made archivable by no means **Desired behavior after PR is merged:** - `x_active` acts as a proxy for magic `active` - All magic works on `x_active`, too. **Note:** Please do not close, even if not immediately accepted (`wishlist` tag). This PR is meant to be carried along and actively maintained, until this semantic will be completed this way or another. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @xoe-labs
Cash rounding settings now allow businesses to define separate accounts for rounding gains and losses. This helps Belgian accounting users route positive and negative invoice rounding differences correctly, while preserving the existing behavior when no loss account is configured.
Original PR description
Cash rounding only allowed for one account to be specified => Belgian accounting requires 2 types of account depending on whether the rounding line on the invoice is a + or - amount. On cash rounding config (account.cash.rounding), one account is added (many2one). Existing account is renamed Profit account, new account is named Loss account. The loss account is used when rounding line has a negative amount, and vice versa for profit account (account.move). If no Loss account is set, only Profit account is used. Task :https://www.odoo.com/web?#id=2091658&action=327&model=project.task&view_type=form&menu_id=4720
This update fixes small wording mistakes in internal web code comments and adds the contributor's legal signature. It has no expected effect on product behavior, but keeps the codebase clearer and contribution records complete.
Original PR description
Just fixing a few irresponsible typos. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The accounting chart setup and regular views are now more consistent, making navigation easier for users. Asset-related fields were also added to the list view so finance teams can see and manage asset settings more directly.
Original PR description
**Chart of Accounts** - Same views for config bar and regulare one - Add create_asset and asset_model fields in list view. **Task ID: 2048225**
Resolved issues and error corrections
This fixes the VAT label used for Colombia so it better matches the local business terminology. Colombian users will see the correct tax identification label in country-specific records and related forms.
Original PR description
This PR updates the vat label of Colombia. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @xoe-labs
Stock transfers now handle newly added items more consistently, so availability checks and related warehouse rules appear and apply as expected. Immediate transfers with added quantities are also marked ready correctly, reducing confusion and helping warehouse teams process transfers without unnecessary delays.
This update fixes an internal automated test for Snail Mail account processing so it can reliably load required assets during test runs. It helps maintain quality and stability by preventing false test failures without changing normal user-facing behavior.
Original PR description
Somehow, the fact that this test has been converted (partially) to a SavepointCase makes the assets to be rollbacked after generation. Notify the registry to be in "test" mode, where one cursor serves several requests, solves the issue (no 404 when getting the assets, and no registry reloading). 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
Email addresses with special or non-English characters are now formatted more reliably. This prevents missing address markers and avoids corrupted email content in some mail clients, improving the consistency of sent messages.
Original PR description
[FIX] tools: correctly format emails when having an encoding issue [IMP] tools: restore P2 formataddr default behavior [FIX] ir.mail.server: squash redundant CRs (bpo-34424) Task: 2003936
Fixes an issue where subscription reference numbers could be missing or disrupted during creation. This helps sales teams keep subscription records consistently identified without requiring manual entry.
Original PR description
Task:https://www.odoo.com/web#id=2093548&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.00069edd89c2440dbeb54c1008fcd252
Miscellaneous changes
Ignore exceptions when resolving dependencies in that case. This reimplements a behavior from former versions. Forward-Port-Of: odoo/odoo#40286
Original PR description
Ignore exceptions when resolving dependencies in that case. This reimplements a behavior from former versions. Forward-Port-Of: odoo/odoo#40286
With this PR we can use the IoT Box with the new Raspberry Pi 4 B using raspbian 'Buster' With buster we remove the kiosk mode of firefox and replace this mode with a fullscreen view of firefox. To do that we adapt DisplayDriver to expend window with a 'call_xdotool(F11)' We remove postgresql and patch `odoo/odoo/http.py` for he does not return a DB. We edit the `/root_bypass_ramdisks/etc/resolv.conf` to be able to be connected trough `chroot /root_bypass_ramdisks` and so can use apt
Original PR description
With this PR we can use the IoT Box with the new Raspberry Pi 4 B using raspbian 'Buster' With buster we remove the kiosk mode of firefox and replace this mode with a fullscreen view of firefox. To do that we adapt DisplayDriver to expend window with a 'call_xdotool(F11)' We remove postgresql and patch `odoo/odoo/http.py` for he does not return a DB. We edit the `/root_bypass_ramdisks/etc/resolv.conf` to be able to be connected trough `chroot /root_bypass_ramdisks` and so can use apt or apt-get install package Task id: 2089286 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#40043
When installing requirements on MS Windows platform with Python 3.8, the Pillow requirement is defined two times. This leads to a pip crash. With this commit, the Pillow requirement is only defined once. Fixes #40080 Forward-Port-Of: odoo/odoo#40239
Original PR description
When installing requirements on MS Windows platform with Python 3.8, the Pillow requirement is defined two times. This leads to a pip crash. With this commit, the Pillow requirement is only defined once. Fixes #40080 Forward-Port-Of: odoo/odoo#40239
stdnum is not a mandatory dependency It is often present as required to install the base_vat module but having a system with account without the dependency should be possible. As the calc_check_digits is pretty small, it is easy to extract Replaces and closes odoo/odoo#40067 Forward-Port-Of: odoo/odoo#40253 Forward-Port-Of: odoo/odoo#40238
Original PR description
stdnum is not a mandatory dependency It is often present as required to install the base_vat module but having a system with account without the dependency should be possible. As the calc_check_digits is pretty small, it is easy to extract Replaces and closes odoo/odoo#40067 Forward-Port-Of: odoo/odoo#40253 Forward-Port-Of: odoo/odoo#40238
After loading the calendar view, making a search with an inactive domain in the list will trigger a search "partner_ids not in []" which returns zero result. The code intention was to initialise the avoidValues, not to send an empty list. To reproduce the issue: 1. create an event shared between user 1 and 2 2. as user 2, open the Calendar menu -> shared event is present 3. click on "week" tab (forcing a refresh) -> shared event no longer appears @Gorash can you please have a look?
Original PR description
After loading the calendar view, making a search with an inactive domain in the list will trigger a search "partner_ids not in []" which returns zero result. The code intention was to initialise the avoidValues, not to send an empty list. To reproduce the issue: 1. create an event shared between user 1 and 2 2. as user 2, open the Calendar menu -> shared event is present 3. click on "week" tab (forcing a refresh) -> shared event no longer appears @Gorash can you please have a look? I am not sure this is the proper fix as I don't understand all the interactions. I was not able to understand why, when clicking on the Calendar menu, I get a different list of filters than clicking on the "week" tab. Maybe should be merged in upper versions than 11.0 for safety. Forward-Port-Of: odoo/odoo#40106
http://runbot.odoo.com/runbot/build/683028 http://runbot.odoo.com/runbot/build/687505 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40054
Original PR description
http://runbot.odoo.com/runbot/build/683028 http://runbot.odoo.com/runbot/build/687505 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40054
When adding a new record to a Many2one, after the record is created the inverse is calculated and written. Before this commit, the inverse is set to be modified in all the elements of the Many2one, this means that, the “write” method is called for other lines that the one that is added. Now, the inverse is set to be modified only if it's different from the current value. opw-2091842 Co-authored-by: Raphaël Collet <rco@odoo.com> Forward-Port-Of: odoo/odoo#39927
Original PR description
When adding a new record to a Many2one, after the record is created the inverse is calculated and written. Before this commit, the inverse is set to be modified in all the elements of the Many2one, this means that, the “write” method is called for other lines that the one that is added. Now, the inverse is set to be modified only if it's different from the current value. opw-2091842 Co-authored-by: Raphaël Collet <rco@odoo.com> Forward-Port-Of: odoo/odoo#39927
Do not insert variable inside a translated message, it will not be translated. Fixes odoo/odoo#40178 Forward-Port-Of: odoo/odoo#40242 Forward-Port-Of: odoo/odoo#40191
Original PR description
Do not insert variable inside a translated message, it will not be translated. Fixes odoo/odoo#40178 Forward-Port-Of: odoo/odoo#40242 Forward-Port-Of: odoo/odoo#40191
Changing the filter color and its intensity was not working anymore because of failed JS refactoring when the logic was shared for both blog posts and events in website. Forward-Port-Of: odoo/odoo#40217
Original PR description
Changing the filter color and its intensity was not working anymore because of failed JS refactoring when the logic was shared for both blog posts and events in website. Forward-Port-Of: odoo/odoo#40217
FIX [2092459](https://www.odoo.com/web#view_type=form&model=project.task&id=2092459&active_id=2092459&menu_id=) The reconciliation tries to find partner based on the bank number, but that bank number may not be encoded the same way depending where the statement lines come from. A solution is to sanitize the bank number at query time. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have sign
Original PR description
FIX [2092459](https://www.odoo.com/web#view_type=form&model=project.task&id=2092459&active_id=2092459&menu_id=) The reconciliation tries to find partner based on the bank number, but that bank number may not be encoded the same way depending where the statement lines come from. A solution is to sanitize the bank number at query time. 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#39334
Steps to reproduce the bug: - Let's consider two storable products P1 and P2 from the same vendor V - P1 and P2 have the routes 'Buy' and 'Make to order' - Create a SO for 1 P1 and 1 P2 and confirm it - A delivery order DO has been created - A PO has been created for V, confirm it - Process the shipment, receive 1 P1 and 0 P2 with no backorder - Process DO with no backorder - Return DO by clicking on 'Return' button Bug: 1 P1 and 1 P2 were suggested to be returned but the movemen
Original PR description
Steps to reproduce the bug: - Let's consider two storable products P1 and P2 from the same vendor V - P1 and P2 have the routes 'Buy' and 'Make to order' - Create a SO for 1 P1 and 1 P2 and confirm it - A delivery order DO has been created - A PO has been created for V, confirm it - Process the shipment, receive 1 P1 and 0 P2 with no backorder - Process DO with no backorder - Return DO by clicking on 'Return' button Bug: 1 P1 and 1 P2 were suggested to be returned but the movement for P2 had been canceled. Closes #39547 opw:2116582 Forward-Port-Of: odoo/odoo#40150 Forward-Port-Of: odoo/odoo#39950
_action_done() creates extra stock move when quantity_done is superior to initial demand. This extra move should be, after confirmation, either merge into the original stock_move, either stay extra but the move lines still linked to the first one should be shared accordingly to the quantity done. Neither those cases are applied in mrp because the extra move has no picking_id field. condition : `if merge_into_self and extra_move.picking_id:` will therefore be false as well as `if
Original PR description
_action_done() creates extra stock move when quantity_done is superior to initial demand. This extra move should be, after confirmation, either merge into the original stock_move, either stay extra but the move lines still linked to the first one should be shared accordingly to the quantity done. Neither those cases are applied in mrp because the extra move has no picking_id field. condition : `if merge_into_self and extra_move.picking_id:` will therefore be false as well as `if not merge_into_self:` To be sure the two extra move management cases are complementary, this Commit keeps only the first condition. 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#40204 Forward-Port-Of: odoo/odoo#39121
Reproduce this bug - Log in as portal user The top right address detail is over the icon. Cause The others fields are using a `span` who have a style who push them right. This commits add the `span` style for the div. Fine-tuning of 9e30276 OPW-2092345 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
Original PR description
Reproduce this bug
- Log in as portal user
The top right address detail is over the icon.
Cause
The others fields are using a `span` who have a style who push them
right.
This commits add the `span` style for the div.
Fine-tuning of 9e30276
OPW-2092345
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#40105There is a constrains preventing writing debit/credit on an already reconciled journal item. However, this constraint isn't aware about monetary fields and then, was raising an error when writing amount like 1.000001 on a debit of 1.0. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40182
Original PR description
There is a constrains preventing writing debit/credit on an already reconciled journal item. However, this constraint isn't aware about monetary fields and then, was raising an error when writing amount like 1.000001 on a debit of 1.0. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40182
In 4d5c3b9fc1c5 the arguments of the MenuEntryDialog widget were altered, and one instantiation of this widget was not adapted, resulting in the last parameter being undefined and causing a crash. This commit adapts that call. Forward-Port-Of: odoo/odoo#40171
Original PR description
In 4d5c3b9fc1c5 the arguments of the MenuEntryDialog widget were altered, and one instantiation of this widget was not adapted, resulting in the last parameter being undefined and causing a crash. This commit adapts that call. Forward-Port-Of: odoo/odoo#40171
- Create a contact - Create a child contact without name Opening POS causes an error as the Name Field is not a string. opw-2121499 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#40203
Original PR description
- Create a contact - Create a child contact without name Opening POS causes an error as the Name Field is not a string. opw-2121499 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#40203
- Create a Sale Order with a product - Confirm and deliver the product, create an invoice. - Cancel that invoice, go back to the SO. - Recreate the invoice, you have 2 of them (one cancelled). - Post the second, and try 'Send and print' and 'Preview'. A traceback is raised. The traceback arises because we sort on the `invoice_date`, which is `False` for a canceled invoice. Actually, we should not take into account canceled invoices. opw-2119870 Description of the issue/featur
Original PR description
- Create a Sale Order with a product - Confirm and deliver the product, create an invoice. - Cancel that invoice, go back to the SO. - Recreate the invoice, you have 2 of them (one cancelled). - Post the second, and try 'Send and print' and 'Preview'. A traceback is raised. The traceback arises because we sort on the `invoice_date`, which is `False` for a canceled invoice. Actually, we should not take into account canceled invoices. opw-2119870 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#40192
Fields `Nome` and `Cognome` cannot be identical. However, Odoo has only a single field for name. Therefore, we split the name based on the assumption that the name is written as 'Name Surname'. opw-2093035 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#40037
Original PR description
Fields `Nome` and `Cognome` cannot be identical. However, Odoo has only a single field for name. Therefore, we split the name based on the assumption that the name is written as 'Name Surname'. opw-2093035 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#40037
this module define a map view. web_map is auto_installed, but this doesn't imply the web_map module being loaded before crm_enterprise. Forward-Port-Of: odoo/enterprise#6690
Original PR description
this module define a map view. web_map is auto_installed, but this doesn't imply the web_map module being loaded before crm_enterprise. Forward-Port-Of: odoo/enterprise#6690
Community FP https://github.com/odoo/odoo/pull/39820
Original PR description
Community FP https://github.com/odoo/odoo/pull/39820
Steps to reproduce the bug: - Go to planning app - Set the gantt view - Create a slot for today with planning template between 8 AM - 2 PM Bug: The hours displayed were not in the right timezone opw:2091602 Forward-Port-Of: odoo/enterprise#6561
Original PR description
Steps to reproduce the bug: - Go to planning app - Set the gantt view - Create a slot for today with planning template between 8 AM - 2 PM Bug: The hours displayed were not in the right timezone opw:2091602 Forward-Port-Of: odoo/enterprise#6561
The `lastRefreshed` field might have the ISO 8601 format, e.g. `2019-11-11T19:56:52Z`. The ORM doesn't understand such a format. opw-2122471 Forward-Port-Of: odoo/enterprise#6687
Original PR description
The `lastRefreshed` field might have the ISO 8601 format, e.g. `2019-11-11T19:56:52Z`. The ORM doesn't understand such a format. opw-2122471 Forward-Port-Of: odoo/enterprise#6687
It was impossible to preview (and maybe send) the mail template named "Digest: Default main template" because the computed method "_compute_kpi_account_total_bank_cash_value" fetch 'amount' field from the account.move model. And the name of this field change into 'amount_total' in the commit bc131c0cfb51c953de8ec41fb820c8c7831eefb5 . Fix by fetching with the correct name. task-2085912 Forward-Port-Of: odoo/enterprise#6648
Original PR description
It was impossible to preview (and maybe send) the mail template named "Digest: Default main template" because the computed method "_compute_kpi_account_total_bank_cash_value" fetch 'amount' field from the account.move model. And the name of this field change into 'amount_total' in the commit bc131c0cfb51c953de8ec41fb820c8c7831eefb5 . Fix by fetching with the correct name. task-2085912 Forward-Port-Of: odoo/enterprise#6648