Daily updates from Odoo
Friday, July 5, 2024
3 changes · saas-17.2
Resolved issues and error corrections
Stock lots will now use the company linked to their related product by default, even when another default company is present in the workflow. This prevents lots from being assigned to the wrong company or getting a company when they should not, improving accuracy in multi-company inventory operations.
Original PR description
Now that lots can be set without company, we want them to have by default the company of their related product. The issue is that if there is a `default_company_id` set in the context at any point, it will prevent the computation of the right `company_id`, causing the wrong company (or a company where there shouldn't be one) to be set on the lot. To prevent this, we simply pop the `default_company_id` from the context if present when checking the default values, forcing the use of the compute instead. Also restores the `default_company_id` in `action_generate_lot_line_vals`, as this removes the default from move lines, and is no longer necessary for lots. Description of the issue/feature this PR addresses: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where the starred message counter could stay outdated in another browser tab after a starred message was deleted. The counter is now updated from the server, so users see a consistent and reliable count across tabs.
Original PR description
Before this PR, the star message counter was not updated on message deletion on tabs that were unaware of the message. Steps to reproduce the issue: - Open two tabs and log in as admin. - Star a message; the counter should show 1 on both tabs. - Reload one tab without accessing the channel. - Delete the starred message from the other tab. - Notice that the star counter on the second tab still shows 1. The issue arose because the client-side star counter updated based on partial information, specifically only when the message was starred. If the message had not been fetched, this information was unavailable. This PR resolves the issue by removing the client-side computation and implementing a server-side notification instead. runbot-61305,62004
Fixes an issue where applicants entering an invalid LinkedIn URL on a job application briefly saw a warning that then disappeared. The warning now remains visible when needed, helping applicants correct their information before submitting.
Original PR description
steps to reproduce -go to host/jobs -go to any job -put a wrong linkedin url -> the message is not displayed (after a blink) reason https://github.com/odoo/enterprise/pull/65011 this pr adds a js function (checkRedundant) that remove the warning message no matter what if its check are successful fix adds a condition and parma to check if the warning message should be removed or not task-4010892 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