Monday, June 24, 2024
12 changes · 17.0
Resolved issues and error corrections
This fixes an accidental change in the point-of-sale self-ordering interface by removing updates that were not meant to be included. It helps keep the customer ordering experience consistent and avoids unintended behavior from the earlier change.
Original PR description
The diff introduced here https://github.com/odoo/odoo/pull/170267 was absolutely not wanted. It needs to be removed opw-3787201 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update ensures the accounting tax lock date value is recalculated when its underlying tax lock date changes. It mainly improves reliability in automated tests and edge cases, with little expected impact on normal production use.
Original PR description
The field `max_tax_lock_date` is not always computed correctly. This is since the compute function does not depend on the `tax_lock_date` field. It should not happen in production since the `tax_lock_date` and the check of `max_tax_lock_date` should not happen in the same transaction. But it can still cause issues in tests. The missing dependency is added in this commit. enterprise PR (fixing a test): https://github.com/odoo/enterprise/pull/65262
The point-of-sale display now checks connected IoT devices much less often, changing from near-constant requests to once per minute. This reduces unnecessary load on devices and the system while keeping device status updates available.
Original PR description
Increased delay between every request to iot_devices. Requests were performed every 10ms, now every minute.
New project setup now correctly carries over the configured email alias domain when the setup wizard opens. This prevents missing default values and helps ensure project-related email routing uses the expected company setting.
Original PR description
Steps: - Install the project - Enable use custom enable server from general settings. Set an alias domain - Create a new project - Wizard pops up Issue: - Default value of alias domain is not set. Cause: - alias_domain_id is related to alias_id and it is not present in the view. Fix: - Issue is been fixed by adding a field in wizard view as alias domain was getting fetched on that field. - Additionally the same field is been to added to form view as well. task-3744319
This fixes an error that could occur when users cancelled a filter in a project burndown chart. The change helps keep project reporting views stable and prevents an unnecessary interruption during chart analysis.
Original PR description
Description of the issue/feature this PR addresses: - When a user cancels a filter on a burndown chart, if stageIdSearchItemId is undefined, an error is raised. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Creating a company and installing an accounting chart template before setting a country no longer causes an error. The company country is now aligned with the selected chart template, helping users complete setup smoothly.
Original PR description
Before this commit, when creating a company and directly installing a chart template without putting a country first, the installation of the chart template was giving a traceback. By updating the country of the company by the one of the chart template, the issues will not happen again. task: 3945833 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents the website editor from crashing in debug mode when users adjust a snippet's color filter after adding a background image. It ensures opacity values are handled in the expected format, making the editing experience more reliable.
Original PR description
Since [1], `opacity` needs to be a number as defined in ColorPlaette's props definition. However, in the ColorpickerUserValueWidget, when the props is passed to the ColorPalette component, it is given from the dataAttributes, which are strings. This leads to a crash in debug mode as the types are miss-matching. This commit fixes that by parsing the dataAttribute to float. [1]: https://github.com/odoo/odoo/commit/d7245d2abf528d093226c80e40975e63d61e8997#diff-c4e4c8cbbe59c3e61eba1cdcfd8f23809818a0b78c118d84606a1ab5d7bf1203 task-4001189
This fixes list views so columns with set widths no longer stretch unexpectedly. Business users get more predictable table layouts, making records easier to scan and reducing visual disruption in everyday workflows.
Original PR description
// TODO if validated Task 3866837 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 update fixes a test in the Luxembourg tax reporting module that was not properly respecting tax lock date restrictions. The fix ensures the test will continue to work correctly after an upstream improvement to tax lock date validation. This is a maintenance update that prevents test failures and ensures the tax reporting system functions as intended.
Original PR description
Currently the tax lock date is not checked correctly in a test when posting a move. This problem is solved in the related community PR. This commit ensures the test does not fail after the community fix. To do this we just remove and re-introduce the tax lock date. community PR: https://github.com/odoo/odoo/pull/170475
This update fixes a button contrast issue in the Sign module that was making text difficult to read. By removing an unnecessary styling class, the button now displays with proper contrast in both light and dark modes, improving the user experience without requiring any action from users.
Original PR description
This PR fixes a contrast issue on a primary button within the sign module due to a `text-white` class applied. The default button utility classes already provide a good contrast, meaning that adding extra class is not useful. To fix the issue, we simply remove the class from the button. task-3692048 | Light mode (`:focus` state) | Dark mode | |--------|--------| | <img alt="image" src="https://github.com/odoo/enterprise/assets/128030743/b73a2fe7-f802-4461-9015-16a2f4b46d92"> | <img alt="image" src="https://github.com/odoo/enterprise/assets/128030743/8354c78f-6525-4aef-9057-fdb706b3cd0d"> |
A recent system update automatically assigns a country to companies based on their chart template. This caused Peru sales tests to fail because document validation rules were unexpectedly triggered. This fix updates the tests to properly handle the new document requirement validation.
Original PR description
With this commit: https://github.com/odoo/odoo/pull/166896/commits/90088bd97ec096fa8c360868e3a1addef91bd4ce We automatically add the country of the chart template to the company if the company does not have one by default. This change had a side effect that in the context of the test "TestPeSales," the boolean field l10n_latam_use_documents on the journal was now set to True. The consequence of that was that the constraint _check_l10n_latam_documents was breaking since this constraint checks that for the posted moves that use documents, the move must have a document type and a document number. task: 3945833
This update configures the translation system to properly export Swiss payroll-related text for translation into other languages. By adding these terms to the translation configuration, the Swiss payroll module can now be fully localized, ensuring that payroll documents and communications are available in multiple languages for international teams.