Daily updates from Odoo
Wednesday, October 16, 2024
20 changes
1 change
Resolved issues and error corrections
When adding new content to an online course with multiple sections, the system now automatically selects the most recently created section if no section was chosen. This reduces extra clicks and helps course editors continue adding content in chronological order.
Original PR description
Purpose ======= When users are editing course content and created multiple sections they are most likely working "chronologically" adding content to sections one after the other. It seems the fix to preselect last section by default when many exist to populate new content is in regression. How to fix ========== Whenever a channel has sections and users has not selected one: make the last section as the default one. task-4109586 see odoo#132934 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
19 changes
Resolved issues and error corrections
The Discuss onboarding tour is now included in the correct application assets instead of being limited to test-only files. This ensures users can see the intended onboarding guidance when using Discuss, improving first-time user orientation.
Original PR description
The discuss onboarding tour was missing because it was in the tests assets. It has been moved and change for the new system of onboarding tour. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The sales order confirmation warning now better explains what to do when an order was created before a warehouse existed. This helps users resolve the issue by assigning the warehouse to the order instead of repeatedly being told to create one.
Original PR description
### Steps to reproduce: - Create a new company - With this new company, create an SO for a storable product - Try to confirm the SO #### > A redirect warning is raised: "Please create a warehouse…
### Steps to reproduce: - Create a new company - With this new company, create an SO for a storable product - Try to confirm the SO #### > A redirect warning is raised: "Please create a warehouse ..." - Go to warehouses and create such a warehouse - Try to confirm the SO once more #### > The same warning is raised: "Please create a warehouse ..." ### Cause of the issue: The redirect warning that asks you to create a warehouse is raised when you try to confirm an SO wihtout a set "warehouse_id": https://github.com/odoo/odoo/blob/114b476755c37ae670f613200ffcc03377258873/addons/sale_stock/models/sale_order.py#L102-L113 https://github.com/odoo/odoo/blob/114b476755c37ae670f613200ffcc03377258873/addons/stock/models/stock_warehouse.py#L166-L172 Since you created the SO before the warehouse, the SO is curently not linked to any warehouse. Furthermove, when you created the warehouse, it did not update the 'warehouse_id' so that the exact same warning will be raised after the warehouse creation. opw-4250791 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website task creation form preview no longer crashes when opened directly without an existing task. This helps website editors test and configure forms more reliably.
Original PR description
Currently, an exception is generated when the user clicks on the preview URL of the "Create a Task" form by following the steps: - Go to any website page and open the website editor - Add form to website page - click on the added form and select Action as "Create a Task" - Click on the Preview URL button of the added form >> errro generated Error `KeyError: 'task'` This is because when the user opens the direct URL, no task is available. This commit will fix the above issue by accessing the key `task` when it is available in view. sentry-5983056185
This update prevents manufacturing report logic from accidentally mixing up an input value while processing operations. It helps keep bill of materials structure reporting consistent and reduces the chance of incorrect results in manufacturing views.
Original PR description
This commit makes sure `operation` parameter is not reused in the `for` loop. 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
This fixes an issue where videos used as the cover media in website Card snippets could appear shifted or fail to fill the card correctly when a fixed ratio was applied. Website editors can now replace card cover images with videos and expect the layout to remain consistent.
Original PR description
In the "Card" snippet, if the cover image is replaced by a video, and if it has a ratio (i.e. the "Ratio" option is not set on "Image default"), the video is not placed correctly. This happens because the videos have a rule setting their position to `relative`, overriding the `absolute` position set and needed by the `ratio` class. This commit fixes that by setting the position of card cover videos as `absolute`, to be placed correctly according to the ratio. Steps to reproduce: - Drop a "Card" inner snippet. - Click on the cover image and replace it by a video. => The video is shifted and does not fill the wrapper properly. Related to task-3674888
This fix prevents Odoo from automatically opening a default form view in list screens unless the user is creating a new record or the action explicitly requests it. This avoids confusing navigation in certain list views while preserving the intended behavior for dedicated open-form buttons.
Original PR description
This commit tweaks the behavior of the openFormView function introduced in https://github.com/odoo/odoo/pull/176707 by making it fallback on the default form view only in create mode or when the caller explicitly wants it to (using the force parameter). This solves issues with some list views where we don't want to show the form view on click while keeping the spec intact in case of list's open_form_view button. Task-4164683
This fixes an issue where scrolling an open Gantt popover out of view could trigger an error while it was closing. The change improves stability by ensuring the interface only repositions popovers when the required page elements are still available.
Original PR description
Since [1] have a gantt popover opened and then scroll the popover out: a traceback occur due to the onPositioned callback still called when the popover is being closed. Now usePosition will check if needed elements are connected before the positioning computation. [1]: https://github.com/odoo/enterprise/commit/ebeb633be737eb7bd614c2b474fafd65cd54f0ae
This update corrects a leftover internal reference in the hardware drivers used for customer-facing displays. It helps ensure connected display devices continue to launch and use the browser state correctly after a previous cleanup.
Original PR description
In #183565 the `chromium_additional_args` variable was removed, however a reference to it was missed in `DisplayDriver_L`. This PR fixes this reference by replacing it with `browser.state`. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Sales orders that open tasks from the Tasks button now show the expected project navigation bar when all tasks belong to the same project. This restores easier navigation for users moving between a sales order, its project, and related tasks, while keeping the previous behavior when tasks span multiple projects.
Original PR description
Steps to reproduce: ------------------- 1. Install Project and Sales app 2. Create an SO which generates a project with tasks on confirmation 3. Confirm the SO 4. From the SO form view, click on the 'Tasks' stat button 5. The top bar is unavailable Fix: ------------------- In the action method, we check if all the tasks linked to the SO are in the same project. If so, we display the top bar by retrieving the right xml_id and passing the active_id of the project in the context. If not (more than one project), we fall back on the current behaviour. task-4239673 version-18.0 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users verifying Indian E-waybill credentials in production will now see a clear validation message when the username or password is incorrect. This prevents a confusing system error and makes it easier to correct setup issues during accounting configuration.
Original PR description
Before this PR, if the E-waybill credentials are wrong, the user gets a traceback in the production environment due to 61a85754800. Instead we introduce a `ValidationError`. Steps to reproduce: - Turn On (✓) "Production Environment" and "Indian Electronic Waybill" from accounting configuration settings. - Click "Verify Username and Password" in "Indian Electronic Waybill".
This fix ensures users can save email templates when using the mass mailing composer. If the composer cannot be saved first, the system now stops and shows the normal validation guidance instead of continuing into a broken template creation flow.
Original PR description
In the new composer design [1] saving a template is done by first saving the composer, then opening the "template creation" view on the same composer. The second step thus requires the composer to be properly saved first. This is easily checked as `Record.save` returns false on failure. In that case we do nothing and let the framework point out why the record could not be saved. [1]: 6c4526ec3b9509e0a6b99503d8d888417b2695e0 task-4246399
Dashboard administrators are now automatically treated as internal users, preventing permission mismatches that could break dashboard-related tests or setup flows. This keeps administrator access consistent and avoids errors caused by dashboard admins being treated like portal users.
Original PR description
With this commit, all Dashboard Admins are also automatically internal users. Steps to reproduce: - install module spreadsheet_dashboard_edition - run test `.test_session_info_with_right` => the test fails because of a combinaision of two factors: - the user is granted the group `group_dashboard_manager` but he is not an internal user (which means he is a portal user) - `_inverse_calendar_res_users_settings` creates `res.users.settings` for portal users (will be fixed independently) and it crashes in the readonly transaction --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Web Studio onboarding tour now appears correctly for users. This helps new or returning users discover Studio features as intended, improving guidance without changing core business workflows.
Original PR description
The studio onboarding tour was missing because it was in the tests assets. It has been moved and change for the new system of onboarding tour.
The update fixes an internal Documents test so it handles users who already belong to another company. This helps keep access-rights checks reliable in multi-company setups without changing everyday user behavior.
Original PR description
This commit fixes the test. When there is extra company then test is failing because it replaces the companies in user, instead of adding the new company.
This fixes an internal issue that could incorrectly shorten sorting rules used in grouped views and reports. The change helps ensure accounting and document lists are ordered consistently when custom sorting logic is involved.
Original PR description
`_read_group_orderby` used `cr.mogrify`, `split(",")` and `split()[0]` for the
result coming from the `_order_to_sql` which may come from `_field_to_sql`
As a side effect, SQL code after a space/newline not adjacent to a comma will
be dropped after `split()[0]`. So the mogrified customized `_field_to_sql`
shouldn't have any space/newline not adjacent to a comma if the field is used
for `Model._order`.This update corrects how withholding reference information is read in the Indian TDS/TCS reporting module. It helps ensure the report uses the right linked accounting records and avoids errors caused by incomplete field access.
Original PR description
With this PR, field `l10n_in_withholding_ref_move_id` will be accessed with `mapped` from the record set which was missing in the commit https://github.com/odoo/enterprise/commit/69e5817f5c72b75f3879801364ca78c83b522f83
The SEPA direct debit mandate report layout has been adjusted so it prints on a single page. This helps users generate cleaner, more professional documents without awkward page breaks.
Original PR description
Adapt the layout of the account sepa direct debit report to make it fit on a single page. task-4183056
Users who try to validate the same project document twice will now see a clear invalid operation message instead of an unexpected error. This prevents disruption and makes the issue easier to understand and resolve.
Original PR description
Steps to Reproduce: 1. Select a document 2. validate document 3. click on validate again 4. Traceback thrown Technical Reason: Instead of raising a UserError, it throws a ValueError when evaluating directly '_()' in the XML file without using the 'env' context. After this commit: An invalid operation dialog will open with the message 'Impossible to validate twice'. Task-4228827
Manufacturing users can now post work-in-progress accounting entries even when a work order has been started but not yet given an end time. This avoids an unexpected error and helps keep manufacturing accounting actions from being interrupted.
Original PR description
before this commit, if user tries to open/generate WIP entry for manufacturing without recording the end time in the time tracking inside the work order a traceback is shown to user * create a manufacturing order that generate work order * in the work orders generated, start a work order * now click on POST WIP accounting entry from action * traceback is shown after this commit, no traceback wont be shown in the above scenario