Daily updates from Odoo
Friday, September 2, 2022
8 changes
Resolved issues and error corrections
This fixes the color used for list view table headers so they match the appearance users had before the Bootstrap 5 migration. The change keeps the interface visually consistent and removes an obsolete styling line left over from the migration.
Original PR description
Before in BS4, the table used the `$table-head-color` SCSS variable to
color the header of table. This variable doesn't exist anymore on BS5.
In the commit of the BS5's merge, we have replaced the old value by
a value calculated with the color contrast in the case of the list view
it wasn't the right fix, so in community commit we restore the original
value like it was before the merge of BS5.
In this commit, we remove the unused line that was left in
the migration of BS5.
Note:
In BS4 branch the result is `#212529`:
```scss
$o-gray-900: #212529 !default;
$o-main-headings-color: $o-gray-900 !default;
$table-head-color: $o-main-headings-color !default;
.o_list_view .o_list_table thead {
color: $table-head-color;
}
```
In BS5 branch the result is `#00000`:
```scss
.o_list_view .o_list_table thead {
color: color-contrast(opaque($body-bg, $light));
}
```This fix updates internal tests so they keep working after a backend optimization changed when data is refreshed. It helps maintain reliability for Helpdesk and Field Service Sales without changing customer-facing features.
Original PR description
…ed_triggers`. `_modified_triggers` read and flush much less than before. Then some test crash because of that, fix it. https://github.com/odoo/odoo/pull/99274
Account reports now apply the correct number styling to all numerical values. This helps keep financial report figures visually consistent and easier to scan for users.
Original PR description
Sometimes the numerical values on an account report will not have the number class. This insures that the number class is properly applied to all numerical values. Signed-off-by: Ruben Gomes <rugo@odoo.com>
The Helpdesk ticket portal layout was adjusted to use page layout components more consistently. This helps keep ticket pages visually aligned and avoids minor display issues for portal users.
Original PR description
In this commit, we replace wrong usage of col without row, also adapt some gutter instead of padding and replace the old btn-block.
This fixes an issue in the sales subscription flow where the wrong unit of measure could be used on order lines. It helps ensure quantities and pricing are calculated consistently for recurring sales.
Original PR description
task-2960768 see also: - https://github.com/odoo/odoo/pull/98780
This fixes how Knowledge pages are accessed through web requests, helping ensure the right user context is used. It reduces the chance of access or permission issues when people open Knowledge content.
Removing someone from a Knowledge article's sharing panel now works without triggering an error. This prevents confusion and keeps collaboration management smooth when updating article access.
Original PR description
When the user removes a member from the share panel, the user will get a missing record error. The error occurs in the `article_remove_member` method: In that method, we fetch the partner from the member after deleting it. When we try to fetch the partner, the model raises an error as the member partner no longer exists. To fix the issue, we will backup a reference of the partner associated to the member we want to delete before deleting it. We will then use that reference in the following instructions. task-2968657
The Knowledge share panel no longer shows article links that the current user cannot open. This prevents users from clicking links that would lead to an access error and makes permission inheritance clearer.
Original PR description
In Knowledge, an article can inherit its permissions and its members from one of its parents. When it happens, the share panel includes a link to the article giving new permissions or members. When the user does not have access to the article, the user will get an access error by clicking on the provided link. To avoid that, we will no longer display a link in the share panel if the user does not have access to the target article. task-2968511