Monday, July 8, 2024
4 changes
2 changes
Resolved issues and error corrections
This fix stops the web interface from registering the same template extension more than once. It reduces the risk of unexpected crashes when duplicate frontend assets are loaded, improving stability for users.
Original PR description
Before that commit, it was possible to register several times the same template extension. This can lead to crash in some occasions. For example consider the template
```xml
<t t-name="A">
<div attr="a" />
</t>
```
and its extension
```xml
<t t-name="B" t-inherit="A" t-inherit-mode="extension">
<xpath expr=".//div[@attr='a']" position="attributes">
<attribute name="attr">b</attribute>
</xpath>
</t>
```
In that case, when building the template A with B registered twice, the first application of B to A will succeed while the second application will cause a crash (no target found for the xpath).
Here we prevent multiple registering of the same template extensions. Note that this is similar to what happens when the same js module is received several times: odoo.define has no effect after the first registering.The message composer now displays recipient names and joining words with proper spacing in the chatter. This makes the recipient list easier to read and avoids a small visual glitch when sending messages.
Original PR description
Before this commit the recipients list displayed when sending a message on the chatter missed spacing between the recipients and conjunctions. This happens because the container has display flex which removes whitespace from child elements. This commit fixes the issue by wrapping the list in a div tag so to preserve the whitespace. task-4032550 Before:  After: 
1 change
Resolved issues and error corrections
This fixes an error that could occur when an employee was assigned to a preparation display order in Point of Sale. It helps keep kitchen preparation workflows stable and avoids interruptions during order handling.
Original PR description
Fix traceback when assigning employee_id to pdis order. taskId: 4037944
1 change
Resolved issues and error corrections
This update corrects how expense accounts are classified in Danish financial reports. The "Purchase of goods" account was reclassified from a general expense to a direct cost category, which ensures the test data accurately reflects the proper account ordering in reports. This fix ensures Danish compliance reporting works correctly.
Original PR description
[FIX] l10n_dk_reports: fix account type of DK report tests By fixing the type of the account "Purchase of goods" from expense to expense_direct_cost the test now takes the new first expense account which is now "Freight costs" and not "Purchase of goods" anymore task-id#3983710 odoo-pr#[168838](https://github.com/odoo/odoo/pull/168838)