Monday, January 20, 2025
11 changes
1 change
Resolved issues and error corrections
The Lebanon accounting demo company setup now correctly recognizes demo data during installation. This avoids an unnecessary warning and helps demo environments install more smoothly.
Original PR description
The install_demo is missing from the try_loading of the Libanese demo company. runbot-109449 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
10 changes
Resolved issues and error corrections
Portal chatter messages now load the needed Discuss translations on the website frontend. This prevents untranslated labels or text from appearing to portal users and improves the experience for multilingual websites.
Original PR description
Portal chatter now uses discuss, thus it relies on translation of Discuss in `mail` module. Frontend translations need to be available, they aren't by default unless the module is prefixed by `website`. This isn't the case for `mail`, and the module `website_mail` does not share the translations. This commit fixes the issue by enabling `mail` in the translations of available translations in the frontend Task-4423556
This fixes an Accounting issue where companies using February 29 as their fiscal year end could encounter errors when journal entry placeholder names were created in non-leap years. The system now safely uses February 28 in those years, allowing accounting records to be created or updated without interruption.
Original PR description
### Description of the issue/feature this PR addresses: If the customer sets their last fiscal day and month to February 29th, a ValueError may be raised when creating a placeholder name for…
### Description of the issue/feature this PR addresses: If the customer sets their last fiscal day and month to February 29th, a ValueError may be raised when creating a placeholder name for account.move records if their dates are not in a leap year. More precisely, a ValueError is thrown when creating the starting sequence of the placeholder name, as a new date object is created using the company's last fiscal day and month and the year of the account.move. This commit adjusts the day of the created date to February 28th if the last fiscal day and month is set to February 29th and if the account.move year is not a leap year. This date was chosen since that's 365 days after February 29th. ### Current behaviour before PR: If the company's last fiscal day and month is set to February 29th, creating a placeholder name for account.move records whose date is not in a leap year raises a ValueError. Steps to reproduce: 1. Set the last fiscal day to February 29th. 2. Go to Accounting > Journal Entries (account.move). 3. Trigger the computation of the placeholder name for account.move() (edit journal_id, create record, edit date field...) 4. A ValueError exception is raised. ### Desired behaviour after PR is merged: The placeholder name for account.move records is successful and less prone to errors. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix corrects the layout of a stock location table so it expands across the available form width as intended. It improves readability and avoids a cramped display caused by the previous automatic layout handling.
Original PR description
Commit 239e75b1385fa0 removes `colspan="2"` to guess it from the `nolabel` attribute. This is not working because of the `string=` attribute in the `group` tag that makes the DOM having two elements instead of only one. The rule in https://github.com/odoo/odoo/blob/0ba664bace1e6bbb256bd98570866df19d35f401/addons/web/static/src/views/form/form_controller.scss#L474 is not applied. 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
Purchase requests for quotation and purchase orders now show their title properly when the folder document layout is selected. This prevents malformed report headers and keeps printed documents easier to read for users and customers.
Original PR description
Steps to reproduce: ------------------ - Go to settings - Change the Document Layout to folder - Go to purchase - Print a RFQ or a PO Issue: ------ Currently the display of the folder wants the layout_document_title to fit in the upper right corner, which is not always possible especially in the purchase. This leads to the title being malformed. However this fix will also changes other apps display for this layout. Fix: ---- The fix replace the ```html <h2 t-out="layout_document_title"/> ``` where it is in every other layout. This fix the issue and does not break other apps display. opw-4380886 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change adds extra checks to an automated Studio test so it follows the intended path during module export validation. It helps reduce false test failures and improves confidence in the Studio export process without changing user-facing behavior.
Original PR description
In this commit, we add 2 additionnal check steps to ensure the tour take the good way. runbot-error-id~109456
The settle due flow now searches only among open orders, so already finalized orders are no longer selected by mistake. This helps cashiers avoid confusion and reduces the risk of handling payment follow-ups on orders that are already paid.
Original PR description
Before this commit, when searching after an empty order, sometime a finalized order was returned. This commit fixes the issue by only checking open orders.
When a file upload fails in Documents, users will now see a clear error message instead of being left without feedback. This helps users understand that the upload did not complete and reduces confusion when resolving upload issues.
Original PR description
**Before this PR:** Upload fails(normal) but there is no proper error message. **Technical:** We previously received an error message in the "handleUploadError" function, such as "result.error." However, after the commit https://github.com/odoo/enterprise/commit/a32825ee00f2b330d99113f4d8c1488903fe744e, the error now appears directly in the "result". **After this PR:** An appropriate error message will be shown. Task-4357390
Automatic bank reconciliation now records the reason when a validation issue prevents a statement line from being matched. This helps support teams investigate reconciliation problems after the fact without changing the reconciliation flow for users.
Original PR description
During the auto bank reconciliation, user error when validating the matching are ignored which hides why a statement line is not matched by a reconciliation model. This PR adds logs including the user error so it can be retrieved from the logs when doing post mortem analysis. opw-4393854
The update fixes an internal test setup so project profitability checks can run correctly even when demo data is not installed. This helps ensure the manufacturing work order accounting integration remains reliable across more deployment configurations.
Original PR description
This commit's purpose is to make the profitability test works without demo data. The issue is that without some specific groups, the 'workorder_ids' field is not visible inside the views, making the creation of record impossible. Adding these groups in the config of the test fixes the issue version 18.0-master
The grid view now respects configured time steps, such as showing one column for a full month instead of loading daily columns. This prevents incorrect or overly detailed grid displays when businesses customize date ranges.
Original PR description
Before this commit, if the user alters the grid view to have this kind of ranges: ```xml <range name="month" string="Month" span="month" step="month"/> ``` the `step="month"` will not be used to load the data for the grid view and will continue to load data per day (when this range is the current one in the grid view). This commit makes sure the step is correctly used to fetch the data for each columns displayed in the grid view (in this case only one column for the whole month should be displayed).