Daily updates from Odoo
Friday, February 16, 2024
11 changes
4 changes
Resolved issues and error corrections
This fix ensures country-specific payroll modules load with the right payroll and accounting dependencies. It helps prevent installation or configuration issues when companies use localized payroll features without needing unnecessary accounting components.
Original PR description
l10n_xx_hr_payroll shouldn't depend on account and should depend on hr_payroll l10N_xx_hr_payroll_account should depend on l10n_xx_hr_payroll and account
This fixes a setup issue in the US payroll accounting test module when demo data is not installed. It prevents no-demo test builds from failing because the module incorrectly assumed demo company data was available.
Original PR description
When no demo data, we still have the main_company. It causes an issue when installing this module, as it expects the demo data. The whole no demo data build fails because of it. We should change what we make the check on.
This fix removes a duplicate Lithuania-specific Intrastat region setting because the same setting is now managed centrally. It helps keep accounting configuration consistent and reduces the risk of conflicting setup options.
Original PR description
In the previous commit https://github.com/odoo/enterprise/commit/77ff6f595d5c6f2ec297b7dddff866a77e3b87ed, the field intrastat_region_id was moved from l10n_be_intrastat to account_intrastat. The l10n_lt_intrastat localization was forgotten and is being removed in this commit. The field intrastat_region_id can indeed be defined only once in account_intrastat instead of all localizations. The view of the intrastat region (visible in the settings) was defined in account_intrastat, and is therefore no longer needed specifically in the l10n_lt_intrastat module task-3691571
Restaurant table bookings now process correctly when they arrive through live notifications. This prevents errors that could interrupt booking updates in the point-of-sale restaurant appointment flow.
Original PR description
When receiving websocket message with a new table booking, we tried to access the pos_store object from the wrong variable, which caused an error. Is now fixed by using the correct variable.
7 changes
Resolved issues and error corrections
This update improves how appointment types are displayed on the appointment page by automatically sorting published appointments first. This makes it faster and easier for staff to find and access the most important appointments without having to search through unpublished options.
Original PR description
This PR changes the order of appointment types on the appointment page based on the appointment's published status. This makes it easier for internal users to access published appointments first. Task-3725160
This update fixes missing translations for three key terms ("gain", "loss", and "gain/loss") in the asset modification wizard. These terms are now properly translated for users in different languages, ensuring a consistent and professional experience across the accounting asset management features.
Original PR description
Fix translation for account_asset / wizard There was fixed strings without translation - gain - loss - gain/loss
This fix corrects the error message that appears when a subscription code is already linked to another database. Previously, the message wasn't displaying properly, making it unclear to users what action to take. Now the helpful guidance message will display correctly, improving the user experience when managing subscription codes across multiple databases.
Original PR description
When a subscription code is already linked to a database and you try to use it on another database, the message displaying that this subscription code is already used and provides the informations of what to do is not correctly displayed. Forward-Port-Of: odoo/enterprise#56618 Forward-Port-Of: odoo/enterprise#47326
This update adds the required XML declaration to the Belgian intrastat XML report. A Belgian partner identified that the XML report was missing the proper XML declaration header, which is now included to ensure compliance with XML standards and partner requirements.
Original PR description
We got a feedback from a Belgian partner that we don't have a xml declaration in the xml report. opw-3745820 Forward-Port-Of: odoo/enterprise#56764 Forward-Port-Of: odoo/enterprise#56727
This update changes how Odoo organizes its internal module list from an unpredictable set to a sorted list. This ensures that tests run consistently and reliably, fixing issues where security tests were failing randomly due to module order variations. The change is internal and won't affect how users interact with Odoo.
Original PR description
Make the set() of module sorted, aka a list. We can be pretty sure that nobody relied on the order of this set before since it was completely underterministic. Therefore this change should not break anything and make the testing on runbot more consistant. This is mainly following the issue with the sql-injection testing failing randomly with the order of the modules. Forward-Port-Of: odoo/odoo#154140
This update fixes access control settings for Polish tax office information in the accounting module. A field that references tax office data now properly enforces the same access restrictions as the underlying tax office model, making the system more secure and eliminating test warnings.
Original PR description
The model `l10n_pl_tax_office` has a group to be able to access it. The Many2one that refers to it, `l10n_pl_reports_tax_office_id`, does not. Currently, it is not really an issue as the accounting's settings are invisible if you don't have the group, but it creates a warning in a test and is more robust Linked to runbot error 24602, 24721 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#154215 Forward-Port-Of: odoo/odoo#153660
This update prevents the web interface from crashing when it encounters permission errors while checking stylesheets for compilation issues. The system now gracefully handles these errors instead of failing, ensuring a more stable user experience when stylesheet features are restricted.
Original PR description
This commit follows [1], which attempted to fix CORS errors occurring when we access the `cssRules` property of stylesheets, to detect scss compilation errors and display a warning to the user. [1] doesn't seem to be enough, as we faced another source of CORS errors. Indeed, in non-secure http, the error is raised even if the origin is the same. We never want this access to crash anyway, as it's a nice to have feature, and if reading `cssRules` is forbidden, there's nothing the user can do anyway. For those reasons, we decided to simply protect the code with a try/catch. [1] odoo/odoo#152696 opw 3746910 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