Tuesday, July 23, 2024
6 changes · 17.0
Resolved issues and error corrections
Mobile search results for chats and channels now display names with their intended capitalization instead of forcing uppercase. This makes search results easier to read and keeps the mobile messaging interface consistent with the actual chat and channel names.
Original PR description
Before this commit, search results for chats and channels on mobile show up in uppercase. This happens because of the class `text-uppercase` on a parent element. This commit fixes the issue by removing said class on the parent element. Before:  After: 
Spanish Facturae electronic invoices now include the seller's name when the seller is registered as an individual rather than a company. This prevents incomplete invoice files and helps ensure compliance when sending or printing Facturae documents.
Original PR description
To replicate the issue: - Go to the partner page of the current company (Invoicing > Customers > Customers > Look for the company) - Change type from Company to Individual - Create and post an invoice - Click on Send & Print. Download the Facturae - NAME should appear in line 30, before AddressInSpain, but it doesn't Cause of the issue: The template values do not include a value for self_party_name, only for other_party_name. In the template, when partner_name is set, no value is passed for self_party. Fix: Instead of only extracting the partner name for partner (other_party), the code is used in a new function, which can be called for both partner and company (self_party). Then, self_party_name can be used as a value in the template. opw-4053023 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents copied databases using the Romanian e-Factura module from accidentally interacting with live external systems. It helps support teams investigate issues safely without risking real customer or production impacts.
Original PR description
This commit adds the missing neutralization necessary for the l10n_ro_efactura module introduced in [1] The purpose of the standard neutralization framework is to allow us to create database copies that will not interact with external systems in ways that could impact the production database (or if it is not possible to prevent the interactions, make sure that they are benign or won't result in actual changes), or impact the customers of the operator of the production database. This is mainly useful to allow safe support investigation on database duplicates. [1] https://github.com/odoo/odoo/pull/144061
The date range widget now correctly flags a required end date when it is left blank. This helps users spot incomplete date ranges immediately and avoid saving forms with missing required information.
Original PR description
Specification: In the daterange widget, if the second date field is required and left empty, the field should be marked as invalid and be colored red. Expected behavior: if the second field is empty so that fields should be highlighted in red. Task-3786540
This fixes a Dutch website translation that accidentally changed a carousel button class name, causing the next arrow icon to disappear. Dutch-language website carousels should now show the expected next button icon again, improving navigation for visitors.
Original PR description
Description of the issue/feature this PR addresses: Carousel icon doesn't display icon for next button due to a translated class name. Current behavior before PR: On my site the carousel doesn't…
Description of the issue/feature this PR addresses:
Carousel icon doesn't display icon for next button due to a translated class name.
Current behavior before PR:
On my site the carousel doesn't display the right next icon. It's because the html served contains the wrong class.
On my site the carousel still doesn't display the icon, but this has to be the fix. I believe my site is using a cached version, since the aria label also doesn't change when choosing another language. Would appreciate it if someone can test if this actually solves it.
```html
<a class="carousel-control-next o_not_editable o_we_no_overlay" data-bs-slide="next" role="img" aria-label="Volgende" title="Volgende" href="{unique}">
<span class="carrousel-control-next-icon"></span>
<span class="visually-hidden o_default_snippet_text">Volgende</span>
</a>
```
Desired behavior after PR is merged:
```html
<a class="carousel-control-next o_not_editable o_we_no_overlay" data-bs-slide="next" role="img" aria-label="Volgende" title="Volgende" href="{unique}">
<span class="carousel-control-next-icon"></span>
<span class="visually-hidden o_default_snippet_text">Volgende</span>
</a>
```
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update adjusts how the Kenya EDI system logs messages when no company information is found during routine scheduled tasks. Instead of flagging these occurrences as errors, they are now logged as warnings, which better reflects that this is a normal operational situation rather than a system problem. This reduces unnecessary alert notifications and helps teams focus on actual issues.
Original PR description
Currently, log level error message occur when no company is found during scheduled actions run at line [1]. This commit changes 'logger.error' to 'logger.warning' to log a message instead of an error since this is not an actual error in the code base. [1]-https://github.com/odoo/enterprise/blob/ddc81ed35a6738739647db868c13236673695cff/l10n_ke_edi_oscu/models/res_company.py#L437-L438 sentry-5608113473