Monday, December 26, 2022
9 changes · master
Resolved issues and error corrections
This change fixes an installation failure in the LDAP authentication settings caused by an outdated settings reference. It also renames the related settings section so it is clearer and consistent, reducing confusion for future maintenance.
Original PR description
This is an oversight in odoo/odoo#106425 `<div name="auth_ldap_right_pane">` has been replaced by `<setting ... id="oauth">` But, in the `auth_ldap` module, the view has not been adapted to replace the selector `<div name='auth_ldap_right_pane' position="inside">` Therefore leading to the below exception ``` odoo.tools.convert.ParseError: while parsing /home/odoo/src/odoo/master/addons/auth_ldap/views/res_config_settings_views.xml:3 Error while validating view: Element '<div name="auth_ldap_right_pane">' cannot be located in parent view ``` This is most-likely because the runbot doesn't install `auth_ldap` and therefore doesn't test it. I take the opportunity of the commit to better name this setting section, from `id="oauth"` to `id="module_auth_ldap"`, first because "oauth" is not "ldap", second to make the naming uniform compared to the other setting section id names.
Miscellaneous changes
When you have some order lines linked to a registration that have a 'product_uom_qty' equals to 0, you get a division by 0 error when you try to get the 'sale_price' and the 'sale_price_untaxed'. To avoid such issue, we are now checking if the 'product_uom_qty' is not equals to 0 to avoid a division by 0. In the case it is equal to 0, we consider that the 'sale_price' and 'sale_price_untaxed' are equal to 0 as nothing has been paid for this registration. To reproduce you can do like this:
Original PR description
When you have some order lines linked to a registration that have a 'product_uom_qty' equals to 0, you get a division by 0 error when you try to get the 'sale_price' and the 'sale_price_untaxed'. To avoid such issue, we are now checking if the 'product_uom_qty' is not equals to 0 to avoid a division by 0. In the case it is equal to 0, we consider that the 'sale_price' and 'sale_price_untaxed' are equal to 0 as nothing has been paid for this registration. To reproduce you can do like this: - create invite someone to your event - create a SO with qty 1 and the price - validate the SO and select the registration - set product_uom_qty to 0 in the SO - open the event dashboard (and remove the filter to get your event) 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#108297
Starting from 1 January 2023, the Goods and Services Tax rate (GST) will change and go from 7% to 8% task-3098705 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#107761
Original PR description
Starting from 1 January 2023, the Goods and Services Tax rate (GST) will change and go from 7% to 8% task-3098705 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#107761
Domain widget has Components for every type of field to define list of available operators, initial value, etc. However, class and template for the binary field is missing. This commit adds basic support for the binary fields. More advanced usage can be implemented manually via Code Editor of the domain wdiget. opw-3084273 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the C
Original PR description
Domain widget has Components for every type of field to define list of available operators, initial value, etc. However, class and template for the binary field is missing. This commit adds basic support for the binary fields. More advanced usage can be implemented manually via Code Editor of the domain wdiget. opw-3084273 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#108032
It is important that users are able to filter by invoices that need to be posted to TIMS This commit adds that filter in the account move tree view. task-id: 2950308 Forward-Port-Of: odoo/odoo#107728
Original PR description
It is important that users are able to filter by invoices that need to be posted to TIMS This commit adds that filter in the account move tree view. task-id: 2950308 Forward-Port-Of: odoo/odoo#107728
Purpose ======= Web: ------- Adding a css rule constraint to avoid the rule from overwriting the o_field_highlight css class applied on a field in a form view. Base, auth_totp: ----------------------- Adding the o_field_highlight class on the 2FA form fields to display the input bottom border and thereby more easily identify the fields. Adding a placeholder to the 2FA password field. Modifying the 2FA title and toggle font to keep a consistency between the different page titl
Original PR description
Purpose ======= Web: ------- Adding a css rule constraint to avoid the rule from overwriting the o_field_highlight css class applied on a field in a form view. Base, auth_totp: ----------------------- Adding the o_field_highlight class on the 2FA form fields to display the input bottom border and thereby more easily identify the fields. Adding a placeholder to the 2FA password field. Modifying the 2FA title and toggle font to keep a consistency between the different page titles. Task-3083540 Forward-Port-Of: odoo/odoo#106786
**Steps to reproduce the bug:** - Enable “Multi-Step Routes” option in the inventory settings - Create a storable product “P1” with BoM: - Add any Component - Go to “Miscellaneous” tab - Create a new picking type and set in in the “Operation” tab - Create a Mo: - Add the product “P1” - Select the created BoM - Go to “Miscellaneous” tab **Problem:** The operation type set on BoM does not update when selecting the BoM on a manufacturing order opw-3091436
Original PR description
**Steps to reproduce the bug:**
- Enable “Multi-Step Routes” option in the inventory settings
- Create a storable product “P1” with BoM:
- Add any Component
- Go to “Miscellaneous” tab
- Create a new picking type and set in in the “Operation” tab
- Create a Mo:
- Add the product “P1”
- Select the created BoM
- Go to “Miscellaneous” tab
**Problem:**
The operation type set on BoM does not update when selecting the BoM on a manufacturing order
opw-3091436
Forward-Port-Of: odoo/odoo#108435Confirmed subscriptions can be paid manually via /my/subscription/... Whenever there's a chance of an SO being paid we must recalculate the taxes to ensure they're up-to-date. Otherwise we end up with a payment that won't match the created invoice (which will have the correct, up-to-date taxes). opw-3105697 Forward-Port-Of: odoo/enterprise#35200
Original PR description
Confirmed subscriptions can be paid manually via /my/subscription/... Whenever there's a chance of an SO being paid we must recalculate the taxes to ensure they're up-to-date. Otherwise we end up with a payment that won't match the created invoice (which will have the correct, up-to-date taxes). opw-3105697 Forward-Port-Of: odoo/enterprise#35200
The EU has made some updates to the intrastat commodity codes for 2023. There have been modifications to some descriptions, some codes have been added, and some codes have been deleted. In practice, this means updating the descriptions of existing codes, creating some new codes (and adding new 'start_date' dates for the respective codes from 2023-01-01 onwards), and setting the 'expiry_date' date on the 'deleted' codes (without deleting the code from odoo). task-id: 3107729 Forward-Port-O
Original PR description
The EU has made some updates to the intrastat commodity codes for 2023. There have been modifications to some descriptions, some codes have been added, and some codes have been deleted. In practice, this means updating the descriptions of existing codes, creating some new codes (and adding new 'start_date' dates for the respective codes from 2023-01-01 onwards), and setting the 'expiry_date' date on the 'deleted' codes (without deleting the code from odoo). task-id: 3107729 Forward-Port-Of: odoo/enterprise#35194 Forward-Port-Of: odoo/enterprise#35169