Tuesday, January 9, 2024
13 changes · 17.0
Enhancements to existing features
Point of Sale receipts now include an Odoo marketing line, showing either “Odoo Point of Sale” or “Odoo Restaurant” depending on the setup. This gives Odoo more brand visibility on customer receipts without changing the sales flow.
Original PR description
In this commit we add a line on the receipt with the text "Odoo Point of Sale" or "Odoo Restaurant". ( depending on the case) This is done for marketing reasons. Task: 3635645 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This change updates editor configuration so JavaScript autocompletion works correctly when Odoo is used with the Enterprise code path. It does not change business workflows, but it helps developers work more efficiently and avoid navigation or suggestion issues in their tools.
Original PR description
The jsconfig.json file is used by editors to provide autocompletion but the paths were not updated when it's used in the enterprise path. 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
Features or functions removed from Odoo
The Website app no longer shows the Model Pages menu item in developer mode. This removes an option that was often irrelevant because it could appear even when no model pages existed, making the website management menu cleaner.
Original PR description
On website (with “developer” mode enabled), The “Model Pages” menu item is accessible even when there are no created module page records, which is not relevant in most use cases. The code from [1] introduced a way to expose models (both manual and existing models) publicly on the website by creating pages for them, these records are accessible through the model pages' menu (which is currently visible in debug mode only). A first spec aimed to make this menu item visible only when module pages are created for the current website, But since we need to perform async calls for that (to check if some module page records exist), and after further discussion, it was decided to remove it completely. [1]: https://github.com/odoo/odoo/commit/198e226f5bd66dba6598d1ef85e5fa5fb82b38b2 task-3659626
Miscellaneous changes
### [FIX] point_of_sale: invoice refunds after session closing How to reproduce: - Open a PoS session - Create an order, pay it and validate - In the same session, find the order in `Orders` (filter on Paid) and make a full refund - Close the session - Open a new session and open the "refund" order in Orders - Click the "Invoice" button to invoice this order Observed behavior: - We get a UserError saying the reversal entry is unbalanced, where the credit side equals 0.00 and the cre
Original PR description
### [FIX] point_of_sale: invoice refunds after session closing How to reproduce: - Open a PoS session - Create an order, pay it and validate - In the same session, find the order in `Orders` (filter…
### [FIX] point_of_sale: invoice refunds after session closing How to reproduce: - Open a PoS session - Create an order, pay it and validate - In the same session, find the order in `Orders` (filter on Paid) and make a full refund - Close the session - Open a new session and open the "refund" order in Orders - Click the "Invoice" button to invoice this order Observed behavior: - We get a UserError saying the reversal entry is unbalanced, where the credit side equals 0.00 and the credit note is not generated. Expected behavior: - We are able to generate the credit note correctly. When computing the reversal entry, it seems we inverted the sign of the quantity field of each order line when reversing a refund. However, that did not make sense because the actual amounts are already reversed for a refund. task-3611296 ### [FIX] point_of_sale: multiple taxes duplicated on invoicing We have two taxes on a product, for which the first tax is affecting the base of the second tax. We create a PoS order with that product, pay and validate it and close the session. In a new session, we try to invoice that order. When looking at the reversal entry for that order we can see that the last tax has an additional line, computing it's tax on the first tax as a base amount. Because of that an automatic balacing line is added as well, since the move is not balanced anymore. It turns out that when generating the reversal entry, we go through the `_sync_dynamic_lines` function which is the culprit for computing the second tax again on the first tax. Since we already have all the lines needed from the invoice generated, we can actually skip invoice synchronization and prevent this issue. task-3611296 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#147864 Forward-Port-Of: odoo/odoo#145890
Fixed an issue where users could encounter an error when using the Tab key on vendor bills if analytic plans existed without any analytic accounts. The change safely skips dropdown navigation when there are no options, keeping bill entry uninterrupted.
Original PR description
Issue: - When you have analytic plans but no analytic accounts you got a traceback when you tab through the fields on a vendor bill. Steps to reproduce: - In accounting app create a vendor bill where analytic plans exist without associated analytic accounts. - Use the key 'Tab' to move through the fields on the vendor bill. - Notice Traceback error. Solution: - Checking if the dropdown is not empty before proceeding with the Tab key logic. OPW-3648815 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects Chilean electronic export invoicing so that transport type is no longer required when the service indicator is set to 4. This helps prevent valid export documents from being blocked unnecessarily, reducing manual corrections for affected users.
Original PR description
…rvice indicator is 4
In 16.2, this commit https://github.com/odoo/odoo/commit/b0a6c525b06fabf8cf869890d8383f8304bae697 modified products' domain on a manufacturiong order.. The domain added was not correct as it overrided the domain from stock_move instead of doing the intersection of the two domains. task_id: 3630626 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 guide
Original PR description
In 16.2, this commit https://github.com/odoo/odoo/commit/b0a6c525b06fabf8cf869890d8383f8304bae697 modified products' domain on a manufacturiong order.. The domain added was not correct as it overrided the domain from stock_move instead of doing the intersection of the two domains. task_id: 3630626 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#145521
Before this commit, if a URL was contained in two or more text nodes, e.g. `<p>"link" ".com"</p>`, pressing the space key after the URL failed to convert it into a link. Such text node split can happen as a result of backspace or delete in the middle of a text node. This commit makes sure adjacent text nodes are merged before searching for a URL in its content. task-3468763 Forward-Port-Of: odoo/odoo#148107 Forward-Port-Of: odoo/odoo#147109
Original PR description
Before this commit, if a URL was contained in two or more text nodes, e.g. `<p>"link" ".com"</p>`, pressing the space key after the URL failed to convert it into a link. Such text node split can happen as a result of backspace or delete in the middle of a text node. This commit makes sure adjacent text nodes are merged before searching for a URL in its content. task-3468763 Forward-Port-Of: odoo/odoo#148107 Forward-Port-Of: odoo/odoo#147109
Before this commit, for a barcode rule with the UPC-A encoding, the condition's checking if we should convert an EAN-13 to an UPC-A was always false because the key `upc_ean_conv` was checked on the wrong object (`this` instead of `this.nomenclature`.) task-3472884 Forward-Port-Of: odoo/odoo#146299 Forward-Port-Of: odoo/odoo#142163
Original PR description
Before this commit, for a barcode rule with the UPC-A encoding, the condition's checking if we should convert an EAN-13 to an UPC-A was always false because the key `upc_ean_conv` was checked on the wrong object (`this` instead of `this.nomenclature`.) task-3472884 Forward-Port-Of: odoo/odoo#146299 Forward-Port-Of: odoo/odoo#142163
In 17.0, we implemented the correct balance sheet and profit and loss reports for Belgium [1]. In total we have 6 BS versions and 4 P&L versions. Recently we backported the reports using the micro/abbreviated scheme since the reports in 16.0 were very outdated [2]. However, the micro/abbreviated scheme is missing some lines that were there in the outdated reports in 16.0. That's why we also backport the reports using the full scheme, so all companies can have their reporting as short or e
Original PR description
In 17.0, we implemented the correct balance sheet and profit and loss reports for Belgium [1]. In total we have 6 BS versions and 4 P&L versions. Recently we backported the reports using the micro/abbreviated scheme since the reports in 16.0 were very outdated [2]. However, the micro/abbreviated scheme is missing some lines that were there in the outdated reports in 16.0. That's why we also backport the reports using the full scheme, so all companies can have their reporting as short or extensive as they like. [1] c76133635bc1542765937116f02bbbd390599106 [2] fe5eff73ef7109adac0aaa9b343b774ec23c3e01 [opw-3648224](https://www.odoo.com/web#id=3648224&cids=1&model=project.task&view_type=form) Forward-Port-Of: odoo/enterprise#53907 Forward-Port-Of: odoo/enterprise#53530
This commit fixes a bug where the user had access to the insertion menu inside of an embedded article items view when opened in full screen. This was caused by the quick menu introduced in saas16.3, and more specifically the option to create either a kanban, list or calendar of article items. To fix this we changed the isDisplayed callback for the InsertEmbeddedViewMenu so that it uses the embedded view's ID instead of checking if we have the context key `knowledge_embedded_view_framework`, w
Original PR description
This commit fixes a bug where the user had access to the insertion menu inside of an embedded article items view when opened in full screen. This was caused by the quick menu introduced in saas16.3, and more specifically the option to create either a kanban, list or calendar of article items. To fix this we changed the isDisplayed callback for the InsertEmbeddedViewMenu so that it uses the embedded view's ID instead of checking if we have the context key `knowledge_embedded_view_framework`, which is a more robust way to check the same thing. As the embedded view ID is always a part of the view's context. task-3662991 Forward-Port-Of: odoo/enterprise#53570
Bug === When answering someone tweet, the Twitter API add the users at the beginning of the message, even if we already added them manually (so the API response is different from the create tweet). To fix that issue, we overwrite the API response with the message we just sent (and so with the message that has been created on Twitter). Task-3615860 Forward-Port-Of: odoo/enterprise#53660 Forward-Port-Of: odoo/enterprise#53533
Original PR description
Bug === When answering someone tweet, the Twitter API add the users at the beginning of the message, even if we already added them manually (so the API response is different from the create tweet). To fix that issue, we overwrite the API response with the message we just sent (and so with the message that has been created on Twitter). Task-3615860 Forward-Port-Of: odoo/enterprise#53660 Forward-Port-Of: odoo/enterprise#53533
**Current behavior before PR**: - While canceling/rescheduling the appointment, the text in the chatter is not marked up. - While moving an Article (Which has edit access and 1 child article with read access) from 'Shared' to 'Private', the text in the chatter is not marked up. **Desired behavior after PR is merged**: - The text/image in chatter will always be marked up in all defined cases. **Task**-3458211 Forward-Port-Of: odoo/enterprise#53708 Forward-Port-Of: odoo/enterprise#48380
Original PR description
**Current behavior before PR**: - While canceling/rescheduling the appointment, the text in the chatter is not marked up. - While moving an Article (Which has edit access and 1 child article with read access) from 'Shared' to 'Private', the text in the chatter is not marked up. **Desired behavior after PR is merged**: - The text/image in chatter will always be marked up in all defined cases. **Task**-3458211 Forward-Port-Of: odoo/enterprise#53708 Forward-Port-Of: odoo/enterprise#48380