Saturday, June 28, 2025
3 changes · saas-18.3
Resolved issues and error corrections
Invoice PDFs now avoid extra blank lines when a customer address has empty fields, such as a missing second street line. This makes generated documents look cleaner and more professional without changing the underlying contact data.
Original PR description
To Reproduce: ============= - add contact with empty street2 - create invoice - generate pdf from invoice --> blank line Problem: ========= -The _compute_display_name method concatenates address fields using newline characters (\n). -When some address components (like street2) are empty, this results in multiple consecutive newlines (\n\n), producing blank lines in the rendered display name and PDF reports. https://github.com/odoo/odoo/blob/saas-18.3/odoo/addons/base/models/res_partner.py#L990 Solution: ========== filtering out empty or whitespace-only lines, and joining them back properly. opw-4820829 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The chat interface now shows the "Jump to Present" button sooner when users scroll back through older messages. This makes it easier to quickly return to the latest conversation, especially in threads with large or many messages, and also corrects its placement in some chatter views.
Original PR description
Before this commit, the "jump present" button when scrolling to older messages was displayed when going quite far in older messages. This happens because condition was: greater distance of either 3…
Before this commit, the "jump present" button when scrolling to older messages was displayed when going quite far in older messages. This happens because condition was: greater distance of either 3 times the view port client height and 10 times the height of most recent messages. When most recent messages are very big, this can be long until to see the jump to present. Also when there are lots of messages, 3 times the scroll client height can be a bit too much. In the past the "jump to present" UI was a banner so we were tempted to show when user was likely to want to jump to present. This is a small button now so we can be much more eager to its showing. This commit removes the condition to recent message height and just uses the height of scroll client height for the showing of jump to present. Before / After  
VoIP configuration now handles cases where the default phone call activity type has been removed. This prevents users from seeing an error when refreshing or loading the system after that activity type is missing.
Original PR description
Currently, an error occurs when the system initializes the voip configuration for the currently logged-in internal user. Steps to Reproduce: - Install the `voip` module. - Delete the activity type where the `Action` is `'Phonecall'`, and then refresh the page. `IndexError: tuple index out of range.` This error occurs when the system initializes the voip configuration and no phonecall activity type exists. The system attempts to search for activity types with the 'phonecall' category, which returns an empty recordset. Then it tries to access the first record of this empty recordset[1], which raises an error. [1] https://github.com/odoo/enterprise/blob/2896974e9eda61bfe5e1d67423dc56f6ab17b2af/voip/models/res_users.py#L128 This commit ensures that if activity type with the 'phonecall' category is present, it store the activity type id, otherwise, it stores False as the activity type id. sentry-6689050392