Monday, May 26, 2025
5 changes · 17.0
Resolved issues and error corrections
This update prevents searches from failing when a user enters a value that can be read as one type of data but not another. It improves reliability for currency-related searches, such as looking up exchange rates, by ignoring incompatible fields instead of showing an error.
Original PR description
Encountered an issue where `_name_search` would crash if a search term couldn’t be converted to all expected field types — specifically when using a string like "1971-01-01" that gets interpreted as a date, but also hits a float field in the comodel. This happened when searching currencies by exchange rates, which involve both a date field (`name`) and a float field (`rate`) in `res.currency.rate`. The original implementation only caught `ValueError` during type conversion, but in my case it was raising a `TypeError` when attempting to convert a `datetime.date` to a float. To fix this, I expanded the exception handling to also catch `TypeError`, ensuring `_name_search` gracefully skips over fields where conversion is invalid. This aligns with the intended behavior described in the original fix — to silently ignore incompatible fields instead of failing. Failing in Distro Build , python version >=3.10 raises a `TypeError` build_error-110207
This fix updates the blog testing setup so it properly verifies the month shown for blog posts. It helps prevent incorrect blog date behavior from passing unnoticed in automated checks.
Original PR description
This PR updates the blog tour configuration to match what the Python test expects. The tour was designed in a way that avoids checking the actual month name, so even if the blog's publish month and the tour's month were different, the test wouldn’t fail. To make sure the test behaves correctly, we needed to update the tour so it fully aligns with the Python test case. Related PR: [#197172](https://github.com/odoo/odoo/pull/197172) task-4546888
This fix prevents the system from flagging nearly identical Date headers as duplicate issues when they are only milliseconds apart. It reduces misleading warnings for valid website or API requests, helping teams focus on real problems.
Original PR description
The code proved unreliable, emitting warnings for genuine controllers because the two headers were milliseconds appart. Made the warning ignore some almost equal headers.
This fixes an error that could appear when creating automation rules using rental pricing filters. Business users can now set up these rules without running into a confusing technical failure.
Original PR description
Versions -------- - 17.0+ Steps ----- 1. Go to Automation Rules; 2. create a new automation; 3. set model to `product.pricing`; 4. in one of the filters, check the record(s) that fit in the domain. Issue ----- > EvalError: Can not evaluate python expression: (bool(parent.product_variant_count < 2)) > Error: Name 'parent' is not defined Cause ----- `parent` is not defined because the `product_variant_ids` field in the view does not have a parent field to evaluate. Solution -------- Remove the `parent` checks. opw-4788215
The Swiss payroll module now uses a longer external code for the 13th salary provision, preventing display issues on payslips. This is a small correction that helps payroll documents appear correctly for users handling Swiss salary processing.
Original PR description
…de for payslip display We increase the size of the external CH code to not impact payslip display