Daily updates from Odoo
Wednesday, November 27, 2024
7 changes
2 changes
Resolved issues and error corrections
Amazon order processing tests now fail clearly when an order-processing error occurs instead of hiding it through an automatic rollback. Test data was also corrected so invalid Amazon order identifiers are caught, improving confidence that Amazon sales workflows behave as expected.
Original PR description
While testing, if we get an error while trying to process an order, `rollback` is called, we prevent this by raising the exception. Moreover, in the test data, the AmazonOrderId was a dict instead of a string, that error was silently ignored (test passed, but shouldn't).
This update adjusts an internal timesheet test after company-based employee access rules were restored. It helps ensure timesheet functionality continues to be validated correctly in multi-company setups, with no direct change expected for everyday users.
Original PR description
This reverts commit 73223682daaaa6d2ed2f062705917a59716209b4 since the multi-company rule in `hr.employee` and `hr.employee.public` models has been re-introduced.
3 changes
Resolved issues and error corrections
This fixes an issue in automated website editor walkthroughs where actions could lose track of earlier input changes between steps. Keeping the action context consistent from the start makes these tours more reliable and helps prevent false test failures around link editing.
Original PR description
The setupEventActions defines an element (environment) in which the history of actions is retained. If this element changes at each step of the tour, then it is for example not possible to "blur" a previously altered input. This environment must be defined at the beginning of the tour.
The portal chatter setup no longer shows an error just because a user cannot access a related discussion at initialization. Access is still checked when messages are actually loaded, reducing false failures while preserving the normal permission checks.
Original PR description
Since the `chatter_init` route is only responsible for checking the valid partner in the case of a public user, there is no need to raise `NotFound` if there is no access to the thread. Checking for access to the thread and raise if it's needed is done when fetching the messages. reported on [this build error](https://runbot.odoo.com/web/#id=99087&menu_id=405&cids=1&model=runbot.build.error&view_type=form)
The Gantt view now handles cases where certain time scales, such as month or year, are not available but still selected. This prevents users from seeing a crash and keeps planning views usable with customized configurations.
Original PR description
The attribute scales of the gantt view specifies which scales are available in the view. This means that for instance "year" or "month" can be absent from scales. If that happens and that "year" or "month" is the selected range, a crash occurs when rendering the GanttRendererControls component:
TypeError: Cannot read properties of undefined (reading 'groupHeaderFormatter')
Here we assign to each range a function groupHeaderFormatter so that we can call it independently from the available scales.2 changes
Resolved issues and error corrections
This update fixes a problem where some Odoo clients using Quadrum or SW Sapien were receiving rejected CFDI invoices due to excessive schemaLocation headers. The change now only includes the necessary headers, ensuring invoices comply with Mexican tax regulations and avoid rejection.
Original PR description
Problem: ======== when using pacs : Quadrum, SW Sapien some clients get their CFDI rejected because the schemaLocation is is containing more headers than needed. Solution: ========= We will only keep the needed schemaLocation for customer invoice, so headers for Payment and External Trade will be removed. opw-4168509 Forward-Port-Of: odoo/enterprise#72450
This update ensures that tests for the account import process run consistently, regardless of whether the `xlrd` library is installed. Previously, tests were skipped when `xlrd` was available, leading to unreliable test results. This change utilizes `openpyxl` for XLSX files, guaranteeing test execution.
Original PR description
Since `xlrd >= 2.0` dropped XLSX support, we use `openpyxl` to open XLSX files if the `xlrd >= 2.0` is installed.[^1] However, the tests in `account_base_import` are skipped unless `xlrd.xlsx` can be imported. As a result, they are not run on runbot, where `xlrd >= 2.0` is installed. We therefore need to avoid skipping them if openpyxl is installed. runbot-108001 [^1]: https://github.com/odoo/odoo/pull/169245 Forward-Port-Of: odoo/enterprise#74608