Tuesday, November 12, 2024
5 changes · saas-17.4
Resolved issues and error corrections
This change adds logging to help support teams identify when a websocket session has silently fallen back to a public user. It makes troubleshooting easier when messaging appears to work partially but the connection is not tied to the expected user session.
Original PR description
Debugging websocket can be tough as we don't know when a session is downgraded. Some messages can be received, giving the impression that everything is working fine while the socket is actually linked to a public user. This PR introduces some logs to help debugging this scenario. opw-4218953
Delivery tracking links are no longer automatically converted to lowercase. This prevents broken carrier tracking links when the carrier requires specific uppercase and lowercase characters in the URL.
Original PR description
Steps to reproduce the bug:
- Create a storable product P1
- Go to the delivery method
- Select the Standard delivery
- Add this tracking link: “https://iel.co.th/tracking/?trackingNo=<shipmenttrackingnumber>”
- Create a delivery for one unit of P1
- Go to the additional information:
- carrier: Standard delivery
- Tracking Reference: 1234
- Mark as todo
- Click on the racking smartbutton
Problem:
The link is lowercase, so its become not valid (some URLs are CASE-sensitiv)
opw-4296872Weekly Gantt labels now show the correct year when a week crosses into a new calendar year. This prevents misleading planning dates such as showing the first week of 2025 as belonging to 2024 for locales where weeks start on Monday.
Original PR description
Versions -------- - saas-17.4+ Enterprise PR: https://github.com/odoo/enterprise/pull/73318 Steps ----- 1. Have Planning installed; 2. change localisation to 'en_GB' (or any whose weeks start on Monday); 3. open in Gantt view in weekly granularity; 4. go to the week of 2024-12-30. Issue ----- Label on top right displays "W1 2024"; Cause ----- It uses the `getLocalWeekNumber` function to get the week number of 2024-12-30, which falls in the first week of 2025. It then combines it with the `year` of the date, which is 2024. Solution -------- ### Community: Like the `weeknumber` function added in 9c47e911d0ca7 to `odoo.tools.date_utils`, have a function in `web` that returns both year and week number. ### Enterprise: Define a `formatLocalWeekYear` function in `web_gantt` using the new `getLocalYearAndWeek` function from `web`. opw-4280192
The Gantt view now shows the correct year alongside week numbers when a week crosses into a new year. This prevents confusing labels such as showing the first week of 2025 as belonging to 2024 for users with Monday-based week settings.
Original PR description
Versions -------- - saas-17.4+ Community PR: https://github.com/odoo/odoo/pull/186284 Steps ----- 1. Have Planning installed; 2. change localisation to 'en_GB' (or any whose weeks start on Monday); 3. open in Gantt view in weekly granularity; 4. go to the week of 2024-12-30. Issue ----- Label on top right displays "W1 2024"; Cause ----- It uses the `getLocalWeekNumber` function to get the week number of 2024-12-30, which falls in the first week of 2025. It then combines it with the `year` of the date, which is 2024. Solution -------- ### Community: Like the `weeknumber` function added in 9c47e911d0ca7 to `odoo.tools.date_utils`, have a function in `web` that returns both year and week number. ### Enterprise: Define a `formatLocalWeekYear` function in `web_gantt` using the new `getLocalYearAndWeek` function from `web`. opw-4280192
Restaurant table lists in the floor plan now show the linked appointment resource. This helps staff quickly see which resource is associated with each table, reducing confusion when managing restaurant appointments.
Original PR description
Before this commit, appointment_ressource_id was not showing in floor_plan form (table list). It is now. Community PR: odoo/odoo#185808