Wednesday, January 28, 2026
105 changes
2 changes
Resolved issues and error corrections
This update resolves an issue where the IoT Box was incorrectly downloading standard drivers, potentially causing conflicts and outdated versions. A new setting allows custom drivers to be downloaded, but this change has been adjusted to avoid overwriting existing drivers and introducing previous bugs. This ensures a more stable and reliable IoT Box experience.
Original PR description
The stable IoT Box uses drivers from git repository: it doesn't download them from the database as it used to do. However, sh/on premise clients might want to develop custom drivers that the IoT Box would download. For that, they have to enable a checkbox on the IoT homepage, making the IoT Box download handlers as before. The issue is it will also download standard drivers that are already present on the IoT Box: on newer databases it would simply overwrite them, but on older ones, it would duplicate as names might have changed. Also, it would introduce issues back that were already fixed. To avoid this, we avoid adding drivers from standard modules to the downloaded archive, to prevent issues with the main ones. Forward-Port-Of: odoo/enterprise#105686 Forward-Port-Of: odoo/enterprise#105531
A recent bug in the Point of Sale appointment tour was causing it to fail when tests were run close to midnight. This was due to the system scheduling appointments for the next day, which the POS frontend then filtered out. This fix ensures the tour functions correctly regardless of the time of day.
Original PR description
The `test_pos_restaurant_appointment_tour_basic` test was failing when run late in the day. The test creates an appointment 30 minutes in the future and expects a corresponding label to appear underneath the table in the POS floor plan. However, if the test is executed near midnight (e.g. 23:45 UTC), the appointment is scheduled for the following day. Since the Point of Sale frontend only displays appointments for the current day, it filters the booking out, causing the tour to timeout while waiting for the label. runbot-232601 Forward-Port-Of: odoo/enterprise#105738
2 changes
Resolved issues and error corrections
This update fixes a technical issue where Greek translations were incorrectly using the 'gr' language code instead of the correct 'el' code. This ensures that all Greek language content within the Odoo Enterprise system is accurately translated and displayed. The fix was part of a larger effort to improve the consistency of our internationalization efforts.
Original PR description
~~Modules added into stable without being properly added to .weblate.json file = never translatable.~~ Fix Greek translations using the wrong language code. `gr` => `el` Forward-Port-Of: odoo/enterprise#105578 Forward-Port-Of: odoo/enterprise#104890
A recent bug in the Point of Sale appointment tour was causing it to fail when tests were run close to midnight. This was due to the system scheduling appointments for the next day, which the POS frontend then filtered out. This fix ensures the tour functions correctly regardless of the time of day.
Original PR description
The `test_pos_restaurant_appointment_tour_basic` test was failing when run late in the day. The test creates an appointment 30 minutes in the future and expects a corresponding label to appear underneath the table in the POS floor plan. However, if the test is executed near midnight (e.g. 23:45 UTC), the appointment is scheduled for the following day. Since the Point of Sale frontend only displays appointments for the current day, it filters the booking out, causing the tour to timeout while waiting for the label. runbot-232601 Forward-Port-Of: odoo/enterprise#105738
1 change
Resolved issues and error corrections
This update ensures that the employee's current location field is consistently included when views are generated, particularly in situations like creating many-to-many relationships in Studio. Previously, this data was sometimes missing, causing issues. This fix guarantees accurate location information is available across all views, improving data consistency and reporting.
Original PR description
Before this commit, the feature at commit odoo/odoo@b3be3af61cc08d0dea84969425d24957f215b26f worked by chance, because in most cases ALL fields where returned in the get views, since most of the time the search view is asked for as well, hence yielding all fields in the model There were issues when triggering get_views from another place, namely studio when creating a many2many. After this commit, we make sure the current day location field's description is sent opw-5484321 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 Forward-Port-Of: odoo/odoo#245740