Daily updates from Odoo
Navigate
Branch
Thursday, June 1, 2023
17 changes
New functionality added to Odoo
Manufacturing orders can now be processed directly in the barcode app, making shop floor production workflows faster and more consistent with warehouse picking flows. The update also improves validation messages, backorder navigation, scrolling, and button layout for a smoother barcode experience.
Original PR description
This commit adds the abiltiy to process MOs from the barcode app Community PR: odoo/odoo#114708 TaskId: 3052744
Enhancements to existing features
Indian payroll has been updated with revised salary categories and rules, including new allowance and bonus items. This helps payroll calculations better reflect current compensation structures by removing outdated items and adjusting key deductions, allowances, and net pay rules.
Original PR description
In this commit did the following changes:
- Removed following hr salary rule category:
- Base Salary
- Daily Salary
- New add following hr salary rule category:
- Leave Travel Allowance
- Performance Bonus
- Standard Allowance
- New add following hr salary rule:
- Leave Allowance
- Bonus
- Performance Bonus
- Modify following hr salary rule:
- House Rent Allowance
- BASIC
- Standard Deduction
- Leave Travel Allowance
- Professional Tax
- NET
- Supplementary Allowance
- Removed following hr salary rule:
- Base Salary
- Daily Salary
- Variable pay
task-3251621Resolved issues and error corrections
Renaming an embedded view in Knowledge now immediately shows the new name without requiring a page reload. This removes a small but visible usability issue caused by a previous breadcrumb change.
Original PR description
Purpose: -------- Commit [1] refactored the breadcrumbs. Since then, renaming an embedded view did not show the new name until the view was reloaded (because the active element has not the same class as before). This commit uses the new class of the active element to update the name of the embedded view. [1]: https://github.com/odoo/odoo/commit/caef16ee4e5351142ef04f02798999ccb38a56bc Task-3329989
Code cleanup and technical improvements
Planning and planning report search options now use a shared base setup, so users see consistent filters and grouping choices in both places. This reduces duplicate configuration across related apps and makes future updates easier to maintain.
Original PR description
Planning and planning report search views should be identical. Before this commit in-order to make both view same we add same content (filter,group_by..) twice which was making it hard to keep track as lots of search content comming from other bridge application and we have redundant code. So this commit make a base search view which contains all content of search view and use it in both planning and planning report search views. task-3117332
Miscellaneous changes
When you want display a document on which you are the owner, but the attachment is linked to a model you cannot read. You get an access right error. To avoid this issue, we are using the model 'documents.document' the get the access rights through the field attachment_id of this model. Example: A payslip is generated for you. To get it in your documents a documents.document is created with the generated payslip and you are set as owner of the document. Then you go in your doc
Original PR description
When you want display a document on which you are the owner, but the attachment is linked to a model you cannot read. You get an access right error. To avoid this issue, we are using the model…
When you want display a document on which you are the owner, but the attachment is linked to a model you cannot read. You get an access right error. To avoid this issue, we are using the model 'documents.document' the get the access rights through the field attachment_id of this model. Example: A payslip is generated for you. To get it in your documents a documents.document is created with the generated payslip and you are set as owner of the document. Then you go in your document and click on the payslip to display it, and the pdf viewer tries to display the payslip through the route '/web/content' with the attachment id as parameter. Since you try to read an attachment, a check is made on the access rights of it, and those rights are based on the 'res_model' and 'res_id'. As you don't have read access to the hr.payslip object, you get an error. By giving the model 'documents.document' and the id of the document to the route '/web/content', you use the document on which you have read access and so you can read the field attachment_id of this document. Forward-Port-Of: odoo/enterprise#41775
Go to Documents, switch to list view, select a record, try to edit one of its field in the inspector. Before this commit, the change wasn't applied. This was due to the presence of the attribute edit="0" in the arch, which disallows the edition since commit [1], as this attribute now is correctly used in the model to mark all fields as readonly, and thus prevent them from being edited. [1] https://github.com/odoo/odoo/commit/81dda7340fcc88f4d6c1186abf0bcbe5fa4d49dc opw 3325877 Forward-Por
Original PR description
Go to Documents, switch to list view, select a record, try to edit one of its field in the inspector. Before this commit, the change wasn't applied. This was due to the presence of the attribute edit="0" in the arch, which disallows the edition since commit [1], as this attribute now is correctly used in the model to mark all fields as readonly, and thus prevent them from being edited. [1] https://github.com/odoo/odoo/commit/81dda7340fcc88f4d6c1186abf0bcbe5fa4d49dc opw 3325877 Forward-Port-Of: odoo/enterprise#41767
Before this commit: Goto the 'online appointments' tab in the 'Calendar' module. We choose from the available appointments and then click on the 'SHARE' button to open the 'appointment_invite_view_form'. We can observe, the label 'Link URL', as it appears inline with the field. After this commit: The actual field for link URL is shifted to a new line, below its label. task-3263502 Forward-Port-Of: odoo/enterprise#41753 Forward-Port-Of: odoo/enterprise#40602
Original PR description
Before this commit: Goto the 'online appointments' tab in the 'Calendar' module. We choose from the available appointments and then click on the 'SHARE' button to open the 'appointment_invite_view_form'. We can observe, the label 'Link URL', as it appears inline with the field. After this commit: The actual field for link URL is shifted to a new line, below its label. task-3263502 Forward-Port-Of: odoo/enterprise#41753 Forward-Port-Of: odoo/enterprise#40602
Purpose: - Currently, the embedded item views (list and kanban) show the "New" button if the user does not have write permission on the active article. Clicking on this button in that case results in an access error, since the user tries to add a child to the current article, which he is not allowed to do. This commit hides the "New" button for these item views when the user does not have write permission on the current active article, to prevent triggering these access errors. Task-329205
Original PR description
Purpose: - Currently, the embedded item views (list and kanban) show the "New" button if the user does not have write permission on the active article. Clicking on this button in that case results in an access error, since the user tries to add a child to the current article, which he is not allowed to do. This commit hides the "New" button for these item views when the user does not have write permission on the current active article, to prevent triggering these access errors. Task-3292052 Forward-Port-Of: odoo/enterprise#41699 Forward-Port-Of: odoo/enterprise#40432
*: documents, knowledge, mrp_workorder_hr, planning, social, social_push_notifications, spreadsheet_edition, voip Since the Milk refactoring, the backend uses only `.rounded` avatar images. The `.rounded-circle` classes on images have been replaced by `.rounded`. Community PR: https://github.com/odoo/odoo/pull/122283 task-3336569 part of task-3326263 Forward-Port-Of: odoo/enterprise#41406
Original PR description
*: documents, knowledge, mrp_workorder_hr, planning, social, social_push_notifications, spreadsheet_edition, voip Since the Milk refactoring, the backend uses only `.rounded` avatar images. The `.rounded-circle` classes on images have been replaced by `.rounded`. Community PR: https://github.com/odoo/odoo/pull/122283 task-3336569 part of task-3326263 Forward-Port-Of: odoo/enterprise#41406
Currently, the mobile users can not see or reveal the buttons of the sidebar for creating new articles or for joining a hidden article. The user needs to hover those elements with a mouse pointer to reveal them. In order to ensure that mobile users can interact with those buttons, this PR will ensure that they will remain visible when the user does not have a mouse pointer. The button for joining a hidden article has different styling compared to the button right next to it. This PR wil
Original PR description
Currently, the mobile users can not see or reveal the buttons of the sidebar for creating new articles or for joining a hidden article. The user needs to hover those elements with a mouse pointer to reveal them. In order to ensure that mobile users can interact with those buttons, this PR will ensure that they will remain visible when the user does not have a mouse pointer. The button for joining a hidden article has different styling compared to the button right next to it. This PR will update the styling of that button to ensure visual consistency. task-3297985 Forward-Port-Of: odoo/enterprise#41718 Forward-Port-Of: odoo/enterprise#40614
When reversing an account.move of type 'entry' containing taxes, the same repartition must be used as on the original move, so that everything is cancelled in the tax report (unlike invoices, which will switch to the refund repartition). This test was instead checking the result in the tax report corresponded to the refund repartition ... Though the test was only passing by chance, because of the bugs solved in https://github.com/odoo/odoo/pull/121605. The repartition that was used actually was
Original PR description
When reversing an account.move of type 'entry' containing taxes, the same repartition must be used as on the original move, so that everything is cancelled in the tax report (unlike invoices, which will switch to the refund repartition). This test was instead checking the result in the tax report corresponded to the refund repartition ... Though the test was only passing by chance, because of the bugs solved in https://github.com/odoo/odoo/pull/121605. The repartition that was used actually was the invoice repartition, not the refund one, but the wrong values computed for tax_tag_invert caused the reverse to still appear in positive in the report. The confusion came from the fact the refund repartition impacts the same tags as the invoice one on the test tax used here, with the same signs. Forward-Port-Of: odoo/enterprise#41664 Forward-Port-Of: odoo/enterprise#41162
Issue: When website_sale_renting_comparison module is installed then t-if is replaced so comparison price appeared. Steps: - Installed website_sale_renting_comparison. - Activated Product Comparison Tool - Got To shop - Select the Customizable Desk Product - Click on compare button - Check the compare task-3245649 Forward-Port-Of: odoo/enterprise#39690
Original PR description
Issue:
When website_sale_renting_comparison module is installed then t-if is replaced so comparison
price appeared.
Steps:
- Installed website_sale_renting_comparison.
- Activated Product Comparison Tool
- Got To shop
- Select the Customizable Desk Product
- Click on compare button
- Check the compare
task-3245649
Forward-Port-Of: odoo/enterprise#39690Enterprise part of odoo/odoo#122042 Forward-Port-Of: odoo/enterprise#41602 Forward-Port-Of: odoo/enterprise#41329
Original PR description
Enterprise part of odoo/odoo#122042 Forward-Port-Of: odoo/enterprise#41602 Forward-Port-Of: odoo/enterprise#41329
Since [1] when the `description` field of the `website.twitter.wall` was converted into an HTML field, editing the description of a twitter wall in the `/twitter_walls` page produces an error. On that page, the description field is within an `<h5>` tag, but upon edit, text HTML fields are wrapped inside a `<p>`. The `lxml` `HTMLParser` transforms the received DOM structure: ```xml <h5 ...> <p>Edited value</p> </h5> ``` which becomes: ```xml <div> <h5 .../> <p>Edited value<
Original PR description
Since [1] when the `description` field of the `website.twitter.wall` was converted into an HTML field, editing the description of a twitter wall in the `/twitter_walls` page produces an error.
On that page, the description field is within an `<h5>` tag, but upon edit, text HTML fields are wrapped inside a `<p>`. The `lxml` `HTMLParser` transforms the received DOM structure:
```xml
<h5 ...>
<p>Edited value</p>
</h5>
```
which becomes:
```xml
<div>
<h5 .../>
<p>Edited value</p>
</div>
```
But to perform the save, `ir.ui.view`'s `save` looks at the `data-oe-*` attributes on the saved root element.
This commit converts the `<h5>` to a `<div class="h5">` to avoid the problem.
It also removes the `title` attribute which now contained HTML content.
[1]: https://github.com/odoo/enterprise/commit/776fa2f3bf5cce4e8a6e643440645f08d17278da
task-3289945
Forward-Port-Of: odoo/enterprise#41729This commit fixes a bug where in readonly mode when clicking on the div containing the button to publish an article on the frontend this would cause the application to crash because the user cannot change the published state of an article if he cannot edit it. Now we are using a custom function patched to the PermissionPanel Component that checks if the user can write before trying to publish the article, leading to no more crashes. task-3208630 Forward-Port-Of: odoo/enterprise#41545
Original PR description
This commit fixes a bug where in readonly mode when clicking on the div containing the button to publish an article on the frontend this would cause the application to crash because the user cannot change the published state of an article if he cannot edit it. Now we are using a custom function patched to the PermissionPanel Component that checks if the user can write before trying to publish the article, leading to no more crashes. task-3208630 Forward-Port-Of: odoo/enterprise#41545 Forward-Port-Of: odoo/enterprise#37577
To reproduce the bug this commit fixes do the following: 1) Create a bom with 2 operations. 2) Create a quality point for each operation. 3) Create an MO based on the bom with quantity to produce 2. 4) For the first workorder, set quantity producing to 2 and pass the check, mark done 5) For the second workorder, set the quantity producing to 1 and pass the check, mark done 6) Go back to the MO, quantity to produce should be 1 / 2, click produce. 7) A backorder pop up appears, create
Original PR description
To reproduce the bug this commit fixes do the following: 1) Create a bom with 2 operations. 2) Create a quality point for each operation. 3) Create an MO based on the bom with quantity to produce 2.…
To reproduce the bug this commit fixes do the following: 1) Create a bom with 2 operations. 2) Create a quality point for each operation. 3) Create an MO based on the bom with quantity to produce 2. 4) For the first workorder, set quantity producing to 2 and pass the check, mark done 5) For the second workorder, set the quantity producing to 1 and pass the check, mark done 6) Go back to the MO, quantity to produce should be 1 / 2, click produce. 7) A backorder pop up appears, create backorder. 8) The fully finished workorder should appear cancelled in the backorder. 9) Process the second workorder and pass the check. 10) Go back to backorder and click produce, a UserError shows up asking to process all checks Expected: Should be able to produce the backorder since the workorder was already processed and marked as cancelled Explanation: The bug was that there were hidden quality checks created for the cancelled workorder when the backorder workorders were confirmed. taskId: 3292221 Forward-Port-Of: odoo/enterprise#41675 Forward-Port-Of: odoo/enterprise#41418
The case where we want to add an accessory product that can be rented on the ecommerce on the '/shop/cart' page is not managed. When we are on the '/shop/cart' page, the "Add to cart" button will be displayed if the product that triggered the proposal of this accessory product is present in a line of the sale order. Moreover, it is important to verify that this line contains the time period. If we can add the rentable accessory product to the cart, we will apply the same time period
Original PR description
The case where we want to add an accessory product that can be rented on the ecommerce on the '/shop/cart' page is not managed. When we are on the '/shop/cart' page, the "Add to cart" button will be displayed if the product that triggered the proposal of this accessory product is present in a line of the sale order. Moreover, it is important to verify that this line contains the time period. If we can add the rentable accessory product to the cart, we will apply the same time period as the product that triggered this accessory product. opw-3247134 Forward-Port-Of: odoo/enterprise#41381 Forward-Port-Of: odoo/enterprise#39451