Friday, December 22, 2023
34 changes · 17.0
Enhancements to existing features
The Indian localization demo data has been reorganized to provide clearer and more useful sample records. Some older examples were removed and replaced with improved demo entries, helping users better understand Indian accounting and e-waybill scenarios during setup or testing.
Original PR description
Before PR: === Demo data of the Indian localization was divided in different modules. After PR: === Reorganization of demo data in the Indian localization modules. Specifically: - Removed demo data entries. - Added new demo data entries for improved examples. Enterprise PR: https://github.com/odoo/enterprise/pull/52104 task id: 3614544
The Indian localization module's demo data has been reorganized and cleaned up. Demo data entries have been removed and consolidated into a new dedicated documents module to streamline the setup process and improve maintainability of the Indian localization features.
Original PR description
Before PR: === Demo data of the Indian localization was divided in different modules. After PR: === Reorganization of demo data in the Indian localization module. Specifically: - Removed demo data entries. Community PR: https://github.com/odoo/odoo/pull/144951 task id: 3614544
Resolved issues and error corrections
This fixes a broken layout in the import module dialog so the form displays correctly. Users benefit from a cleaner, more usable screen when importing modules, with no change to underlying business processes.
Original PR description
Before this commit, the layout of the import module form view (in the dialog) was broken. This was due to unnecessary and wrong use of col/colspan attributes. 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
Code cleanup and technical improvements
This change reorganizes internal test support code for the web module by moving kanban testing helpers into a shared helper file. It does not change product behavior, but makes future JavaScript tests easier to build and maintain.
Original PR description
Before this commit, the helpers for the kanban view are only used in the kanban tests in web module and those helper functions are not exported and so it is impossible to use it outside that file. This commit moves the helper functions for the kanban view in a new file called "helpers.js" in the same directory containing the tests for the kanban views and export all the helper functions to be able to use it anywhere we need to use those helpers in JS tests.
Miscellaneous changes
Each line of the french VAT report should be rounded to the unit. In addition, the tax amounts should be recomputed using the rounded base amounts! The rounding of each line is enabled using the 'integer_rounding' option introduced in https://github.com/odoo/enterprise/commit/1916433a951fb98baf1a54e6b6e0f8a3f59920a4. The recomputation of the tax lines base on the rounded base lines is done using aggregation expression (so the `tax` tags are no longer used in the report). The rounding diff
Original PR description
Each line of the french VAT report should be rounded to the unit. In addition, the tax amounts should be recomputed using the rounded base amounts! The rounding of each line is enabled using the 'integer_rounding' option introduced in https://github.com/odoo/enterprise/commit/1916433a951fb98baf1a54e6b6e0f8a3f59920a4. The recomputation of the tax lines base on the rounded base lines is done using aggregation expression (so the `tax` tags are no longer used in the report). The rounding difference is accounted during the closing entry. task-3607253 Forward-Port-Of: odoo/odoo#145557
Event attendee badges now show the attendee's own company name instead of the event organizer's company. This prevents incorrect company information from appearing on printed or generated badges, improving accuracy for event participants and organizers.
Original PR description
Following the event badge redesign in odoo/odoo@1da6cbc4c, we should display on the attendee's badge (report) the attendee's company name (`company_name`) instead of the event's company (`company_id`) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Calendar filter items in the sidebar and mobile panel now appear in ascending order, making lists easier to scan. Numeric labels are sorted more naturally, while empty-value items remain at the end as before.
Original PR description
Before this commit: Filter items in the sidebar/panel are sorted DESC. Items without value are put at the end of the sorted list (eg : Open Shifts) After this commit: Filter items are sorted ASC. Label that begins with numeric are also sorted correctly. Items without value are stull put at the end of the sorted list. task~3524031
The website page properties dialog now displays its footer buttons in the correct position. This removes a small visual issue that could make the duplicate and delete page actions look out of place.
Original PR description
Steps to reproduce: Go to the website's home page > Site > Properties > The control panel buttons in the footer of the "Page Properties" dialog are not aligned correctly. The "Page Properties" dialog…
Steps to reproduce: Go to the website's home page > Site > Properties > The control panel buttons in the footer of the "Page Properties" dialog are not aligned correctly. The "Page Properties" dialog extends the `FormViewDialog` component and updates its template using `xpath` to add extra buttons on the right side of the footer (to "duplicate" & "delete" the current page). But since [1], a `w-100` class has been added to the default button container (`.o_cp_buttons`) on form view dialogs to get the same result as the "More Options" button on `Calendar > Quick Create` dialogs (the difference here is that the extra button was added inside the default buttons wrapper, while on page properties, the buttons are added next to it). The goal of this commit is to "safely" fix this misalignment issue on stable by simply removing the `w-100` class for the page properties dialog. On master, we will replace the template structure with the following implementation: - Inherit `web.FormViewDialog.ToOne.buttons` instead of the whole `web.FormViewDialog` template. - Add the extra buttons inside the `.o_cp_buttons` > `.o_form_buttons_edit` using `xpath`. - Use this template as `this.viewProps > buttonTemplate` - Pass the `clonePage` & `deletePage` handlers as props to the form controller, where the `buttonTemplate` template will be called. This way, the page properties buttons will have the same structure as on the calendar dialog. [1]: https://github.com/odoo/odoo/commit/7dd6e5d1a55de99a4212abc6f24490e47d9ce5bb task-3642712
Contact phone and mobile details now display in a cleaner, stacked layout when printing purchase requests for contacts with full address information. This prevents contact information from being split awkwardly, making printed documents easier to read.
Original PR description
Phone and mobile numbers are not well displayed on contact widget.. This is because of the display flex that split the column in two if there is too much information. We remove the display flex + flex column as all the children of the element are div, which is a block element, therefore they are already arranged one on top of the other. Steps: - Having a contact X with full address informations (address, name, phone) - With purchase module, you see the bug by printing a RFQ for the contact X opw-3626486
This update removes a flex display setting from the customer statements report to align with recent changes made across the Odoo platform. This ensures consistent formatting and appearance of customer statement reports throughout the system.
Original PR description
Remove flex display in order to be consistent with https://github.com/odoo/odoo/pull/146455 opw-3626486
This update removes a temporary workaround in the marketing automation campaign form that is no longer needed. The underlying issue has been resolved in the core system, allowing us to simplify the code and improve maintainability.
Original PR description
This reverts commit 31dc1d2e9985f739fed52b3c04459ed9068acda5 because the root cause has been fixed in the ORM, see the community version. https://github.com/odoo/odoo/pull/146778
This update resolves a recurring test failure in the Documents Spreadsheet module that was causing infinite loops during testing. The fix improves the reliability of automated tests by using a more appropriate testing method that doesn't interfere with the normal operation of background services. This ensures tests run consistently without disruptions.
Original PR description
Since [1], the `toggleCogMenuSpreadsheet` helper patches the `setTimeout` function. This sometimes leads to infinite recursion when the `multi_tab` service has enough time to initialize: this service make use of `setTimeout` to call the `heartbeat` method repeatedly. Moreover, patching the `setTimeout` method is not a good idea since it makes this method synchronous which totally changes the flow that is tested. This PR fixes this issue by using the `contains` helper instead: this method will wait for the element to be inserted in the DOM and perform the assertion afterwards. fixes runbot-24889 [1]: https://github.com/odoo/enterprise/pull/41851 Forward-Port-Of: odoo/enterprise#53212
Related to https://github.com/odoo/enterprise/pull/52648 we add the analytic distributino to the move vals for the exchange diff move. We also remove the precompute on the fields, manual backport of https://github.com/odoo/odoo/commit/b9047febf3c4d67ce409f9f1dba8a9cc7c7165fe opw-3603668 Forward-Port-Of: odoo/odoo#147221 Forward-Port-Of: odoo/odoo#146549
Original PR description
Related to https://github.com/odoo/enterprise/pull/52648 we add the analytic distributino to the move vals for the exchange diff move. We also remove the precompute on the fields, manual backport of https://github.com/odoo/odoo/commit/b9047febf3c4d67ce409f9f1dba8a9cc7c7165fe opw-3603668 Forward-Port-Of: odoo/odoo#147221 Forward-Port-Of: odoo/odoo#146549
Steps to reproduce: - Install Contacts and Sales. - Activate debug mode and go to contacts. - Create new contact and get the mobile view inside the contact form. - Go under Sales & Purchases and look for sales team. - Try to change it in mobile. The issue is that we were missing the template view for this specific field when on mobile, specifically we didn't had the proper kanban view set for the field. opw-3323976 Forward-Port-Of: odoo/odoo#147262 Forward-Port-Of: odoo/odoo#139586
Original PR description
Steps to reproduce: - Install Contacts and Sales. - Activate debug mode and go to contacts. - Create new contact and get the mobile view inside the contact form. - Go under Sales & Purchases and look for sales team. - Try to change it in mobile. The issue is that we were missing the template view for this specific field when on mobile, specifically we didn't had the proper kanban view set for the field. opw-3323976 Forward-Port-Of: odoo/odoo#147262 Forward-Port-Of: odoo/odoo#139586
The VAT rate is increasing from 20% to 22% from January 1st, 2024. We need to keep both 20% and 22% taxes until the end of 2025 for the phasing-out period. 20% taxes will be inactive for new customers. See also odoo/enterprise#52921 task-3615036 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#147157 Forward-Port-Of: odoo/odoo#145324
Original PR description
The VAT rate is increasing from 20% to 22% from January 1st, 2024. We need to keep both 20% and 22% taxes until the end of 2025 for the phasing-out period. 20% taxes will be inactive for new customers. See also odoo/enterprise#52921 task-3615036 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#147157 Forward-Port-Of: odoo/odoo#145324
Steps to reproduce: - Install Accounting - Activate a payment provider (e.g. Stripe) - Configure payment provider with "Capture Amount Manually" option activated - Invoice Online Payment in Accounting settings - Create an invoice - Go to invoice portal preview - Pay it via "Pay Now" button - Go back to invoice portal preview => The "Pay Now" button is still there (not expected) - Uninstall "account_payment_invoice_online_payment_patch" module - Go back to invoice portal preview
Original PR description
Steps to reproduce: - Install Accounting - Activate a payment provider (e.g. Stripe) - Configure payment provider with "Capture Amount Manually" option activated - Invoice Online Payment in…
Steps to reproduce:
- Install Accounting
- Activate a payment provider (e.g. Stripe)
- Configure payment provider with "Capture Amount Manually" option activated
- Invoice Online Payment in Accounting settings
- Create an invoice
- Go to invoice portal preview
- Pay it via "Pay Now" button
- Go back to invoice portal preview
=> The "Pay Now" button is still there (not expected)
- Uninstall "account_payment_invoice_online_payment_patch" module
- Go back to invoice portal preview
=> The "Pay Now" button does not appear anymore (expected)
Cause:
"account_payment_invoice_online_payment_patch" module has been created to allow to disable invoice online payment without uninstalling "account_payment" module.
However, it overrides 2 different `t-if` conditions:
1)
```
(invoice.amount_residual or not tx_ids) and
invoice.state == 'posted' and
invoice.payment_state in ('not_paid', 'partial') and
invoice.amount_total
```
2)
```
invoice.state == 'posted' and
invoice.payment_state in ('not_paid', 'partial') and
invoice.amount_total and
invoice.move_type == 'out_invoice' and
(pending_manual_txs or not tx_ids or invoice.amount_paid < invoice.amount_total)
```
with the same condition `invoice._has_to_be_paid()` that corresponds to:
```
(self.amount_residual or not transactions) and
self.state == 'posted' and
self.payment_state in ('not_paid', 'partial') and
self.amount_total and
self.move_type == 'out_invoice'
```
One part of the second `t-if` condition is removed by the override:
`(pending_manual_txs or not tx_ids or invoice.amount_paid < invoice.amount_total)`
The second condition is used and is overridden 2 times.
Solution:
Add `(pending_manual_txs or not tx_ids or invoice.amount_paid < invoice.amount_total)`
in the `_has_to_be_paid` method.
opw-3378400
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#147213
Forward-Port-Of: odoo/odoo#146305Before this commit ================ - Portal users were not able to download the return label via the portal because the Access token is not passed. After this commit ================ - Portal users are able to download return labels via the portal. task-3245766 Forward-Port-Of: odoo/odoo#146935 Forward-Port-Of: odoo/odoo#119296
Original PR description
Before this commit ================ - Portal users were not able to download the return label via the portal because the Access token is not passed. After this commit ================ - Portal users are able to download return labels via the portal. task-3245766 Forward-Port-Of: odoo/odoo#146935 Forward-Port-Of: odoo/odoo#119296
Current behaviour: --- When setting a form to fullscreen, it doesn't save. Steps to reproduce: --- 1. Go to eLearning 2. Select a course 3. Add Content, type Web Page 4. Select it, Go to website 5. Drag and Drop a form in the middle 6. Click on Fullscreen 7. Try to send the form 8. An error has occurred, the form has not been sent. Cause of the issue: --- Caused by: https://github.com/odoo/odoo/commit/17c6f6f30bf13bd3c303b28d9a314bd76dd8f4dc When using a form normally, websi
Original PR description
Current behaviour: --- When setting a form to fullscreen, it doesn't save. Steps to reproduce: --- 1. Go to eLearning 2. Select a course 3. Add Content, type Web Page 4. Select it, Go to website 5.…
Current behaviour:
---
When setting a form to fullscreen, it doesn't save.
Steps to reproduce:
---
1. Go to eLearning
2. Select a course
3. Add Content, type Web Page
4. Select it, Go to website
5. Drag and Drop a form in the middle
6. Click on Fullscreen
7. Try to send the form
8. An error has occurred, the form has not been sent.
Cause of the issue:
---
Caused by: https://github.com/odoo/odoo/commit/17c6f6f30bf13bd3c303b28d9a314bd76dd8f4dc
When using a form normally, website_form_signature is added by
add_form_signature in the page, because rendered through XML.
When using a fullscreen form, website_form_signature is not added,
because the page is rendered through JS.
Fix:
---
Calling ir.qweb.field.html in the JS route which calls
value_to_html (in website) which calls add_form_signature
Concerning {'template_options': {}}, without it, when we call
_post_processing_att with the argument options.get('template_options'),
because options are empty, it returns None, and in _post_processing_att
when doing options.get('inherit_branding') we get a traceback.
Since in 16.0, options are not used either in value_to_html
nor _post_processing_att, it is no use to fix their modules.
{'template_options': {}} will be removed in 16.0 and up
opw-3611126
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#144857When the payment reference is set as the customer reference, the warning message of the transaction still show the order reference instead. With this commit, we now ensure the expected reference is shown instead. opw-3461181 Forward-Port-Of: odoo/odoo#147039 Forward-Port-Of: odoo/odoo#146808
Original PR description
When the payment reference is set as the customer reference, the warning message of the transaction still show the order reference instead. With this commit, we now ensure the expected reference is shown instead. opw-3461181 Forward-Port-Of: odoo/odoo#147039 Forward-Port-Of: odoo/odoo#146808
…tive Steps to produce: - Go to project application and create a new task with SO. - Select a customer that has prepaid hours product. - Check that remaining hours on SO is less than 0. - Share that project. - Go to front-end. Issue: The value of 'remaining hours on SO' should be displayed in red if the value is negative Cause: Necessary class was not added to the field Solution: To resolve this issue added decoration-danger when remaining hours so is less th
Original PR description
…tive
Steps to produce:
- Go to project application and create a new task with SO.
- Select a customer that has prepaid hours product.
- Check that remaining hours on SO is less than 0.
- Share that project.
- Go to front-end.
Issue: The value of 'remaining hours on SO' should be displayed in red
if the value is negative
Cause: Necessary class was not added to the field
Solution: To resolve this issue added decoration-danger when remaining
hours so is less than 0.
task-3549489
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#146733
Forward-Port-Of: odoo/odoo#140682Before this commit if invisible elements are in the DOM (e.g. device-visibility restricted) the arrows to move snippets (columns, sections) did show up and behave as if the neighbour elements were visible. This commit hides arrows that would not visually move the snippet, and upon using the move arrow, it also moves the snippet beyond the first visible neighbour. Steps to reproduce as of 16.0: - Drop a "Columns" snippet. - Make the center column hidden on desktop. - Move the first colum
Original PR description
Before this commit if invisible elements are in the DOM (e.g. device-visibility restricted) the arrows to move snippets (columns, sections) did show up and behave as if the neighbour elements were visible. This commit hides arrows that would not visually move the snippet, and upon using the move arrow, it also moves the snippet beyond the first visible neighbour. Steps to reproduce as of 16.0: - Drop a "Columns" snippet. - Make the center column hidden on desktop. - Move the first column to the right. => It did not move and an arrow to move to the left was displayed. Steps to reproduce before 16.0: - Drop three snippets. - Make the second snippet conditionally visible. - Hide it using the eye icon in the "Invisible Elements" list. - Move the first block down. => It did not move and an arrow to move upwards was displayed. task-3584947 Forward-Port-Of: odoo/odoo#146667 Forward-Port-Of: odoo/odoo#145895
In a Manufacturing Order based on a BoM, changing the qty values and then change the scheduled date will reset the qty to the bom ones. This should not be the case. enterprise: https://github.com/odoo/enterprise/pull/51822 opw-3568943 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#145257 Forward-Port-Of: odoo/odoo#143496
Original PR description
In a Manufacturing Order based on a BoM, changing the qty values and then change the scheduled date will reset the qty to the bom ones. This should not be the case. enterprise: https://github.com/odoo/enterprise/pull/51822 opw-3568943 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#145257 Forward-Port-Of: odoo/odoo#143496
Since its introduction with commit [1], the blog post teaser is not translatable as the field was not set as `translate=True` by mistake. It's not possible sadly in stable to add it since the jsonb introduction for translated fields, as `translate=True` behaves as a DB change. Without a module update, it will crash, trying to set jsonb value in a non jsonb field. A best effort is make here to add a tooltip to hint what's going when in translate mode and clicking on this field text. Note t
Original PR description
Since its introduction with commit [1], the blog post teaser is not translatable as the field was not set as `translate=True` by mistake. It's not possible sadly in stable to add it since the jsonb…
Since its introduction with commit [1], the blog post teaser is not translatable as the field was not set as `translate=True` by mistake. It's not possible sadly in stable to add it since the jsonb introduction for translated fields, as `translate=True` behaves as a DB change. Without a module update, it will crash, trying to set jsonb value in a non jsonb field. A best effort is make here to add a tooltip to hint what's going when in translate mode and clicking on this field text. Note that the field is not marked as translatable, but if people click on it, they will see the tooltip. If we face multiple needs, it might be clever to introduce a new property on field declaration allowing the mark a field as "translate forgotten" so that our builder shows this warning out of the box. [1]: https://github.com/odoo/odoo/commit/8cc850f3a54f62072d4df99de612f17494ffb123#diff-ae5c21b812e929930064fb93dc919ef1701fd63bae3d9fb306160d01be5629b3R114-R115 opw-3474638 Forward-Port-Of: odoo/odoo#147223 Forward-Port-Of: odoo/odoo#146931
Current behavior: When you add multiple note in a sale order, only the last one was taken into account in the POS. Now we show all notes on the ProductScreen and on the ReceiptScreen. Steps to reproduce: - Install pos_sale - Create a sale order with a product and 2 notes - Open the POS and load the sale order - Only one note appears under the product - Validate the order - Only one note appears on the receipt under the product opw-3551331 --- I confirm I have signed the CLA and re
Original PR description
Current behavior: When you add multiple note in a sale order, only the last one was taken into account in the POS. Now we show all notes on the ProductScreen and on the ReceiptScreen. Steps to reproduce: - Install pos_sale - Create a sale order with a product and 2 notes - Open the POS and load the sale order - Only one note appears under the product - Validate the order - Only one note appears on the receipt under the product opw-3551331 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#146831 Forward-Port-Of: odoo/odoo#144225
Steps to reproduce the bug: - Create a tracked product “P1” - Go to inventory > overview: - Create a receipts: - select “P1” - qty: 4 units - Set 4 serial numbers and validate - Create a return - Try to validate Problem: A user error is triggered: "Record does not exist or has been deleted." When clicking the validate button, we attempt to update the qty_done in each `move_lines` with the `quantity_reserved` through a for loop iteration. However, when setting the fir
Original PR description
Steps to reproduce the bug: - Create a tracked product “P1” - Go to inventory > overview: - Create a receipts: - select “P1” - qty: 4 units - Set 4 serial numbers and validate - Create a return - Try…
Steps to reproduce the bug:
- Create a tracked product “P1”
- Go to inventory > overview:
- Create a receipts:
- select “P1”
- qty: 4 units
- Set 4 serial numbers and validate
- Create a return
- Try to validate
Problem:
A user error is triggered: "Record does not exist or has been deleted."
When clicking the validate button, we attempt to update the qty_done in each `move_lines` with the `quantity_reserved` through a for loop iteration. However, when setting the first one, we set the "product_uom_qty=1" in the associated move. Since the reserved availability is greater, the move is unreserved, and the other three `move_lines` are deleted:
https://github.com/odoo/odoo/blob/a9a43362df6a6ec031ea14e09ae28115ece62e04/addons/stock/models/stock_move.py#L675-L679
https://github.com/odoo/odoo/blob/56e7bcf0cb88acf3d60420569ab3eea9bdb19bdb/addons/stock/models/stock_move.py#L758
opw-3553042
Forward-Port-Of: odoo/odoo#142760
Forward-Port-Of: odoo/odoo#142657Steps to reproduce: - In Settings/technical/actions/reports: find the invoice report - in advanced: activate "Reload from attachment" - create an invoice with a swiss customer - confirm and print - print the invoice again Issue: There are two pages with the same qr-code opw-3626815 Forward-Port-Of: odoo/odoo#147102
Original PR description
Steps to reproduce: - In Settings/technical/actions/reports: find the invoice report - in advanced: activate "Reload from attachment" - create an invoice with a swiss customer - confirm and print - print the invoice again Issue: There are two pages with the same qr-code opw-3626815 Forward-Port-Of: odoo/odoo#147102
Create a new live-session survey with a multi-choice question of 4 choices. In one of the choices write a word of 20+ characters. Start the live-session, on the manager side the choices overlap on the screen. In case a word is longer that the available place, it can overlap on the labels of the other columns, making the text very hard to read. This work wraps words that are too long for a single line over multiple ones. Task-3530706 Forward-Port-Of: odoo/odoo#139520
Original PR description
Create a new live-session survey with a multi-choice question of 4 choices. In one of the choices write a word of 20+ characters. Start the live-session, on the manager side the choices overlap on the screen. In case a word is longer that the available place, it can overlap on the labels of the other columns, making the text very hard to read. This work wraps words that are too long for a single line over multiple ones. Task-3530706 Forward-Port-Of: odoo/odoo#139520
Issue: ------ Depending on the order of installation, we may end up with actions that have a `0` at the end. For example, for the calendar module, if the value of `quick_create` is `390`, we will have `hasQuickCreate` which is `false`. ```js hasQuickCreate = archParseBoolean(node.getAttribute("quick_add"), true); ``` Solution: --------- Correct the regex to detect a `false` or a `0` on the entire character string. opw-3488262 Forward-Port-Of: odoo/odoo#147206 Forward-Port-Of:
Original PR description
Issue:
------
Depending on the order of installation, we may end up with actions that have a `0` at the end.
For example, for the calendar module, if the value of `quick_create` is `390`, we will have `hasQuickCreate` which is `false`.
```js
hasQuickCreate = archParseBoolean(node.getAttribute("quick_add"), true);
```
Solution:
---------
Correct the regex to detect a `false` or a `0`
on the entire character string.
opw-3488262
Forward-Port-Of: odoo/odoo#147206
Forward-Port-Of: odoo/odoo#147065[FIX] website_event_booth: make images of booth categories accessible by public user Currently, categories' images can only be seen while logged in. This fix will allow public user to have access to images. Description of the issue/feature this PR addresses: add access rights for booth category for public user Current behavior before PR: images of booths' are not loading if not logged in Desired behavior after PR is merged: images of booths' are loading regardless of the user opw-3625
Original PR description
[FIX] website_event_booth: make images of booth categories accessible by public user Currently, categories' images can only be seen while logged in. This fix will allow public user to have access to images. Description of the issue/feature this PR addresses: add access rights for booth category for public user Current behavior before PR: images of booths' are not loading if not logged in Desired behavior after PR is merged: images of booths' are loading regardless of the user opw-3625773 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#146916
In list views with search panel, in case there are no records found, the nocontenthelp is being cut off, because the o_list_renderer doesn't take the full height. This commit sets the height on the div, so there is no cut off happening. Part of: task-3619987 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#144809
Original PR description
In list views with search panel, in case there are no records found, the nocontenthelp is being cut off, because the o_list_renderer doesn't take the full height. This commit sets the height on the div, so there is no cut off happening. Part of: task-3619987 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#144809
Task latam: 1137 Task Adhoc: 33333 Prevent delete document number if invoice date is assigned (manual documents). Description of the issue/feature this PR addresses: On a draft vendor bill (manual documents) if the document number setted, and then if the user set a date, the document number is automatically cleaned and it`s must not be cleaned. Current behavior before PR: On a draft vendor bill if the document number setted, and then if the user set a date, the document number is autom
Original PR description
Task latam: 1137 Task Adhoc: 33333 Prevent delete document number if invoice date is assigned (manual documents). Description of the issue/feature this PR addresses: On a draft vendor bill (manual documents) if the document number setted, and then if the user set a date, the document number is automatically cleaned and it`s must not be cleaned. Current behavior before PR: On a draft vendor bill if the document number setted, and then if the user set a date, the document number is automatically cleaned. Desired behavior after PR is merged: On a draft vendor bill if the document number setted, and then if the user set a date, the document number is not automatically cleaned. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#142522
**steps to reproduce:** - install the module auth_totp_mail_enforce - open settings - activate "Two-factor authentification enforcing policy" to "Employees only" (or "All users") and save - try to (re)connect with a user (demo/demo or admin/admin) **before this commit:** - internal server error **after this commit:** - error is passed to the user, allowing him (or the admin) to debug without contacting odoo support opw-3624816 --- I confirm I have signed the CLA and read the
Original PR description
**steps to reproduce:** - install the module auth_totp_mail_enforce - open settings - activate "Two-factor authentification enforcing policy" to "Employees only" (or "All users") and save - try to (re)connect with a user (demo/demo or admin/admin) **before this commit:** - internal server error **after this commit:** - error is passed to the user, allowing him (or the admin) to debug without contacting odoo support opw-3624816 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#147090
Fix a small issue with the trusted account lock system, where we would raise an error when you change the partner or account number on a record at the same time as you untrust it. Before this fix it would be blocked, and you would need to untrust, save, and then redo the change in a second edition for it to work. At the same time, we will allow the process to untrust an account and change values at the same time. Task id #3647635 --- I confirm I have signed the CLA and read the PR g
Original PR description
Fix a small issue with the trusted account lock system, where we would raise an error when you change the partner or account number on a record at the same time as you untrust it. Before this fix it would be blocked, and you would need to untrust, save, and then redo the change in a second edition for it to work. At the same time, we will allow the process to untrust an account and change values at the same time. Task id #3647635 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#147055
Description of the issue/feature this commit addresses: On the first of Janurary 2024, Indonesia will use 16 digits VAT numbers in addition to 15 digits ones. This commit makes it possible to use any of these two possibilites when entering the VAT number on an indonesian company. --- Desired behavior after this commit is merged: This commit makes it possible to enter either a 15 or 16 digit VAT Number on an Indonesian company. --- task-3636748 --- I confirm I have signe
Original PR description
Description of the issue/feature this commit addresses: On the first of Janurary 2024, Indonesia will use 16 digits VAT numbers in addition to 15 digits ones. This commit makes it possible to use any of these two possibilites when entering the VAT number on an indonesian company. --- Desired behavior after this commit is merged: This commit makes it possible to enter either a 15 or 16 digit VAT Number on an Indonesian company. --- task-3636748 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#147066 Forward-Port-Of: odoo/odoo#146111