Thursday, July 14, 2022
17 changes · master
Resolved issues and error corrections
Survey result badges now appear on the right on standard screens, restoring the intended layout while keeping the mobile-friendly column design. On very small screens, badges stay left-aligned so the results remain readable and easy to navigate.
Original PR description
Before the change added in odoo/odoo#87990 the badges on the result view were aligned on the right. However, this broke the mobile design. This was changed to a bootstrap column view but the alignment was lost in the process. It is brought back using a text-right alignment, making sure the center remains clean and the view open and clear enough. However, for very small screens they are displayed aligned on the left. The column display is kept. Task-2908045 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website theme selector now displays with the intended spacing and styling again. This fixes a visual regression that could make choosing a website theme look inconsistent or less polished.
Original PR description
Since 4f984568e139d8da448018af12ef79005e317cf6, the css theme is not correctly applied to the website theme selector. The order in which the css rules were applied without the '.o_legacy_kanban_view' selector removed a margin from the kanban_record element.
The database manager forms have been adjusted to display correctly with the newer page layout framework. This helps keep database creation and management screens visually consistent and easier to use after platform updates.
Original PR description
Adapt forms for BS5 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes a display issue in the Mail app where dropdown menus could appear misaligned after a framework upgrade. Users should see follower and messaging menu options open in the expected position, improving day-to-day usability.
Original PR description
[FIX] mail: dropdown menu not at the right position Since Bootstrap 5 migration, when we use the OWL `dropdown` component it must have the class `o-dropdown-menu` and not `dropdown-menu`. This commit replaces this class and also clean some CSS. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes English grammar in the gift card area. It improves the clarity and professionalism of user-facing text without changing business processes or functionality.
Original PR description
en_US police 👮
This fixes an issue in Odoo Discuss where using the arrow key to edit the most recent message did not work correctly. The change helps users quickly correct their last message without extra clicks, improving day-to-day messaging reliability.
Original PR description
task-2918507
The Expenses Analysis view no longer shows the expense dashboard, keeping the analysis area focused on reporting rather than dashboard actions. This reduces confusion for users reviewing expense data and makes the screen behave as intended.
Original PR description
The expense dashboard was displayed on the Expenses Analysis whilst it shouldn't have.
This update fixes a grammar issue in the Time Off area to make the wording clearer and more professional. It does not change any business process or functionality, but improves the quality of text users see.
Original PR description
en_US police strikes again 👮♂️
Sales orders with multiple linked payment attempts now confirm correctly when exactly one payment is authorized or completed. This prevents valid paid orders from being blocked just because earlier or extra payment transactions exist.
Original PR description
Before this commit, orders were not confirmed when there was more than one transaction linked to them, regardless of their state. As of now, we check if there is only one confirmed transaction (meaning that the state of the transaction is either 'authorized' or 'done'). Fix https://github.com/odoo/odoo/commit/4d2b04a843c27981e44d6f932d7cf7e6838b4b9d task-2906040
Dragging articles within nested Knowledge trees is now smoother and more predictable. This prevents flickering and reduces the need to drag far past the intended position, making article organization easier for users.
Original PR description
Prevent a flickering effect when dragging item down in a nested tree using the jquery.mjs.nestedSortable library. This is done by preventing the placeholder to go UP the DOM while moving the mouse DOWN. To go UP the tree in a situation where the mouse cursor is above the placeholder, the user should move the mouse UP or RIGHT. Force a position refresh of the following articles when starting an article move. Before this change, the library used obsolete coordinates to evaluate if the helper intersects with another article below, forcing the user to drag the nest far below the target position to move the placeholder. Task-2883290 PR SAAS-15.4:COMMUNITY: https://github.com/odoo/odoo/pull/93719 PR SAAS-15.4:ENTERPRISE: https://github.com/odoo/enterprise/pull/29307 PR MASTER:ENTERPRISE: https://github.com/odoo/enterprise/pull/29315
A compatibility issue could prevent some account-related mailed notifications from starting correctly after an underlying messaging service change. This fix updates the affected notification handling so those alerts continue to work reliably.
Original PR description
Some legacy services are still relying on the bus_service as a dependency. However, this service is now a wowl service which means those services won't start.
This fixes an issue where records grouped by the same date field at different levels, such as month and week, could lose the correct date range information. The change helps reports and grouped views calculate and navigate date-based groups more reliably.
Original PR description
There was an issue with the computed `read_group` `__range` when grouping on the same date/datetime field on multiple granularities (i.e. month, week). Since the range was stored with the field_name…
There was an issue with the computed `read_group` `__range` when grouping on
the same date/datetime field on multiple granularities (i.e. month, week).
Since the range was stored with the field_name as a key, the last evaluated
range would override the previous ones.
Impacted Versions:
- master
(- exists since 15.0 but it does not impact the user directly so it has been
decided to fix this only in master, since the API is modified)
Steps to reproduce:
1. Open a list view and group by a date field with at least 2 granularities
2. Open the chrome debugger (network) and check a web_read_group rpc preview
3. Find the web_read_group for groups related to one of the largest
granularities and check the `__range`
Current behavior:
- `__range = {field_name: false}`
Expected behavior:
- `__range = {field_name: {from: range_start, to: range_end}`
Explanation
Since the smaller granularities are evaluated last, and the condition to update
`__range` is related to the field_name and not the granularity, the range is
always overriden by the smaller granularities (even if their value is False)
when grouping on the same field with multiple granularities.
Furthermore, there is a conceptual problem with the current solution: it does
not allow to store multiple ranges when the read_group is not lazy and when
grouping on the same field with multiple granularities.
Therefore, the proposed solution is to use the full groupby keys in the
`__range` to allow storing multiple ranges depending on granularity. The keys
in `__range` would thus match the group value keys and allow more flexibility
if a domain must be forged from the group(s) range(s).
Task-2894519This fix adjusts the layout of buttons on social media kanban cards so they no longer sit too close to the card border. It provides a cleaner, more polished visual presentation for users managing social media records.
Original PR description
Before this commit, the button on the kanban record didn't have a space between the border of the button and the border of the kanban record.
The Aged Payable report now displays outgoing payment amounts as positive values in standard black text instead of negative red figures. This makes the report easier to read and avoids implying an issue where the negative presentation was only a formatting problem.
Original PR description
In the Aged Payable, amounts are all in red and in negative. It is kind of pointless, we are in a report that specifically reports OUT payments, so all amounts should be in black, and in positive Signed-off-by: Ruben Gomes <rugo@odoo.com>
This fixes the visual state of indeterminate checkboxes in Odoo Studio after the Bootstrap 5 migration. Users will now see the correct checkbox styling, reducing confusion when configuring or reviewing Studio options.
Original PR description
Since BS5 migration, the style of checkbox don't use a pseudo-element
input (`::before` and `::after`) to render the checkbox customized but
the input it-self.
In the rush of the migration, the following CSS rule was wrongly
adapted:
```css
.custom-checkbox {
...
&.o_web_studio_checkbox_inactive > input + label:after {
background-image: url("/web_studio/static/src/img/ui/checkbox_indeterminate.svg");
}
}
```Updated a tooltip in the VoIP user settings to make its meaning clearer. This small wording fix helps users better understand the option without changing how the feature works.
The Aged Payable report now displays outgoing payment amounts as positive values in standard black text instead of negative red amounts. This makes the report easier to read and better aligned with its purpose of showing payable amounts.
Original PR description
In the Aged Payable, amounts are all in red and in negative. It is kind of pointless, we are in a report that specifically reports OUT payments, so all amounts should be in black, and in positive Signed-off-by: Ruben Gomes <rugo@odoo.com>