Monday, August 26, 2024
6 changes · 17.0
Resolved issues and error corrections
Spanish TicketBAI electronic invoices now use the delivery date as the operation date when it is available. This ensures the XML sent to the government reflects the actual delivery timing, falling back to the invoice date only when no delivery date is set.
Original PR description
Use the delivery date to fill the `FechaOperacion` and fall back to the invoice date if no delivery date is set. Steps: - Make an invoice with delivery_date != invoice_date != today - Send invoice to gouvernment - Download the xml generated - The field `FechaOperacion` is the invoice date instead of the delivery date opw-4072748
Printed documents now keep the phone marker together with the phone number in contact address blocks. This avoids awkward formatting in purchase orders and other reports when layouts or long phone numbers previously caused a line break after the phone icon.
Original PR description
Currently there might be a line break after the phone marker in the contact widget. It depends on the document layout and the length of the phone number. After this commit the line break does not happen anymore. (In commit cbcda0b222b17312b9e42e23801a330f0030033f line breaks inside phone numbers were removed.) To reproduce: 1. Ensure Purchase app is installed 2. Settings -> Configure Document Layout - layout: boxed - font: Oswald - paper format: A4 3. Edit some partner to have a long phone number (E.g. via Purchase -> Orders (menu) -> Vendors) e.g. use: (870)-931-0505 12 12 12 12 4. Create a request for quotation / purchase order and select the partner from 3 as Vendor 5. Confirm the purchase order 6. Print the purchase order 7. There is a line break after the phone marker in the vendor address opw-3783870 opw-3970768 PR the mentioned commit belongs to: https://github.com/odoo/odoo/pull/166336
This fix adjusts how a Project task list column is hidden so the list view behaves as intended. It helps avoid confusing or inconsistent task list displays for users working in the Project app.
Original PR description
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
Issue ---- POS payment methods that are already translated don't have their translation show up. Steps ----- Go to Point of Sale -> New/Continue Session -> Add something to pay for -> Click on "payment". The listed payment methods are not translated if you chose another language. Cause ----- Although the terms were translated, they were not showing up because the model referral comment wasn't there. opw-3880510
Original PR description
Issue ---- POS payment methods that are already translated don't have their translation show up. Steps ----- Go to Point of Sale -> New/Continue Session -> Add something to pay for -> Click on "payment". The listed payment methods are not translated if you chose another language. Cause ----- Although the terms were translated, they were not showing up because the model referral comment wasn't there. opw-3880510
A spacing issue in the Mexican EDI payment report has been corrected where a space was missing between the VAT label and account information. The fix adds consistent styling to ensure proper spacing between these elements, improving the readability and professional appearance of payment reports.
Original PR description
In the payment report, a space was missing between the VAT label and the span "Emitter Acc. Ben.". In order to don't rely on spaces, a ps-1 class was added in both "Emitter Acc. Ben." and "Emitter Acc. Ord.". --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/enterprise#53722
This fix addresses a performance test failure in the Appointment module where database queries were exceeding expected limits. The issue occurred when the Appointment module was tested in isolation, and the fix ensures consistent test conditions by warming up the cache to prevent unexpected query increases from being missed in future updates.
Original PR description
Before the commit the [appointment single module build](https://runbot.odoo.com/runbot/build/66250461) is breaking due to query_count being more than 9 (11) The increase was introduced in b3487219c070cdc03c933d92bc0d362ad733e11f in `_unavailable_intervals_batch`. It wasn't detected because the are less queries in the standard build all modules installed) because of a warmer ormcache. (get_lang) This commit proposes to warmup the test in all case to avoid the extra queries when appointment is installed alone, hopefully avoiding to miss the increased query count next time.