Daily updates from Odoo
Tuesday, December 10, 2024
19 changes
1 change
Resolved issues and error corrections
Point of Sale receipts now show the company name again, matching behavior from previous versions. This helps customers and staff clearly identify the business on printed or digital receipts.
Original PR description
**Steps to reproduce:** - Make a POS order - Process to payment - Check receipt **Issue:** The company name is not displayed on the receipt as it was in previous versions. opw-4349203 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
14 changes
Resolved issues and error corrections
Timesheets now avoid selecting projects that cannot be used for timesheet entries as the default, reducing confusion and incorrect entry setup. The change also adds supporting model data to make future timesheet testing easier and more reliable.
Original PR description
This commit's purpose is to add some data model in order to ease the writing of hoot tests. These data are introduced due to a necessity in the enterprise part of the pr. https://github.com/odoo/enterprise/pull/74264 task 4268687
Customers and staff can now download invoices for point-of-sale orders paid online. The fix ensures the invoice can be accessed even when only its reference is available, reducing failed invoice downloads after online payment.
Original PR description
Before this commit, it wasn't possible to download the invoice of an order paid with online payment. This was because the account move of the order was not loaded, even though it could have its ID, which is sufficient. opw-4357927 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes an automated purchase product matrix walkthrough by removing outdated jQuery usage. It helps keep internal testing reliable so future purchase product matrix changes can be validated with fewer false failures.
Original PR description
In this commit we fix tour by removing the usage of jQuery. 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
This fix ensures users can still find and select records in dropdown fields even when a model has no configured display name search. It avoids unintentionally narrowing results while keeping the existing warning for administrators or developers.
Original PR description
We already display a warning message, but we need to explicitely not restrict the search. The `name_search` method is called when trying to populate many2one fields and we want to be able to select items even when name searching is not defined. task-3484032 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Closing the tour recorder now clears its active state, so it no longer appears to keep recording when users return later. This prevents confusion and makes the tour recording tool behave more predictably.
Original PR description
When closing the tour recorder, the state should be clear. Because if not, when leaving and coming back later, the tour recorder would be still recording. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update prevents Korean localization accounting report codes from overlapping with codes used elsewhere in Odoo. It helps avoid test failures and reduces the risk of reporting setup conflicts for Korean accounting features.
Original PR description
Some code used in accounting report lines are also used in other reports outside of the KR localization. As of now, unlike what the constrains hint, codes are not expected to be unique per report but instead unique entirely which was not the case. The Unallocated Earnings lines had the same code as the standard ones which ended up causing some tests to fail. To fix this, we are adding a prefix to all codes. The constrains was also temporarily changed to ensure that the new codes are at least unique in the KR module and do not clash with account_reports. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix makes an automated stock picking batch test more precise by clearly identifying when actions happen inside pop-up windows. It helps prevent false test failures and improves confidence in future updates to batch transfer workflows.
Original PR description
In the test_stock_picking_batch_sm_to_sml_synchronization tour, it is imperative to be exhaustive about whether we are in a modal or not. The trigger targets an element that is not in a modal when it should be. In this commit, we stipulate each modal for each trigger. This not only makes the tour more understandable but also avoids any ambiguity. runbot-error-id~109487 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
The Update DGI Status button is now hidden when a Uruguayan electronic invoice has already been accepted or rejected by DGI. This prevents users from trying to refresh a status that can no longer change, reducing confusion on completed documents.
Original PR description
This PR hides the “Update DGI Status” button on the account.move form view when the CFE Status is either “CFE Accepted by DGI” or “CFE Rejected by DGI”. This change is necessary because both “Accepted” and “Rejected” are final states that cannot transition to another status. Once a CFE reaches either of these states, there is no status update possible, making the button irrelevant in these scenarios. Task Adhoc side: 43467 Task Latam side: 1295
This fix prevents Spanish invoice records from being incorrectly marked as manually modified when their invoice type is adjusted during creation. It helps keep invoice status information accurate and avoids unnecessary follow-up or confusion for accounting teams.
Original PR description
this fix adds skip_is_manually_modified context to the moves in spanish localization create method, so that is_manually_modified field is not unnecessarily changed to true when changing the invoice type. [link to runbot build errors](https://runbot.odoo.com/web#id=99362&menu_id=424&cids=1&action=573&model=runbot.build.error&view_type=form)
Korean accounting report line codes were updated to avoid overlaps with other reports. This prevents related report tests from failing and helps ensure the Korean localization remains reliable.
Original PR description
Some code used in accounting report lines are also used in other reports outside of the KR localization. As of now, unlike what the constrains hint, codes are not expected to be unique per report but instead unique entirely which was not the case. The Unallocated Earnings lines had the same code as the standard ones which ended up causing some tests to fail. To fix this, we are adding a prefix to all codes. The constrains was also temporarily changed to ensure that the new codes are at least unique in the KR module and do not clash with account_reports.
**Issue:** Some terms don't appear in Spanish in DIAN invoice PDF files.  **Expected:** These terms should be translated in Spanish. **Steps to reproduce:** - Activate Accounting app in a Colombian database; - Configure the DIAN credentials, client, journal and product (https://www.odoo.com/documentation/18.0/applications/finance/fiscal_localizations/colombia.html?highlight=dian); - Create a cust
Original PR description
**Issue:** Some terms don't appear in Spanish in DIAN invoice PDF files.  **Expected:** These terms should be…
**Issue:** Some terms don't appear in Spanish in DIAN invoice PDF files.  **Expected:** These terms should be translated in Spanish. **Steps to reproduce:** - Activate Accounting app in a Colombian database; - Configure the DIAN credentials, client, journal and product (https://www.odoo.com/documentation/18.0/applications/finance/fiscal_localizations/colombia.html?highlight=dian); - Create a customer invoice; - Send and print with (only) DIAN checkbox checked; - Open the PDF for the invoice. **Cause:** No translations (or erroneous ones) have been found for these keys. **Fix:** Add Spanish translations for these terms. <img width="642" alt="Capture d’écran 2024-12-09 à 11 52 44" src="https://github.com/user-attachments/assets/77f548f4-f87e-4823-9fdc-5b54d0db2a1f"> **Testing:** Testing needs actual credentials and complete configuration (including setting the client's language to LATAM Spanish)  opw-4343184
Project kanban cards now show the budget progress symbol again. This helps users quickly see budget status directly from the project overview without opening each project.
Original PR description
Because of a missing field, the budget symbol to indicate the progress of the budget of a project was not displaying on its kanban card. This commit adds the missing field. Task-4353196
Portal users can now see the Document link on a shared project task when a related document has been shared with them. This makes shared task documents easier to access and avoids confusion when no other task links are present.
Original PR description
- 18.0 ### Steps to reproduce: - Install document and project. - Create a portal user. - Create the project and the task. - Upload the document in the task. - Share the document with the portal user. - Share the project with read access to the portal user. - Login with the portal user. - Open the shared project and created task. ### Issue: 'Document' is missing from the left sidebar, even after sharing with portal user ### Cause: 'Document' is in the link section of the sidebar. It will be visible when any task link is shared, eg, invoice, sale order, and helpdesk ticket. So, when there is only a document shared it doesn't display. ### Solution: Display the 'Document' when the document is shared with the portal user. task-4194318
Deleting a project now also archives its related document folder when no remaining projects use that folder. This keeps Documents cleaner by preventing unused project folders from lingering after their projects are removed.
Original PR description
Purpose ======= When deleting a project, its documents are archived but not the documents folder. Fixing that by archiving the folder if every projects it is related to has been deleted. Specification ============= As a folder is created for every new project, it seems logical to archive the folder if the project is deleted. This prevents having "flying" folders, i.e. empty project folders not being linked to any project. Technical: - As the same folder can be linked to multiple projects, only archiving the folder if every projects it is related to has been deleted. - Using sudo(False) because documents access rules can be slow. Task-4262380
4 changes
Resolved issues and error corrections
This update resolves a warning message appearing in payment receipts for Mexican invoices. The fix addresses an issue with how PyPDF2 handles XML data, preventing errors during CFDI generation. This ensures payment receipts are consistently produced without technical disruptions.
Original PR description
**Steps to reproduce:** - Make sure that PyPDF2 is in version 1.26.0 - Install l10n_mx_edi - Switch to a Mexican company - Create an invoice: * Customer: [a Mexican customer] * Payment Way:…
**Steps to reproduce:**
- Make sure that PyPDF2 is in version 1.26.0
- Install l10n_mx_edi
- Switch to a Mexican company
- Create an invoice:
* Customer: [a Mexican customer]
* Payment Way: [Effectivo]
* An invoice line with a product having a UNSPSC Category
- Confirm the invoice
- Generate CFDI via "Send & Print" button
- Register a payment with "Efectivo" Payment Way
- Update Payments on the invoice
- Go to the payment
- Force CFDI
- Make sure the CFDI status of the payment is "Signed"
- Print "Payment Receipt"
**Issue:**
PyPDF2 raises a traceback:
"IndexError: list index out of range".
**Cause:**
PyPDF2 is executing this code to format a warning: file = filename.replace("/", "\\").rsplit("\\", 1)[1] where filename is something liked "<xxx>" (coming from the qweb compilation). Therefore, there is no index 1.
The warning is coming from lxml and is due to the fact that we are evaluating a xml value as it is in a qweb template:
"FutureWarning: Use specific 'len(elem)' or 'elem is not None' test instead." And since this commit:
https://github.com/odoo/odoo/commit/fd67b56fc695526d09706d2b6218519ea255fc30 Python's "warning.py" is overridden in PyPDF2.
**Solution:**
Use "len(cfdi['cfdi_node'])" as advised to check if the xml node has children in the payment receipt template.
opw-4359466
opw-4366016This update resolves intermittent errors that prevented the documents access rights tour from completing successfully. The fix involves adding a check to ensure the page correctly transitions between companies before the tour finishes, improving the user experience and reliability of this onboarding feature. The issue was identified through automated testing and addressed with a targeted code change.
Original PR description
backport of pr-s [68962](https://github.com/odoo/enterprise/pull/68962) and [68770](https://github.com/odoo/enterprise/pull/68770). broken runbot builds are [here](https://runbot.odoo.com/web#id=60274&menu_id=424&cids=1&action=573&model=runbot.build.error&view_type=form) Added an extra trigger, that will check that the page has properly changed from one company to another, and to let this page to load before finishing the tour.
This update fixes a visual issue in the mobile and form views of Odoo where long checkbox labels would overlap with the checkboxes themselves. Now, checkbox labels and checkboxes are properly aligned, ensuring a cleaner and more user-friendly experience. This improves readability and usability for users.
Original PR description
`*` = [sale_subscription] Before this commit: In the mobile and form view, when a checkbox field had a long label, the checkbox would appear on top, with the label text displayed below. After this commit: In the mobile and form view, checkbox fields with long labels are now properly aligned, with the checkbox and label text displayed. Task-4269578
This update fixes a display issue in the General Ledger report where the table overflowed, causing the right side of the page to be cut off. The fix addresses a problem with a column width that was too wide, ensuring the report is fully visible and readable. This improves the user experience when generating and reviewing financial reports.
Original PR description
Steps to reproduce ================== - Install account_accountant,l10n_ch_reports - Use the CH company - Create a new chart of account 12345 "Current Account Abcdgraph Labs 12345 Pvt Ltd" - Create a new customer "Abcdefghijklm Abcdefghijklm 1234" - Create and post a new journal entry for journal 12345 - Go to the General Ledger - Print the ledger => The right side of the page is cut off Cause of the issue ================== The column containing account is too wide and the table overflows the body  opw-4286133