Saturday, February 8, 2025
7 changes · saas-18.1
Miscellaneous changes
**Problem**: The close icon on the file upload notification is misplaced, appearing at the top-left instead of the expected position on the right. Before fix:  After fix:  **Solution**: Adjust the button's position to appear on the right side of the notification. **Steps to Reproduce**: 1. Open the Edito
Original PR description
**Problem**: The close icon on the file upload notification is misplaced, appearing at the top-left instead of the expected position on the right. Before fix:  After fix:  **Solution**: Adjust the button's position to appear on the right side of the notification. **Steps to Reproduce**: 1. Open the Editor. 2. Upload a file. 3. Observe that the close button appears on the top-left instead of the right. opw-4512322 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#195209
**Problem**: In Safari, relying on the browser to add a space after automatic link creation causes the cursor to be incorrectly positioned. This issue arises due to DOM manipulations (adding and removing nodes) during the process. **Solution**: To ensure proper link insertion and cursor positioning, explicitly add the space after the link and set the selection programmatically. **Steps to Reproduce**: 1. Open the Editor on Safari. 2. Add the text "test.com". 3. Press the space key. 4
Original PR description
**Problem**: In Safari, relying on the browser to add a space after automatic link creation causes the cursor to be incorrectly positioned. This issue arises due to DOM manipulations (adding and removing nodes) during the process. **Solution**: To ensure proper link insertion and cursor positioning, explicitly add the space after the link and set the selection programmatically. **Steps to Reproduce**: 1. Open the Editor on Safari. 2. Add the text "test.com". 3. Press the space key. 4. Observe that the link is created, but the cursor moves to the start of the paragraph. opw-4441817 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#194989
**Problem**: When `u` or `s` tags are applied, changing the `font-size` wraps the text inside these tags instead of applying it to the tags themselves. For example, `a<u>b</u>c` → `a<u><font>b</font></u>c`, which results in an inconsistent appearance. **Solution**: Ensure that the `span` for font size is applied to the highest non-block ancestor to maintain proper styling. **Steps to Reproduce**: 1. Add text. 2. Apply underline. 3. Increase font size. 4. Observe that the underline
Original PR description
**Problem**: When `u` or `s` tags are applied, changing the `font-size` wraps the text inside these tags instead of applying it to the tags themselves. For example, `a<u>b</u>c` → `a<u><font>b</font></u>c`, which results in an inconsistent appearance. **Solution**: Ensure that the `span` for font size is applied to the highest non-block ancestor to maintain proper styling. **Steps to Reproduce**: 1. Add text. 2. Apply underline. 3. Increase font size. 4. Observe that the underline remains the original size instead of scaling with the text. opw-3086072 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#196943
Before this commit: == - Lot-serial dropdown not visible in the small UI. After this commit: == - Displayed the lot-serial dropdown in the small UI. opw-4551161 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#196957
Original PR description
Before this commit: == - Lot-serial dropdown not visible in the small UI. After this commit: == - Displayed the lot-serial dropdown in the small UI. opw-4551161 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#196957
**Steps to reproduce:** Use a Colombian company. Configure DIAN / Carvajal (company, product, and supplier) as per documentation. Change the language to Spanish (LATAM). Create a new Purchase Order using the supplier and the product: - Receive the product. - Create the Vendor Bill: - Change the Journal to the DIAN Support Documents journal and set the date. - Using the actions, print the invoice (even without payment) and look at the document title. [](https://github.com/user-attachments/files/18359586/SEDS_2025_01_0014.pdf) - Create a Credit Note: - Using the actions, print the credit note (even without payment) and look at the document title. [](https://github.com/user-attachments/files/18359584/RSEDS_2025_01_0009.pdf) --- **Issue:** DIAN vendor bills and vendor credit notes display `Factura de proveedor` and `Nota de crédito de proveedor`. --- **Expected:** DIAN vendor bills and vendor credit notes should display `Documento Soporte` and `Nota de Ajuste del Documento Soporte`. --- **Cause:** Vendor bills and credit notes are not managed by Colombian's EDI nor DIAN modules but only by the Account module. --- **Fix:** Add DIAN-specific `Vendor Bill` and `Vendor Credit Note` translations. Manage the title replacement in the generated file if the PDF generation is done by the DIAN module. [](https://github.com/user-attachments/files/18359493/SEDS_2025_01_0013.pdf) [](https://github.com/user-attachments/files/18359499/RSEDS_2025_01_0008.pdf) --- **Task References:** opw-4423439 opw-4433918 Forward-Port-Of: odoo/enterprise#78819 Forward-Port-Of: odoo/enterprise#76793
Forward-Port-Of: odoo/enterprise#78842
Original PR description
Forward-Port-Of: odoo/enterprise#78842
In 18.0, we dropped the support for the round per line rounding method in Mexico. However, we didn't think about the following scenario: - a user creates an invoice in 17.0 in round-per-line mode, and sends it to the Mexican government without problem - they then upgrade to 18.0 - a while later, they receive payment for the invoice. They then try to send the payment CFDI to the Mexican government. The payment CFDI is a complicated beast because it needs to retrieve values from the i
Original PR description
In 18.0, we dropped the support for the round per line rounding method in Mexico. However, we didn't think about the following scenario: - a user creates an invoice in 17.0 in round-per-line mode,…
In 18.0, we dropped the support for the round per line rounding method in Mexico. However, we didn't think about the following scenario: - a user creates an invoice in 17.0 in round-per-line mode, and sends it to the Mexican government without problem - they then upgrade to 18.0 - a while later, they receive payment for the invoice. They then try to send the payment CFDI to the Mexican government. The payment CFDI is a complicated beast because it needs to retrieve values from the invoice the payment was reconciled with. Since the amounts in the invoice are slightly different from what they should be in round globally, the payment CFDI gets incorrectly generated and gets rejected by the Mexican government. So we need a temporary fix that allows the values of the payment CFDI to be adjusted according to the values of the invoice, which works even if the invoice used round per line. This fix is inspired by the existing solution in version 17: https://github.com/odoo/enterprise/pull/68319 and ensures that the "importe" amount is properly calculated. opw-4537931 opw-4536649 opw-4528785 opw-4490806 Forward-Port-Of: odoo/enterprise#78674