Daily updates from Odoo
Saturday, July 25, 2026
2 changes · master
Enhancements to existing features
Odoo Enterprise now uses the newer Material Symbols icon style across many screens, replacing older icon formats. This makes the interface more consistent and keeps icon selection tools aligned with the current design system.
Original PR description
[IMP] *: apply new icon implementation globally --- This commit is a follow-up to odoo/odoo#273606. It applies the new icon implementation across the entire codebase, replacing almost all legacy icon…
[IMP] *: apply new icon implementation globally
---
This commit is a follow-up to odoo/odoo#273606.
It applies the new icon implementation across the entire codebase,
replacing almost all legacy icon usages.
Previous patterns such as `class="oi oi-fw oi-arrow-left"` or
`class="fa fa-fw fa-arrow-left"` are migrated to the new format
using `class="oi oi-fw"` with the data-icon attribute (e.g.,
`data-icon="west"`), ensuring consistency with the Material
Symbols-based system.
Community PR: odoo/odoo#256840
task-5901783
---
[IMP] web_{enterprise, studio}: adapt icon selector for Material Symbols
---
With the switch to Material Symbols as the icon set, the app/menu icon
pickers and the various places that render web icons no longer rely on
Font Awesome classes. The FontAwesomeIconSelector component is renamed to
the StudioIconSelector and now sources its choices from the html_editor
MediaDialog icon selector (via initFonts) instead of the removed
getFontAwesomeIcons util. Icons are rendered with the `oi` class and a
`data-icon` attribute holding the Material Symbols name rather than a
composed class string, and the st full icon
name (no more stripping the `fa ` prefix).
Templates and components across web_enterprise (home menu, navbar) and
web_studio (icon creator, editor button box
dialog) are updated accordingly, the icon_selector asset is added to the
Studio minimal bundle, and the reusted to use
Material Symbols names.
task-5901783Resolved issues and error corrections
The WinBooks import now avoids merging contact details when contacts with the same number have clearly different VAT numbers. This prevents valid imports from failing because supplier and customer information was incorrectly combined.
Original PR description
When importing a WinBooks zip, contacts sharing the same number might fail VAT validation if distinct contact data is merged incorrectly. Steps to reproduce: - Create a database with the Belgian…
When importing a WinBooks zip, contacts sharing the same number might fail VAT validation if distinct contact data is merged incorrectly. Steps to reproduce: - Create a database with the Belgian localization installed - Install the account_winbooks_import module - Navigate to Accounting > Configuration > Settings > Initial Setup > Import - Import the WinBooks zip Issue: The import fails with the following error: The VAT number [AAAAAA] for partner [BBBBBB] does not seem to be valid. Note: the expected format is BExxxxxxx. Analysis: In WinBooks, contacts can be of type Supplier or Customer, and it is possible for a supplier and a customer to share the same number. During the import, the system will merge contacts if found with the same number. In the specific case, the VAT number from one contact without country is combined with the country information from another contact, resulting in a VAT validation error. This change prevents the merger of partner data if their VAT numbers are explicitly different. opw-6251772 Forward-Port-Of: odoo/enterprise#119579