Thursday, April 3, 2025
5 changes · saas-17.4
Resolved issues and error corrections
This fixes an issue on mobile where navigating between records could show the previous pager number instead of the current one. Users now see accurate record positions when moving through list or kanban records, reducing confusion during mobile use.
Original PR description
Steps to reproduce ================== - Use a mobile viewport - Go to any list/kanban view - Open a record - Use the pager to switch to the next record => "1 / x" is displayed where x is the total amount of records - Click next => "2 / x" is displayed - Click previous => "3 / x" is displayed The pager is displaying the values before the switch has been made. Cause of the issue ================== When sending `this.value` on the `PAGER_UPDATED_EVENT` bus, the props have not been updated yet. This means that we send the previous value. Solution ======== We send the event once either the offset, limit or total props have been updated. opw-4666878
This update fixes an automated project workflow test that could fail because it moved ahead before a new record was fully created. It improves the reliability of internal quality checks for this version without changing day-to-day user behavior.
Original PR description
The tour only fails in saas-17.4 due to the tour not waiting for new record to be created, thus when record is refreshed next step is broken making the tour fail. This is already fixed in 18.0+ in PR https://github.com/odoo/odoo/pull/185691.
The rental website checkout now avoids errors when customers select times that fall during daylight saving time changes. This helps prevent failed purchases or booking interruptions around clock-change periods.
Original PR description
Pytz raises a `NonExistentTimeError` or an `AmbiguousTimeError` when trying to get the offset of a non localized datetime during the daylight saving changing time. Remark: the `_is_customer_in_the_same_timezone` method name should be changed in master as it does the complete opposite. runbot error 162039 Fix courtesy of @Xavier-Do
Rental product pages no longer show a $0.00 rental price when the website is configured to prevent sales of zero-priced products. This avoids confusing customers by keeping the product page consistent with the “Not Available for Sale” message.
Original PR description
Versions -------- - saas-17.4+ Price already hidden in 17.0 & earlier. Steps ----- 1. Set website to prevent sale of zero-priced products; 2. create a zero-priced pricelist; 3. create a rental product; 4. set a rental price of $0 on the zero-priced pricelist; 5. go to rental product page on website. Issue ----- It displays "$0.00/day" above the "Not Available for Sale" text. Cause ----- The rental price element doesn't check whether zero-priced products should be made available for sale. Solution -------- If the rental price is zero, and the website prevents sale of zero-priced products, hide the rental price element. We can use `combination_info['prevent_zero_price_sale']` for this thanks to commit 1f827ac1fad opw-4643155
This corrects a forward-port mistake in the inter-company sales and purchasing rules module. It removes logic that had already been moved elsewhere, helping prevent duplicated behavior and keeping the module split consistent.
Original PR description
This commit fixes a mistake made in [1] during the forward port of [2]. The issue being that the `sale_purshase_inter_company_rules` module was split in two, to extract the stock related logic in its own module. This was not caught correctly during the forward-port and two lines that were originally moved, were mistakenly re-added. [1] 7e5ef6294b6be31173fb67013bee85144ae586cf [2] odoo/enterprise#82079