Monday, January 6, 2025
8 changes · 17.0
Resolved issues and error corrections
This fixes PDF/A-3 conversion so generated files include the required header marker expected by compliance validators. It helps prevent validation errors when businesses archive or exchange PDF documents that must meet PDF/A standards.
Original PR description
**Issue:** When converting a PDF file into a PDF/A compliant file, the result may generate the following error message when parsing it by a PDF/A-3 validator: `The aforementioned EOL marker shall be immediately followed by a % (25h) character followed by at least four bytes, each of whose encoded byte values shall have a decimal value greater than 127 ` **Cause:** A previous fix has moved the four bytes in a conditional operation, but the `%` character has been forgotten. opw-4353108 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The live chat widget styling was adjusted so key elements remain visually clear even when certain layout classes are missing. This helps prevent confusing or broken-looking chat screens for website visitors and support teams.
Original PR description
Purpose of this PR: Enhance the UI styling to address issues caused by the absence of the `o_livechat_no_rating` and `o_livechat_operator_avatar` classes,might removed by other PR's. before:  after:  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Expense settings now correctly update the email domain used for submitting expenses by email. This prevents a mismatch where the visible settings showed one domain while the underlying expense email alias continued using another.
Original PR description
**Steps to reproduce:** - Install hr_expense - Create 2 alias domains - Go to "Settings / Technical / Email / Aliases" - Check the values for Expense model - Go to Expenses settings - Change the…
**Steps to reproduce:** - Install hr_expense - Create 2 alias domains - Go to "Settings / Technical / Email / Aliases" - Check the values for Expense model - Go to Expenses settings - Change the prefix and the domain of the alias - Save - Go to "Settings / Technical / Email / Aliases" - Check the values for Expense model again **Issue:** The prefix has correctly been modified but not the domain. The domain from Expenses settings and the domain of the Expense alias are different. **Cause:** The domain field in Expenses settings is in fact the Email Domain (alias_domain_id) of the company, which makes no sense to combine the prefix and the domain from 2 different sources. **Solution:** Add a non-stored computed field to map the domain displayed in Expenses settings with the domain of the Expense alias. Not great in stable, but there is no other way if we want to keep the option. opw-4293936 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Payment and receipt PDFs no longer show a default customer when no customer was selected. This prevents incorrect customer names from appearing on documents and keeps printed records accurate.
Original PR description
## Before this commit: When creating a Payment/Receipt without specifying a partner, the system defaulted to `Marc Demo` as the customer on the printed PDF. ## After this commit: The customer field on the PDF remains blank if no partner is specified. It only displays the customer name when a partner is specified. > Task: 4182618
This fixes a small display issue in the Contacts list where an empty name column was appearing after a recent change. The contact list is cleaner and shows only the intended information, reducing visual clutter for users.
Original PR description
Description of the issue/feature this PR addresses: - A recent change in the contact's list view introduces a small bug, due to which, now a blank column for display name appears. commit ensure correct attribute value for list view. - [commit](https://github.com/odoo/odoo/commit/76aa55dbfcce535d645270448b096ed8cfede104) that introduces issue. Current behavior before PR: - a blank column is visible  Desired behavior after PR is merged: - `display_name` field is hidden properly.  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix ensures formatted HTML field content is handled correctly when shown in Gantt popovers. Users can now see the intended rich text output instead of incorrectly processed or missing formatting.
Original PR description
In GanttModel, we markup html values like it is done in the util function parseServerValue so that is it now possible to use t-out on html field values in the gantt popovers (and possibly elsewhere) and have correct results. Task ID: 4382205
This fix prevents subscription-related automated tests from failing when inventory features are not installed. It moves the affected check to the module where the required stock information exists, improving test reliability without changing customer-facing behavior.
Original PR description
If stock was not installed, we could not run skip test_prevent_advance_payment_delivered_quantity_product, as there is no qty_to_deliver field in sale.order.line model. By moving the test to sale_subscription_stock, we are solving this issue [link to broken tests](https://runbot.odoo.com/web#id=108148&menu_id=424&cids=1&action=573&model=runbot.build.error&view_type=form)
This fix makes FedEx delivery tests consistently use USD in their mocked setup, regardless of the company or product currency configured in the test environment. It helps prevent false test failures and supports more reliable validation of FedEx delivery functionality.
Original PR description
The tests were written to only support USD currency, however the test does not change the currency of the company/products causing it to fail if somehow it wasn't set up with USD. We now mock the fedex currency mapping in order to always return USD regardless of the active currency. Runbot Error 107969