This update adds a tax number field for partners in the Hungarian localization, helping businesses record locally required tax identification details. It supports better compliance and cleaner customer or supplier records for companies operating in Hungary.

This change adds a simple way to record debug messages while creating or testing server actions. It helps administrators and implementers understand what automated actions are doing, making setup and troubleshooting faster without affecting everyday users.

...building server action

Example of use in server action:
log('Message: %s' % obj.name)

This update makes Odoo translations easier to maintain by splitting large website and HTML content into smaller parts instead of requiring whole pages or descriptions to be retranslated. It also keeps existing translations when only small English typo fixes are made, while flagging larger wording changes for review.

## Improvements

This branch improves the translation mechanism, mostly needed for frontend:

1/ Translation of XML/HTML fields: are managed like arch in ir.ui.view. Splited in smaller goups rather than having to translate the whole field (e.g. a blog, a product description, etc.)

2/ Typos management when translating from the website: if a typo is fixed on an english string, you do not have to translate the whole blog again in all languages. If you completely change a paragraph, it has to be translated again (only the paragraph, not the whole blog). If you just fix a typo, the translated versions remain.

3/ The translation of views is not a specific use case anymore, it's just translate=True on the arch field of ir.ui.view.

4/ Mark as 'To Translate' translated values of an English field that has been changed (if the distance of the change is higher than 0.9). Exemple:
   'Hello Wrold!' to 'Holy Grail!' --> You have to re-translate the french version
   'Hello Wrold!' to 'Hello World!' --> You do not have to re-translate the french version
## Changes
- Fields support not only translate=True, but also translate=CHUNK_METHOD. This method takes a string in argument and return a list of strings to translate.
- From the client side point of view, translate=CHUNK_METHOD is like translate=False. (e.g. you can not modify the french version of the arch field of views)
- The context on translations changed in the exported .PO.   #: view:resource.calendar.leaves:0 is now  #: model:ir.ui.view,arch:resource.view_resource_calendar_leaves_search
## Done

Seems to work fine:
- tested to import .PO
- tested to export .PO
- tested in the frontend (translate read/write)
- tested in backend (translate=True fields  and translate=method ones)
## Todo
- put chunk_xml (in ir_ui_view) in tools/xml.py and use it in blogs, product description, ...
- improve chunk_xml to not split around inline tags: <b>, <i>, <strong>, <span>, <em>
- Adapt the frontend to support translation of HTML fields like views
- I put some TODO in the code, to finnish.
- optional improvement (only if few lines of code): add the english source when translating in french in the frontend as a tooltip. it's way easier for translators and reviewers.
- More tests
- Re-export .POs in all languages (ask ODO for this, he has his own script to do this)
## Known Bugs

get_close_match is not perfect due to spacings in XML (When editing an english version, multiple spaces are be crunched to one space. Due to this, get_close_match think it's a huge change, but there are nearly no change)

To reproduce:
- translate the sentence in footer (We are a team of...)
- change the english version by one character
- the translated version is not available anymore (it should stay in french since you just changed one character)
  If you repeat these steps just after, it works. (no more multiple spaces)

The CRM lead list now shows the company name as a separate column. This makes it easier for sales teams to identify and sort leads by organization without opening each lead record.

Contacts and users can now automatically use a Gravatar image as their default profile picture when an email address is available. This improves recognition in customer and employee records without requiring manual image uploads.

Task: https://www.odoo.com/web?debug=#id=8137&view_type=form&model=project.task&action=333&active_id=131
Pad: https://pad.odoo.com/p/r.lVlmyH1yY7REpZvS

This update modernizes core website components by moving to a newer jQuery version and refreshing related libraries used across Odoo's web interface. It helps keep the platform compatible with newer browser behavior while fixing rendering issues in templates and purchase flows.

- Pad https://pad.odoo.com/p/r.VyCsxr46FC8zDFJa
- Internal Task https://www.odoo.com/web?&debug#id=7864&view_type=form&model=project.task&action=333&active_id=131

The CRM contact merge wizard form has been adjusted to make automatic merging easier to use. This should help users handle duplicate contacts more smoothly and reduce confusion during cleanup.

This fixes how product price surcharges are applied so they align with the product's unit of measure. Businesses should see more accurate pricelist calculations when products use different units, reducing pricing errors for sales and purchasing.

This update makes a small correction to the project's README documentation. It helps keep public project information accurate and easier to follow, with no expected impact on product behavior.

This fixes an issue where switching between views could leave empty page containers visible when no controller was attached. Users should see cleaner, more consistent screens without stray blank areas caused by styling.

The view manager upon switch won't properly hide the empty `div` container for other views when they don't already have a controller.

CSS might then show these div quite easily.

It seems pretty obvious that they should be hidden properly even if empty.

This update addresses reported issue #988 with fixes spanning messaging, website interactions, recruitment, accounting, stock, portal access, events, blogs, and mass mailing. It should improve reliability for users working with communications and public-facing website features while reducing errors in related business workflows.

About Issue #988

This update corrects the alignment of the Weight field on the stock move form. It makes the form display more consistently, reducing visual confusion for users working with delivery or inventory details.

Hello,

Fixed the Issue #541 (#541)
In stock move form set the group alignment on "Weight " field.

Thanks.

Odoo now prevents users from deleting accounting accounts that are still referenced by tax settings. This helps avoid broken tax configurations and reduces the risk of accounting errors caused by removing accounts that are still needed.

This fixes a missing field on sales order lines related to bill of materials options. It ensures sales users can see and use the expected product properties when working with manufacturing-related sales orders.

I guess  the `property_ids` field has been left behind when moving the filed from `sale_stock` to `sale_mrp`.

A missing internal translation helper and service import were added to the common server service. This prevents errors in the about information workflow and keeps the server service loading reliably.

Add missing 'openerp.tools.translate._' function for the 'exp_about()' method and add relative import for the 'openerp.service.security' module.

Incoming emails are now matched to contacts using a stricter email comparison. This helps prevent messages from being linked to the wrong customer when similar email addresses exist.

The current operator is ilike but it add wildcards around right criteria so we can have false positive.

eg. I' have an email in my customer base like a_mail@provider.com

If I get a mail from mail@provider.com as ilike operator uses wildcards a_mail@provider.com can potentially be matched and retrun a faulty match.

Manufacturing orders created from procurement now calculate their required components only once instead of repeating the same step during confirmation. This reduces unnecessary processing and helps improve performance while still respecting the procurement order's bill of materials properties.

I assume that the reason to call `action_compute` method in `procurement.make_mo` is to pass in the `properties` parameters , and thus the BOM of the generated MO will be selected according to the BOM Properties on the related procurement order. 
However, the action_compute will be called the second time by the workflow when the MO is confirmed. The double call of the `action_compute` method caused performance issue <s>and  those unnecessary unlink product_lines process.</s>
This fix take care of the bom properties match inside action_compute, and thus remove the needs to call `action_compute` in `procurement.make_mo`.

The in-browser PDF preview feature has been removed by reverting the earlier web PDF viewer addition. Users will no longer preview PDFs directly inside Odoo through this module, which may change how reports and attachments are opened or downloaded.

This reverts commit 8b46d7b04fd0ddb74225e25c077a1222b1e0f9d7.

This change simplifies how people are linked to CRM, recruitment, project, and sales team records by using the existing follower list instead of a separate member list. This reduces duplicate data, makes access and notifications more consistent, and improves related views, filters, and demo data across affected apps.

Task: https://www.odoo.com/web#id=8544&view_type=form&model=project.task&action=333&active_id=131
Pad: https://pad.odoo.com/p/r.lsWeyXtbq94wHIXr