Saturday, April 20, 2024
6 changes · saas-17.2
Miscellaneous changes
The blogs filters in mobile is breaking the layout. This PR applies a dropdown instead which is displayed next to searchbar. Additionally it adapts the spacing to make it even between the navigation component. A SCSS override is necessary to counter the pseudo elements introduced in portal. This is fixed in 17.0 with this commit[1] but it was decided to not backport this fix and apply the override on blog instead for 16.0 -> 16.4 to avoid breaking any website customization. For >= 17 w
Original PR description
The blogs filters in mobile is breaking the layout. This PR applies a dropdown instead which is displayed next to searchbar. Additionally it adapts the spacing to make it even between the navigation component. A SCSS override is necessary to counter the pseudo elements introduced in portal. This is fixed in 17.0 with this commit[1] but it was decided to not backport this fix and apply the override on blog instead for 16.0 -> 16.4 to avoid breaking any website customization. For >= 17 we might consider offcanvas instead (such as the event page). [1] odoo/odoo@b6a747239a01eca192810a2ff782a0b952e2a05a task-3315921 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#157757 Forward-Port-Of: odoo/odoo#145547
The aim of this commit is to allow user to install `account_peppol` without facing a traceback. Context: The commit cffd0e9dd91376dd7fe4613f4fd94e659daaeef0 introduced a check based on a field introduced in the view by another module it depends on. The problem is that ticking the peppol checkbox install the `account_peppol` module but doesn't trigger an update of the `account_edi_ubl_cii` module. Before the commit: Impossible to installing `account_peppol`. After the commit: Insta
Original PR description
The aim of this commit is to allow user to install `account_peppol` without facing a traceback. Context: The commit cffd0e9dd91376dd7fe4613f4fd94e659daaeef0 introduced a check based on a field introduced in the view by another module it depends on. The problem is that ticking the peppol checkbox install the `account_peppol` module but doesn't trigger an update of the `account_edi_ubl_cii` module. Before the commit: Impossible to installing `account_peppol`. After the commit: Installing `account_peppol` will update the view `account_edi_ubl_cii.account_move_send_form` if the field added by commit cffd0e9dd91376dd7fe4613f4fd94e659daaeef0 can't be found. opw-3874304 Forward-Port-Of: odoo/odoo#162677 Forward-Port-Of: odoo/odoo#162598
The first commit is about the display of the address block, we always had the address of the partner even if the address were the same. Now, depending on the address in the customer field or delivery address, we can decide to display the invoicing address or shipping address or both. The other one is about the size of the footer because the general scaling of the footer font is too big. Normal Sized company names cannot be displayed. In Fact, the Iban numbers etc. are cut off at the bottom.
Original PR description
The first commit is about the display of the address block, we always had the address of the partner even if the address were the same. Now, depending on the address in the customer field or delivery address, we can decide to display the invoicing address or shipping address or both. The other one is about the size of the footer because the general scaling of the footer font is too big. Normal Sized company names cannot be displayed. In Fact, the Iban numbers etc. are cut off at the bottom. task: 3817563 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#162557
This commit improves the performance of the reference check for large categories of Units of Measure (UoM). After this commit, the number of UoMs in the category is counted using the read_group method instead, resulting in faster performance. ### Benchmark: | Nbr of UoM | Before | After | | ---------: | -----: | ----: | | 0 | 0ms | 0ms | | 1 | 1ms | 1ms | | 30 | 6ms | 3ms | | 200 | 7ms | 2ms | | 18000 | 900ms | 15ms | opw-
Original PR description
This commit improves the performance of the reference check for large categories of Units of Measure (UoM). After this commit, the number of UoMs in the category is counted using the read_group method instead, resulting in faster performance. ### Benchmark: | Nbr of UoM | Before | After | | ---------: | -----: | ----: | | 0 | 0ms | 0ms | | 1 | 1ms | 1ms | | 30 | 6ms | 3ms | | 200 | 7ms | 2ms | | 18000 | 900ms | 15ms | opw-3775689 Forward-Port-Of: odoo/odoo#162540 Forward-Port-Of: odoo/odoo#157752
## Steps to reproduce: 1. Go to IoT > Devices 2. Select a device and add the report "Lot/Serial Number (ZPL)" 3. Create a product tracked by lots 4. Purchase 5 units of this product 5. Validate the reception (with a lot) 6. Print labels > Lot/SN Labels - Quantity to print: One per unit - Format: ZPL Labels ## Before this commit: When printing labels for multiple lots of the same product, the wizard was incorrectly generating the docids as a `list[list[int]]`. It works corre
Original PR description
## Steps to reproduce:
1. Go to IoT > Devices
2. Select a device and add the report "Lot/Serial Number (ZPL)"
3. Create a product tracked by lots
4. Purchase 5 units of this product
5. Validate the reception (with a lot)
6. Print labels > Lot/SN Labels
- Quantity to print: One per unit
- Format: ZPL Labels
## Before this commit:
When printing labels for multiple lots of the same product, the wizard was incorrectly generating the docids as a `list[list[int]]`. It works correctly as the ids are joined thanks to JavaScript magic. However, when sending the report to an IoT device, the ids are sent as-is in the context, which raises an error when calling `browse()`.
## After this commit:
The docids are now generated as a flat list of integers, which is correct and works as expected.
opw-3850631
Forward-Port-Of: odoo/odoo#162063
Forward-Port-Of: odoo/odoo#161932Appointment slots are not reflected in the gantt view so there are no indications of whether an appointment is within a valid time period with regards to the appointment-defined time intervals. This commit adds slot intervals in gantt availabilities display and attempts to have more common ground between slots and gantt. task-3813567 Forward-Port-Of: odoo/enterprise#61033 Forward-Port-Of: odoo/enterprise#60100
Original PR description
Appointment slots are not reflected in the gantt view so there are no indications of whether an appointment is within a valid time period with regards to the appointment-defined time intervals. This commit adds slot intervals in gantt availabilities display and attempts to have more common ground between slots and gantt. task-3813567 Forward-Port-Of: odoo/enterprise#61033 Forward-Port-Of: odoo/enterprise#60100