Tuesday, November 26, 2024
7 changes · saas-17.4
Resolved issues and error corrections
Point of Sale now shows a product's internal reference in product details and variant selection screens. This helps staff identify the correct item more quickly, especially when products have similar names or variants.
Original PR description
Before this commit, the internal reference was not displayed. With this commit, the internal reference will be shown in the product info popup and for products with variants in the product configurator. opw-4334505 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Products loaded into Point of Sale by scanning a barcode now use the language selected by the user. This prevents product information from appearing in the wrong language during checkout, improving clarity for staff and customers.
Original PR description
Before this commit, loading a product with a barcode into the PoS did not respect the user language. This was due to overriding the context when reading the product from the server. opw-4346227 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix makes the mail test for jumping to the first unread message more reliable by waiting for scrolling to finish before making further checks. It reduces false test failures during heavy system load, helping keep development and release validation stable.
Original PR description
This PR resolves an issue with the `scroll to the first unread message` test, which occasionally failed due to race conditions. Several issues were identified with this test: - We do not wait for the initial scroll to complete, which can lead to race conditions. - Under high CPU load, the message highlight can be shorter than the scroll. We should wait for the scroll to complete before allowing adjustments to be made. runbot-103421 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The point of sale ticket screen no longer shows the delete button when viewing paid orders. This removes a confusing action that could not be usefully applied, making the order review experience clearer for users.
Original PR description
Before this commit, in the ticket screen, when you filtered paid orders, you could press the delete button, which was useless and confusing. opw-4339996 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update makes an automated test more reliable by adding a small timing buffer so it no longer fails unpredictably. It helps keep quality checks stable and confirms the messaging connection remains active as expected.
Original PR description
The `test_rate_limiting_base_ok` ensures that rate limiting does not activate when requests are made within the accepted delay. However, the test only waits for the exact delay duration, whereas the rate limiter expects the delay to be strictly greater than the threshold. This PR introduces a small additional wait time before each request to ensure it falls within the accepted range. It also verifies that the WebSocket (WS) remains connected at the end of the test. runbot-73027
Buttons added to sales quotation terms and conditions now display correctly when printed as PDF. This fixes missing button styling in generated reports, improving document appearance and consistency for customers.
Original PR description
Steps to reproduce the issue: ============================= - Add a button in terms and conditions in an sale quotation - Print it as PDF - The button styles are missing Origin of the issue: ==================== After [1] the buttons are defined using css variables which are not supported by wkhtmltopdf. Solution: ========= Redefine the button styles for reports using scss variables in the same way they are done in `bootstrap_review_backend.scss` opw-4311049 [1]: https://github.com/odoo/odoo/commit/058212e12b5079eba870bde9775fe98f27928935
Selecting the "This year" filter in Payroll work entries no longer triggers an error. The work entries Gantt view now supports the yearly scale, so users can create entries from that view with dates set to the relevant month boundaries.
Original PR description
Steps - install hr_work_entry_contract_enterprise - Payroll > Work Entries > Select "This year" filter - ** UncaughtPromiseError > OwlError ** Cause With the addition of variable time ranges in Gantt, a new `year` scale is selectable but is missing from the view. Change Add year scale. When clicking on a cell or clicking on the "New" button, the start and end date of the work entries to create will be the beginning and end of the month. opw-4321645