Tuesday, August 6, 2024
5 changes
3 changes
Resolved issues and error corrections
This fix ensures self-ordering always has the required default user set when the feature is enabled. It prevents customers or staff from seeing access errors when opening kiosk or menu ordering pages after the setting was removed.
Original PR description
When self ordering is enabled, default user should always be set. If it is not the case, self ordering pages would return access error Steps to reproduce: ------------------- * Enable self order (kiosk/menu/menu+ordering) * Remove default user from pos config * Try to open the self order page > Observation: you get an access error opw-4076798 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Incoming emails in very long conversations now check only the most recent message references when deciding which thread they belong to. This avoids inefficient database searches on large systems while preserving normal behavior for typical email threads.
Original PR description
We previously took into account all possible Message-IDs found in the References header of incoming messages. We also don't try to match the `In-Reply-To` header separately, since it is supposed to…
We previously took into account all possible Message-IDs found in the References header of incoming messages. We also don't try to match the `In-Reply-To` header separately, since it is supposed to be appended to the `References` header, when present. This is all specified in RFC5322, section 3.6.4: https://datatracker.ietf.org/doc/html/rfc5322#section-3.6.4 However, for very long threads, the `References` field can contain dozens or even hundreds of previous Message-IDs, even though we generally care only about the last one. This can be an issue for databases with a large number of messages, as the query planner could mistakenly choose a suboptimal plan (e.g. a Seq Scan or filtered Index Scan), rather than looping on the `message_id` index, which is the best plan. Here we truncate the list of References to only include the last 32 ones. For most threads this will make no difference, as they have less than 32 referencs. For very long threads it should still pick up the last known Message-ID without trouble. And if the last 32 messages aren't known by the system, it's unlikely that the message should still be considered part of earlier threads - it's been sidetracked elsewhere. PS: also simplify the `order` clause, as no secondary sort criterion is going to work after `ORDER BY id`.
Fixes an issue in Point of Sale where failed kitchen/change printing could leave old content behind and cause it to appear on the customer's receipt. Receipts now print only the intended order information, reducing confusion for restaurant staff and customers.
Original PR description
If you print changes in a restaurant, then print the receipt of the same order. The receipt would contain the changes. Steps to reproduce: ------------------- * Setup a printer to print changes and give it the IP 0.0.0.0 so that it fails * Open a PoS restaurant * Add some product to the order, and send it in preparation * You will have an error * Pay for the order, and print the receipt with web print > Observation: The changes of the order appears on top of the receipt Why the fix: ------------ This was happening because the content of `render-container` was not emptied. So when trying to print the receipt, the content of the receipt was added to the changes already in the `render-container` opw-4027722 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
1 change
Resolved issues and error corrections
This change improves how manufacturing work orders record consumed quantities, helping ensure materials are marked and counted correctly when production is completed. It also cleans up related inventory tests and fixes a barcode manufacturing form check to avoid incorrect matches.
Original PR description
# ARCHIVED PR That's pull request was splited in two separate prs `PART 1`: https://github.com/odoo/enterprise/pull/67683 `PART 2`: https://github.com/odoo/enterprise/pull/67684 ## mrp_workorder: fix…
# ARCHIVED PR That's pull request was splited in two separate prs `PART 1`: https://github.com/odoo/enterprise/pull/67683 `PART 2`: https://github.com/odoo/enterprise/pull/67684 ## mrp_workorder: fix quantity consumed operation With the new way of computing the quantity consumed, it is no longer necessary to mark the move_raw_ids in this function, since we call button_finish method right after. In button_finish, we take responsability for marking it as picked and updating the quantity consumed ## clean up _post_inventory tests This commit add 2 simple refactor to our existing tests, they are: -> _post_inventory calling button_mark_done() will call _post_inventory, so, it is not needed to call _post_inventory to test the flow. -> consumed quantities Fixing some tests to make sure that the current flow will not mark the picked as box when we change the quantity produced. ## stock_barcode_mrp: fix misstyping on saveFormView Before the commit, the condition inside saveFormView was returning True, because the same content was fit in two diferents types. The fix for it was just assert the id and the name of the content. task: 3810344
1 change
Resolved issues and error corrections
Fixed an issue where branch companies couldn't compute taxes using AvaTax because they were looking for their own credentials instead of the parent company's. Now branch companies will automatically use the parent company's AvaTax credentials, since tax reporting is handled at the parent level. This eliminates configuration errors when setting up AvaTax for multi-company structures.
Original PR description
Create Branch Set up Avatax on main company Try to compute taxes using Avatax on Branch company Issue: Receive error asking to add Avatax Credentials When working with branches, Avatax should only be configured on the main company and not from the branches, since the tax report will be done from the parent. opw-3962212