Thursday, August 8, 2024
6 changes · saas-17.4
Resolved issues and error corrections
This fix prevents an error when users create a new view from the view list using the New button. It ensures the system handles newly created, unsaved view records correctly, allowing the creation flow to continue without interruption.
Original PR description
Description of the issue/feature this PR addresses: An error is thrown when trying to create a new view by clicking the "New" button on the ir.ui.view list view. This is due to the NewId value not registering as an ID on the record, which subsequently causes the query generated by the _get_inheriting_views method to be invalid as it will attempt to execute a query with a where clause like this: "WHERE id IN ()" For a new view, this method will always return an empty list, so this PR aims to handle this specific case by checking if the records id is an instance of models.NewId, and if so simply setting the value to be an empty list instead of executing the query. Current behavior before PR: Error thrown on creation of new ir.ui.view record from the list view Desired behavior after PR is merged: No Error Task-ID: 4102663 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The message status tooltip now shows "Sent" when a message has been delivered but not yet seen by anyone. This prevents confusing placeholder text from appearing in chat and gives users a clearer status indication.
Original PR description
Before this commit, the tooltip shown upon hovering the single tick on a sent message showed "undefined". Steps to reproduce: - Send message on a chat with user demo as admin - Log in as user demo - As the admin user hover the single tick on the message This happens because the switch case is not covering the case of the message being fetched but not seen by anybody. This commit fixes the issue by adding a case for such instance, showing "Sent" as the tooltip. Before:  After: 
Fixed an issue where creating a delivery address or contact from a company record could incorrectly mark the new contact as a company. This prevents confusion in contact lists and keeps company/contact categorization accurate.
Original PR description
Steps to reproduce: - Contact > Any company > Contacts and Adresses tab - Create a new delivery adress - Save The delivery adress will be displayed as a company (building icon). In 17.2 and before, is_company used to be passed in the value list upon record creation, this is not the case anymore. Because the defaults are pulled from the parent company, this turns any contact created from a company's form into a company which does not make sense. This fix restores one of the view's invisible fields, but several others were deleted to be inherited from the parent company. (see this commit 855560ed2e21c445c110a948669e336305f29c4c). opw-4072057 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an error that appeared when users tried to create a new record from the selection field on the link tracking page. The change restores a smoother workflow by ensuring the creation action calls the system correctly.
Original PR description
Purpose ======= Fix the traceback appearing when trying to create a new record using the select2 on the tracking page "/r". Specification ============= The "find_or_create_record" method takes 3 arguments but 4 were given. The first given argument (an empty array) isn't needed to call the method. related commit: 68dc5be8279bc8e9cb4614bb774637ddd78aba83 Task-4100264 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes an error that appeared in debug mode when using the Go To button in the Restaurant Point of Sale navigation bar. It ensures the number entry popup handles validation correctly, reducing interruptions for staff and testers using restaurant floor navigation.
Original PR description
Steps to reproduce: 1. Open a restaurant pos config with debug mode 2. Click on the `Go To` button in the navbar 3. Observe the error about the prop with the wrong value --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix updates the India payroll demo data to use the current official Kolkata time zone name. It prevents build or setup failures on newer Ubuntu environments where the older Calcutta time zone name is no longer available.
Original PR description
Asia/Calcutta was removed in ubuntu Noble in favor of Asia/Kolkata This is only visible in the pure noble build and not in the standard build. The assumption is that since requirements are installed as root, the tz is added when installing the pip package. Since we will soon install requirements as odoo on runbot in the docker image, this should will start to break in standard builds too.