Wednesday, November 27, 2024
9 changes · saas-17.4
Resolved issues and error corrections
Fixed a point-of-sale issue where pressing backspace twice while entering a percentage down payment on a quotation could cause an error. This makes the sales flow more reliable for cashiers handling quotation payments in POS.
Original PR description
Steps to reproduce : --------------------------- - Install the point_of_sale and sales module. - Set downpayment on the shop and open session. - Press quotation/orders action button. - Open any quotation try apply percentage downpayment. - Try to press backspace twice. Issue : --------- The number buffer would be "" at starting but when we again press backspace it will become null as mentioned from number buffer services which was directly passed to parseFloat function. Cause : ---------- The parse float function applies startsWith function which won't be there if value is null. Fix : ------ Instead of passing buffer directly now just send buffer to parse if it exist else send "" instead of null.
The self-order product page now displays the currency symbol on product cards. This helps customers clearly understand prices before ordering, reducing confusion during the buying flow.
Original PR description
Before this commit: ========== - The currency symbol was not visible on the product card on the self-order product page. After this commit: ========== - The currency symbol is now visible on the product card on the self-order product page. task-4342039
A test for the web date picker was adjusted so it no longer fails when the picker takes slightly longer to open. This helps keep automated checks stable and reduces false alarms during development, without changing the user-facing product.
Original PR description
This commit fixes a test which sometimes timeout. To quickly explain, the test tries to open the date picker popover and it succeeds almost everytime but it happens that the popover takes more time than the usual.
A visual issue caused the language button to appear twice when hovering over interface views. This fix keeps the button display consistent, reducing confusion for users working in the web interface.
Original PR description
The button is doubled because the visibility is overriden. Let's force it. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix makes shared appointment availability calendars easier to read by better distinguishing past time slots from non-business hours. It also prevents today's calendar view from visually overflowing when past hours are shaded, improving scheduling clarity for users.
Original PR description
Purpose ======= Fix the calendar slots selection display when sharing appointment availabilities. Specification ============= The working hours have recently been added to the user's calendar. To highlight those, the non-business hours cells are grayed out (from 9am to 5pm). Following this change, it is now difficult to differentiate the non-business hours cells from the "Share Availabilities" gray overlay set on all the past cells. Fixing that by darkening a bit the color of the past cells when sharing availabilities. Additionally, for today, a div with a computed height was added to gray out cells before the current time. This div is now pushing the non-business hours divs which makes them overflow the day display. Fixing that by changing today's past hours div to position absolute. related commit: odoo/odoo@09ddd9f46c0d7528cb0138af283f6ec4f388a445 Task-4337795
Studio now only offers timeline scale options that are allowed by the underlying planning view. This prevents users from selecting an unsupported expanded month view that could cause the planning schedule to fail when switching views.
Original PR description
Steps to reproduce ================== - Go to planning - Open studio - Change the default scale to Month (expanded) - Close studio - Switch to Schedule > By Role => Cannot destructure property 'defaultRange' of 'metaData.scales[scaleId]' Cause of the issue ================== The planning view has the scales attribute as `scales="day,week,month,year"`. month_3 is not part of the allowed scales. opw-4175183
This fixes an issue where a Gantt view could fail to open if its configured default time scale was not also listed among the allowed scales. The system now automatically includes that default scale, making scheduling views more reliable for users.
Original PR description
Steps to reproduce ================== - Have a gantt arch with a default_scale that is not part of scales ```xml <gantt scales="week,month" default_scale"day">...</gantt> ``` => Cannot destructure property 'defaultRange' of 'metaData.scales[scaleId]' Solution ======== If we set a default scale that is not part of the scales, add it to the list of allowed scales. opw-4175183
When users create a new spreadsheet from Documents, template options now display their names instead of appearing unnamed. This makes it easier to identify and choose the right spreadsheet template, reducing confusion during setup.
Original PR description
when creating a new spreadsheet in document, the user is prompted to either choose a blank spreadsheet or choose to create them from a template. The view didn't list the name of the template. This commit shows the name of the template Task: 4363974
Payroll users can now open the work entries Gantt view using the yearly scale without triggering an error. This resolves a configuration issue so annual planning and review of work entries works as expected.
Original PR description
…ntt view Steps: • Install the payroll app. • Open the work entries and set the Gantt view scale to "This year". • This will trigger an error. Cause of the issue: • In the Gantt view record, the year is missing in the scales attribute. Fix: • Added the year as an allowed scale. task-4351487