Monday, September 30, 2024
8 changes · saas-17.4
Resolved issues and error corrections
Invoice labels with multiple lines now keep their line breaks visible while editing and after confirmation. This makes invoice descriptions easier to review and avoids confusion caused by browser-specific display differences.
Original PR description
Versions -------- - saas-17.4+ Steps ----- 1. Create an invoice; 2. enter a product; 3. hit enter to add a label; 4. hit enter to add newlines to the label; 5. confirm. Issue ----- On Firefox, the…
Versions -------- - saas-17.4+ Steps ----- 1. Create an invoice; 2. enter a product; 3. hit enter to add a label; 4. hit enter to add newlines to the label; 5. confirm. Issue ----- On Firefox, the added newlines don't show in the invoice lines tab, but do show in the journal items tabs. On Chrome, they show in the journal items tab, as well as invoice lines tab until they become uneditable by confirming the invoice. Cause ----- Bootstrap's `text-wrap` class added in 4f325ef62026 collapses sequential whitespace into a single space, wrapping text if necessary. For `input` and `div` elements, this makes sense. For `textarea`, wrapping is standard, and unlike `input`, it allows pressing Enter to start a new line, but because of `text-wrap`, these get collapsed into a single space, making it difficult for the user to see the actual layout of what they're editing. Solution -------- Remove the `text-wrap` class from `textarea` elements to keep line breaks visible regardless of invoice state. opw-4126094
The point of sale product list now shows warning indicators only when a product actually has a relevant warning. This prevents staff from seeing misleading red information tags on product cards, reducing confusion during sales.
Original PR description
The condition that dictates whether or not the product warning is shown in the product list in pos is inverted. This means that we currently show the product warning when it's not the case. Steps to reproduce: 1. On a db without self order installed, open a pos; 2. Observe that the "info" tags on the corners of the product cards are red; Task: 4214248 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Paid order lists in Point of Sale now sort correctly when the system uses a non-English locale, such as Arabic. This prevents staff from seeing paid orders in the wrong order and makes order lookup more reliable across international deployments.
Original PR description
In systems with a non-English locale (e.g., "ar-001"), the `date_order` field could not be parsed correctly, leading to improper sorting of paid orders. opw-4181429 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Mobile chat controls have been adjusted so the close conversation and start call buttons are larger and easier to distinguish. This reduces the chance that users accidentally start a call when they only intend to close a conversation, avoiding disruption for participants.
Original PR description
Button to close conversation and start a call are too small and close to each other. This means attempt to close the conversation can lead to accidentally starting a call, which scare all members of the conversation. This commit increases the size of these buttons and show borders so that it is less likely to click on start a call when the intent is to close the conversation. Before / After <img width="365" alt="Screenshot 2024-09-29 at 22 22 17" src="https://github.com/user-attachments/assets/7781eb6f-20e4-4ef2-ac0a-be50b39869ee"> <img width="366" alt="Screenshot 2024-09-29 at 22 21 56" src="https://github.com/user-attachments/assets/eede8d9c-891a-4cda-8dca-853b155ed6c3">
This fixes an issue where frozen spreadsheet files could still contain Odoo-specific pivot information. Removing that data makes frozen spreadsheets cleaner and more reliable when shared or reused outside their live Odoo context.
Original PR description
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 payment screen no longer adds an extra zero-value payment line when only one payment method is available and a payment line already exists. This avoids confusing duplicate payment entries and helps cashiers complete checkout more cleanly.
Original PR description
Before this commit, when only one payment method was available, an additional payment line with a value of zero would be automatically added, even if a payment line already existed. opw-4186191 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Planning app now correctly shows an empty row for a resource when users view a period with no scheduled work, such as the next week. This helps planners see available resources instead of mistakenly thinking they are missing from the schedule.
Original PR description
Steps to Reproduce: - Open the planning app. - Create a planning for a resource. - Make sure resource doesn't have any past or future plannings. - Change the time frame to next week. Issue: - We don't see an empty line. Reason: In the PR https://github.com/odoo/enterprise/pull/55618. All the gantt time ranges have domain strictly comparative operators(> and <). But in group_expand_resource_ids we use non strict comparative operators(>= and <=). Fix: - Added strictly comparative operators into operators being checked. task-4188936
This fixes a display issue where menu items in the Studio navigation bar could become difficult or impossible to see when dark mode was enabled. The update restores clear visibility and improves hover styling, making Studio easier to use for users who work in dark mode.
Original PR description
The PR https://github.com/odoo/enterprise/pull/66908 has introduced some problems in the way the studio navbar is styled in dark mode: mainly its menu items are not visible. Here we adapt some variables to have them visible again and have a suitable style on on hover.