Tuesday, December 3, 2024
11 changes · 18.0
Resolved issues and error corrections
Course editors can no longer insert embedded components, such as videos, into slide descriptions where they cannot display correctly on the website. This prevents users from saving content that appears valid in editing but is missing for learners.
Original PR description
Steps to reproduce ================== - Install website_slides - Go to eLearning > Basics of Gardening - Click on a line - Switch to the description tab - Type /video - Insert a video - Save - Click on the "Go to Website" action button - Click on the line that has just been edited => The video does not appear Cause of the issue ================== The new web_editor has a plugin system, and one option that is enabled by default is `embedded_components`. This option has been introduced in: https://github.com/odoo/odoo/commit/03f495c696030214c17e6479076571823513f60e According to the description, > It is forcibly set to `false` in HtmlMailField since embedded > components can only be rendered inside Odoo. Solution ======== Disable the embedded components opw-4329734
Worldline payment references are now kept within the provider's 30-character limit. This prevents hosted checkout requests from being rejected because the order reference is too long, improving payment reliability for affected transactions.
Original PR description
The hostedcheckout param `order.references.merchantReference` is limited to 30 characters [^1], so we must not exceed that size for wordline's payment.transaction reference. [^1]: https://apireference.connect.worldline-solutions.com/s2sapi/v1/en_US/go/hostedcheckouts/create.html?paymentPlatform=ALL --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Argentina withholding tax setup form now hides withholding-specific tax computation details when they do not apply. It also avoids forcing users to fill in a withholding tax field for regular customer or supplier taxes, reducing confusion and setup errors.
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
Opening another internal user's profile no longer triggers an access error related to calendar privacy settings. This keeps user administration smoother while preserving the existing privacy configuration behavior.
Original PR description
Before this commit, an access error was being triggered when opening the user form of different internal users than self. This happened because of the `compute_sudo` flag in the calendar_default_privacy computation function. The sudo flag was introduced for allowing the read of the ResUsersSettings configuration during the computation of calendar_default_privacy. Turns out that this flag is not needed, since the sudo() flags in the inverse function is already sufficient. Thus, we're removing it from the computation. Issue-from: odoo/odoo#183887
This fix prevents Odoo's web tour testing tool from listening for browser errors after a tour has already ended. It reduces false error reports in automated test runs, helping teams get clearer test results.
Original PR description
In this commit, we stop listening for errors that might occur asynchronously after the browser is stopped. This avoids having errors like: Exception received after termination: Uncaught (in promise)Event(isTrusted=true, type='error', target=null, currentTarget=null, eventPhase=0) runbot-error-id~70404 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
The Human Resources department organization chart now opens the employee list correctly when users click the employee-count button. This prevents an error in the department form and keeps navigation to department employees working as expected.
Original PR description
Step to reproduce: 1) Install the hr Application and open the form view of department 2) Clicking the gray button that shows the employee number in the department organization chart will result in an error Cause: The argument in the doAction function is incorrect; it should be an action record, not a Python function Solution: First, we retrieve the action using the ORM and then pass it to the doAction function as an argument. Task-4337876
This fixes an issue in the website editor where the image cropping preview could appear outside the visible window after placing content above an image. Users can now crop images without needing to scroll around to find the preview, making page editing smoother.
Original PR description
Following commit [https://github.com/odoo/odoo/commit/189a7c96e6e26825dc05c0c6466576fe63aa091e] which removed the scroll from the `#wrapwrap` element, the cropper offsets were wrongly calculated. Steps to reproduce: - Drop a random snippet - Drop an image snippet below the other one - Crop the image of the image snippet => The cropper preview is outside of the window, you have to scroll to reach it. [https://github.com/odoo/odoo/commit/189a7c96e6e26825dc05c0c6466576fe63aa091e]: https://github.com/odoo/odoo/commit/189a7c96e6e26825dc05c0c6466576fe63aa091e task-4190506 opw-4333004
This change removes a recently added test optimization that was using too much memory and could cause test runs to crash. It helps keep the web test suite reliable, reducing disruption for development and release validation.
Original PR description
This reverts commit 14b37d5871c97d93723dc925419fa93fa2fb8250. This is due to performance issues likely caused by the added template cache taking way too much memory and occasionnally crashing the test suite. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Planning kanban view now displays date ranges on a single line when users group or filter records. This makes schedules easier to read and avoids confusing split date information in planning cards.
Original PR description
Current Behaviour: - when grouping or filtering records in the planning kanban view, the daterange looks like displayed on two columns Expected Behaviour: - the daterange should be displayed as a single line Task-4273653
The payment form now shows the ISO 20022 reference field in a consistent position regardless of which bank account option is displayed. This reduces confusion for users reviewing or entering payment details.
Original PR description
The position of the `iso20022_uetr` field was defined as being after the `partner_bank_id` field in the view. However multiple of these fields were defined in the view using if/else conditions, and the former field was put after the first occurrence of the latter. So depending on which `partner_bank_id` field was shown, the `iso20022_uetr` field would be either before or after it. This commit makes it consistent and puts it after the last occurrence of `partner_bank_id`.
The Planning onboarding guide now prompts users to click the right controls when launched manually. It also handles the publish action more appropriately on mobile, reducing confusion during setup.