Monday, December 30, 2024
4 changes · 18.0
Resolved issues and error corrections
This fix ensures copied databases using Indian localization settings are neutralized so they do not contact live government or production services. It helps support teams investigate issues safely without risking real-world effects on customers or production records.
Original PR description
Since [1], the filed `l10n_in_edi_production_env` has been moved from module `l10n_in_edi` to `l10n_in`. `l10n_in_gstin_status` needs to be neutralized to not hit the production servers, but it does…
Since [1], the filed `l10n_in_edi_production_env` has been moved from module `l10n_in_edi` to `l10n_in`. `l10n_in_gstin_status` needs to be neutralized to not hit the production servers, but it does not depend on the `l1on_in_edi` module which holds the neutralization script. Even if the `l10n_in_gstin_status` does not end up performing operation that require a strict neutralization, future modules that also depend solely on `l10n_in` might not be so lucky, rendering this change absolutely necessary. The purpose of the standard neutralization framework is to allow us to create database copies that will not interact with external systems in ways that could impact the production database (or if it is not possible to prevent the interactions, make sure that they are benign or won't result in actual changes), or impact the customers of the operator of the production database. This is mainly useful to allow safe support investigation on database duplicates. [1] https://github.com/odoo/odoo/pull/175290
The HTML editor color picker now correctly shows which text or background color is already applied when users open it. This makes formatting clearer and avoids duplicate or missing custom color entries, reducing confusion while editing content.
Original PR description
**Current behavior before PR:** When there is a text having a text-color or background color, opening color selector doesn't highlight the button matching with that selected color in solid color tab. **Desired behavior before PR is merged:** Opening color selector highlights the button matching with that selected color in solid color tab. task-4341528 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix updates an automated test for the self-ordering point-of-sale feature so it selects the intended product directly. This makes test results more reliable and avoids failures caused by products appearing in a different order.
Original PR description
**Problem**: The product created during the tour test was not explicitly selected. It was selected implicitly because it appeared first in the product list. **Solution**: Explicitly select the product created during the test in the tour to ensure proper functionality and remove dependency on list order. runbot-110904 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Reloading the Colombian DIAN configuration no longer crashes when a required certificate is missing. Instead, users receive a clear validation message so they can add or restore the certificate and continue configuration.
Original PR description
Currently, An error occurs when reloading the DIAN configuration in an account journal to obtain the security token of a certificate, if no certificate is available. Step to produce: - Install the `l10n_co_dian` module. - Navigate to Settings and click on Certificates under the Certificates and Keys section. - And delete a 'Demo DIAN Certificate'. - Open any Journals and click on a 'Reload DIAN configuration'. `IndexError: tuple index out of range` The error occurs because the system attempts to access the certificate's token from a company at [1], but it is not available. Link [1]: https://github.com/odoo/enterprise/blob/a354a19060338084df35a14ed7f21defc3c05c11/l10n_co_dian/xml_utils.py#L123 To resolve this issue, Raise a validation error if a certificate is not found when the system attempts to retrieve its security token. Sentry-6165073693