Online store managers can now customize the top area of category pages with rich website content such as covers or other building blocks. This makes category pages more flexible and visually engaging without requiring code changes.

This update simplifies how product attribute information is included on eCommerce product pages. It makes the page structure easier to maintain and reduces the risk of future website display issues, especially in multi-website setups.

Historically, the `website_sale.product_attributes` was a customize option.
That template became a normal view (removed customize_show attribute) with
bbd2d0e42
As it is now a normal view, there is no reason left to be an xpath view and we
can move itw code directly into the inherited template.

That way, we can simplify the `website_sale_comparison.product_attributes_body`
template that was doing a cross xpath (inheriting `website_sale.product` but
xpathing a DOM element from `website_sale.product_attributes` which was also
inheriting `website_sale.product`).

Note that cross xpath was not working well with multi website but was fixed
with 410c07283b

Still, we should avoid doing cross xpath when possible (originally it was not
possible since the view was a customize_show) as it is hard to grep DOM element
to find possible breaking xpath when doing changes on DOM.
This is the reason of this commit.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This change blocks configurations where the same accounting account is used for stock valuation and stock input or output. Preventing that setup helps avoid accounting entries cancelling each other out, so inventory valuation remains accurate.

Description of the issue/feature this PR addresses:
task # https://www.odoo.com/web#id=1908065&action=327&model=project.task&view_type=form&menu_id=
Current behavior before PR:

Desired behavior after PR is merged:




--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Stock location settings were simplified by removing unused and confusing options, including obsolete location usage and partner links. Warehouse and replenishment setup is now safer because key warehouse locations cannot be archived, replenishment points are limited to appropriate locations, and scrap locations are restricted to valid use cases.

Here we are cleaning some stuff in locations

HR users can now search employee records by company, making it easier to find the right people in multi-company environments. This helps teams manage employee information more efficiently when several companies are handled in the same system.

When a manufacturing order is cancelled, any related quality checks that are still pending are now removed automatically. This keeps cancelled work from leaving unnecessary follow-up items and gives stock users the read access needed to view quality checks consistently.

Task : https://www.odoo.com/web#id=1871423&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720

Pad : https://pad.odoo.com/p/r.9f167983b5ac4bb98c304cd53b0b1630

Translation synchronization now consistently chooses the most recent matching translation instead of relying on an unpredictable order. This reduces intermittent translation issues and makes related tests and user-facing translated content more reliable.

When synchronizing translations, the algorithm search for the translated
terms without specifying an order.
As a result, the translation terms are in an non deterministic order and
the first one is chosen which might not be the latest.

During the tests, this bug appeared from times to times during the
rte_translation tour. One way to force it, is to order the translations
by value descending.

With this commit, the translations are ordered by id descending, as a
consequence, the chosen translation will always be the latest.