Friday, June 7, 2024
3 changes · saas-17.2
Resolved issues and error corrections
The calendar month view now shows the correct day names for users in different time zones. This prevents confusion when planning or reviewing dates, such as a Wednesday incorrectly appearing as Tuesday.
Original PR description
Versions -------- - saas-17.2+ Steps ----- 1. Change browser time zone to America/Los_Angeles; 2. go to Calendar; 3. switch to Month view. Issue ----- The day names displayed are one day off, e.g. showing 2024-05-01 as TUE instead of WED. Cause ----- Commit 90f85a19deae updated FullCalendar to V6.1.10. One of the changes it introduced is that month view renders no longer look at a specified date, but one in the distant past, see: https://github.com/fullcalendar/fullcalendar/issues/5854#issuecomment-702495211 The time zone of this "distant past" should get interpreted as UTC instead of defaulting to the local time zone. Solution -------- In the custom render function passed to FullCalendar, interpret the Date object as UTC time instead of local time when scale is set to month. opw-3934014
Fixes replenishment errors when one warehouse resupplies another while using multi-step delivery or reception flows. Businesses using advanced warehouse routes can now trigger reorder replenishments without being blocked by missing route rules or incomplete incoming move checks.
Original PR description
Steps to reproduce: - Have two separate warehouses A & B - Enable 3-step delivery on warehouse A - Enable 'Resupply from warehouse A' in warehouse B - Set a product using that resupply route and trigger its ressuply (e.g. through a reordering rule) Issue: An error message pops up indicating that there are no rules could be found to resupply A/Output. Following the pull&push refactor in #156437, we changed the way the default 3-step delivery would work (with now a mix of pull & push rules). This means that there are no longer any default pull rules to resupply the Output location. To avoid this, we add the missing rule, pulling from Stock -> Output, using the standard delivery rules for the eventual pack operation. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change ensures the website live chat chatbot flow test can run reliably when demo data is not installed. It creates the needed portal user during the test, reducing build failures and improving confidence in release checks.
Original PR description
Before this PR, the `website_livechat_chatbot_flow_tour` was failing in no-demo builds. This test uses the demo portal user, which is not available in these cases. This PR fixes the issue by creating a portal user for this test. fixes runbot-65497