OCB.git, branch 18.0

Merge remote-tracking branch 'odoo/18.0' into 18.0

2025-02-08T23:30:13+00:00

[FIX] base: prevent error on duplicating multiple records

2025-02-08T07:33:31+00:00

This error occurs when attempting to duplicate two actions in 'Server Actions'. Steps to reproduce: - Search 'Server Actions' - Select any two Actions and 'Duplicate' Traceback: ValueError: Expected singleton: ir.actions.server(606, 701) After this commit: We are now able to duplicate multiple records. sentry-6218495006 closes odoo/odoo#194118 Signed-off-by: Raphael Collet

[FIX] point_of_sale: lot-serial dialog in small ui

2025-02-08T02:20:59+00:00

Before this commit: - Lot-serial dropdown not visible in the small UI. After this commit: - Displayed the lot-serial dropdown in the small UI. opw-4551161 closes odoo/odoo#196957 Signed-off-by: Vlad Stroia (vlst)

[FIX] point_of_sale: correctly connect loaded many2one fields

2025-02-08T02:20:58+00:00

Before this commit, if a many2one field was loaded with its data, it would not get connected. For example, in the Chilean localization, the account_move is loaded when capturing an order, but it would not get linked, causing an error. opw-4479284 closes odoo/odoo#196994 X-original-commit: 86fd956e8828117c82d74baa0d7ae04cff93b745 Signed-off-by: David Monnom (moda) Signed-off-by: Andrea Grazioso (agr)

Merge remote-tracking branch 'odoo/18.0' into 18.0

2025-02-07T23:30:16+00:00

[FIX] account: CABA on payment with credit note

2025-02-07T23:17:13+00:00

Before this commit, the credit note's tax lines were causing an issue during reconciliation because they were reconciled with both the invoice and with the cash basis entry. Reproduce: * Enable cash basis accounting. * On the tax that will be used, set: Tax Exigibility: Based on Payment. * Allow reconciliation on the associated account. * Add a product without tax and save. * Then, add a tax. * Try to create and post a credit note for this invoice opw-4281749 opw-4439671 opw-4358532 closes odoo/odoo#196933 X-original-commit: 09da61a1ef67be78f50c042afe650b2c3bea7539 Signed-off-by: Laurent Smet (las) Signed-off-by: William André (wan)

[FIX] pos_restaurant:fix empty preparation receipt

2025-02-07T23:17:05+00:00

When creating multiple preparation printers for different pos categories you could have a case where an empty receipt is printed. Steps to reproduce: ------------------- * Create 2 PoS categories CAT 1 and CAT 2 * Create a first preparation printer for CAT 2 * Create a second preparation printer for CAT 1 * Create a product P1 for CAT 1 * Assign the two printers to a PoS * Open PoS and add the P1 to your order * Send the order in preparation > Observation: Two receipts are printed and one of them is empty Why the fix: ------------ When going over each printer to print the relevant changes, if the first printer in the list has no changes it would always print an empty receipt because `last_preparation_change` would always be empty. To fix this we rely on `changes` to check if there are any changes to print on this printer opw-4462586 closes odoo/odoo#196808 Signed-off-by: David Monnom (moda)

[FIX] hr_*: allow editing unapproved allocation requests

2025-02-07T23:17:02+00:00

*: holidays,holidays_attendance The base.group_user did not have the access right to read overtime_id, which is necessary for filtering allocations that do not have a null overtime_id. The access right was granted to base.group_user only when the allocation state is either draft or confirm. In the test_expiration_date_2 the user needed to be a user_hruser to have the access rights to edit the number_of_days. task-4452360 closes odoo/odoo#196815 X-original-commit: 2bb61e4d534d23bf81a0b36f6ffcc27c0f6a6a0b Signed-off-by: Yannick Tivisse (yti)

[IMP] account: Secured group usability

2025-02-07T23:17:01+00:00

Current behavior: As of now, whenever a journal is set to "Hash on Post", the user is granted the secured group rights. This allows the user to see the lock icon in the status bar, the extra default filters in the list views of Journal Entries and Journal Items, and access to the Secure Entries wizard. However, if only entries from journals with "Hash on Post" are secured, these features are not necessary. The user trusts Odoo to hash any and all entries that are posted in that specific journal. Expected behavior: When "Hash on Post" is active, the user does not need any additional user group. However, if even one entry is secured and does not belong to a journal with the "hash on post" feature, the user will then need access to the new features, such as the lock icon, default filters, and the Secure Entries wizard. Approach: This commit removes the calls to _activate_group_account_secured() when setting a journal to "Hash on Post". It also removes it from the Secure Entries wizard. Instead, we add the key 'journal_restrict_mode' to the chains_to_hash, which indicates the value of the journal's restrict_mode_hash_table field. If at least one chain with moves does not have 'journal_restrict_mode', only then we call _activate_group_account_secured() from _hash_moves(). This will only happen when the Secure Entries wizard is used, hashing entries from all journals. task-4348380 closes odoo/odoo#196748 Signed-off-by: William André (wan)

[FIX] html_editor: correctly position close icon on file upload notification

2025-02-07T23:16:54+00:00

**Problem**: The close icon on the file upload notification is misplaced, appearing at the top-left instead of the expected position on the right. **Solution**: Adjust the button's position to appear on the right side of the notification. **Steps to Reproduce**: 1. Open the Editor. 2. Upload a file. 3. Observe that the close button appears on the top-left instead of the right. opw-4512322 closes odoo/odoo#195209 Signed-off-by: David Monjoie (dmo)