Releases: Niboo/odoo
Releases · Niboo/odoo
16.0.9.0: [FIX] website, *: fix some components in case of contrasted boxed layout
*: website_slides
In some cases, components had dark text over dark background (or light
text over light background) by mistake.
Example:
- Enter edit mode.
- In the theme tab, choose "boxed" as page layout.
- A color picker appears below to control the color behind the box.
- Set it to a dark color (if your box main color is light)
- Go to a course page (install website_slides)
- Check the mobile version
=> The bootstrap tab and its section uses the dark color you set up as
body color instead of the expected boxed layout color.
Another example:
- Do the same thing (set up a dark color behind a boxed layout).
- Go to a shop / product page.
=> The inputs are dark with dark text.
This is because of bootstrap which uses `$body-bg` as default value for
other variables, such as `$nav-tabs-link-active-bg` in the first case
described above. It also uses the variable in the creation of CSS rules
not controlled by explicit variables.
In 16.0, bootstrap was updated to 5.1.3 with [1] and this actually
increased the problem: input backgrounds now default to `$body-bg`,
amongst other things. Since [2], `$body-bg` is also used as the default
color for range thumbs.
In previous versions, this fix focused on fixing a critical component:
nav-tabs, for which the fix was straightforward.
Starting from 16.0, this commit will fix everything at the small risk of
changing the `$body-bg` variable meaning in the case of boxed layouts.
Before this commit, its meaning was "the color used for the background
behind the boxed layout (the <body> background color)", so equal to the
Odoo value `o-color('body')`. After this commit, its meaning will be
"the color used for the background of the box itself", so equal to
`o-color('o-cc1-bg')`. The `<body>` background color will be forced by
using `o-color('body')` as the value for the related *CSS* variable
defined by bootstrap. This allows to have a correct CSS generation for
all components in case of boxed layouts: indeed, the components mix
their own color with `$body-bg` (or use it as it is) relying on the fact
this is the color which appears behind them... which was not right in
case of boxed layouts.
This commit actually fixes another bug that was found during adaptation.
It is 2-fold, and unfortunately, it does not make sense to fix one part
without the other as it would increase the problem without the other
part. The website_slides pages customize their default background color
to not be the one chosen by the user, but a mix of it with some
lightgray. Odoo default for the body being white, this makes it a
lightgray for website_slides pages. This is totally ok... but only in
"full" layout. In boxed layout, we have the 2-fold problem:
A. The mixed color is not applied to the boxed layout but on the
background behind the box. So if you have a white box above a black
background, in website_slides pages you won't have the black
background you expected to keep but a lighter version of it and the
website_slides box will not use the lightgray but stay white
(creating other inconsistencies as the lightgray would also be used
by other components like tabs, for that app only).
B. The mixed color is actually not mixing the right colors: it mixes
the hardcoded lightgray with the color of the background behind the
box, while it was intended to be the one of the content (the one of
the box), like in "full" layout.
The changes explained above about `$body-bg` naturally fixes (B). Not
fixing (A) at the same time would result in a big change for the color
which is behind the box. This commit fixes it at the same time by now
applying the color to the right element. In previous version, this could
be fixed as well but would require a different fix (not relying on
`$body-bg`). So it makes sense to merge this first and backport+adapt.
[1]: https://github.com/odoo/odoo/commit/971e5a91aab96d36129a823e03f1f9f1b1293968
[2]: https://github.com/odoo/odoo/commit/46e53879749be7ba3d30338d0f25c0a68a88eb3c
opw-3151962
closes odoo/odoo#112136
X-original-commit: 03f238aadc4b96da95cb2a55ba5b08cebeeeb345
Signed-off-by: Romain Derie (rde) <rde@odoo.com>
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
16.0.7.0
[FIX] web_editor: fix toolbar not hiding when clicking outside of edi… …table Commit [1] correctly disabled some of the behaviors of the editor that used to modify the selection outside of the editable. However, it also had the inadvertent side-effect of disabling the toolbar update mechanism when clicking outside of the editable. Behavior before this commit: When the toolbar is visible, clicking outside the editable zone does not hide the toolbar. Behavior after this commit: Clicking outside of the editable zone hides the toolbar. [1]: 07a14839671ee516db124b18f5b58d6ad08f382d task-3131435 closes odoo/odoo#109914 Signed-off-by: David Monjoie (dmo) <dmo@odoo.com>
14.0.16
[FIX] portal: fix portal title for the salesperson data Before this commit, if the helpdesk module was installed, the title of the salesperson data was changed from "Your contact" to "Salesperson" for portal users. This did not add any value and the title of the tab also became "Salesperson" which we do not want. This commit allows to keep the title "Your contact" above the salesperson information and to not change the tab title. Steps to reproduce the problem fixed by this commit: - Run Odoo enterprise with helpdesk and sales installed. - As the admin, create a helpdesk ticket with Joel Willis (portal user) as the customer and save. - Click on Joel Willis, select the "Sales & Purchases" tab and set a salesperson. => Log in as Joel Willis and on /my, you will have "Salesperson" as the title of the tab. This bad behavior is due to [this commit] that added a title above the salesperson information. But with this change the title of the tab was also impacted. Then [this other commit] added a default title above the salesperson information. We can be satisfied with this default title which does not alter the title of the tab. [this commit]: https://github.com/odoo/enterprise/commit/700e9dec4a5c9fca354e063d6a85b0514832c84c [this other commit]: https://github.com/odoo/odoo/commit/d5c66ca1fa5d0f364241636bd502342c1d4ee9ac opw-3103718 closes odoo/odoo#108705 Related: odoo/enterprise#35240 Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
16.0.6.0
[FIX] spreadsheet: update o_spreadsheet to latest version ### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/6c89e266 [FIX] collaborative: don't endlessly dispatch new revision https://github.com/odoo/o-spreadsheet/commit/1de19d7d [FIX] GridOverlay: Only react to self targeted double clicks https://github.com/odoo/o-spreadsheet/commit/40fc6151 [FIX] figure: apply dragging style on actual drag, not on mousedown https://github.com/odoo/o-spreadsheet/commit/aee5f929 [FIX] figure: Avoid scroll on a focused figure https://github.com/odoo/o-spreadsheet/commit/37b97b18 [FIX] dashboard: click cells to close filter menu closes odoo/odoo#107644 Signed-off-by: Pierre Rousseau (pro) <pro@odoo.com>
16.0.5.0
[FIX] l10n_id_efaktur: payment terms blocking payment Setup indonesian invoicing Create a payment term with payment in 30 days and 10% if paid before 2 days Create an invoice with said payment term Confirm and register payment Operation will be blocked by error "Cannot mix VAT subject and Non-VAT subject items in the same invoice with this kode transaksi" This occurs when creating the payment move. All the lines have display_type set to 'product' (defualt value), so the system checks consistency of kode transaksi as in an invoice opw-3063052 closes odoo/odoo#107120 Signed-off-by: Josse Colpaert <jco@odoo.com>
16.0.4.0: [FIX] website: stop showing CSS variable assertion tour step to users
Commit [1] introduced a website tour util to assert the value of a CSS variable. This was used at the start of theme tours to check we are in fact on the right theme before starting the tour. While it's great for those tours when they are started as a test, it was not meant to be shown to users following that tour. This commit fixes that. Notice that theme tours are currently broken so the issue was probably hidden. Those will be fixed at [2]. [1]: https://github.com/odoo/odoo/commit/b29e17765f4e912b2dd472493b5be500b3a32c87 [2]: https://github.com/odoo/odoo/pull/106703 Related to task-3084175 closes odoo/odoo#106725 Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
14.0.15.0
[FIX] point_of_sale: load orders with archived product Before this commit: if one product in one of the previous orders is archived, it won't load the order properly for order management. opw-3035231 closes odoo/odoo#105952 Signed-off-by: Trinh Jacky (trj) <trj@odoo.com>
14.0.13.0
[I18N] Update translation terms from Transifex
13.0.19.0
[I18N] Update translation terms from Transifex
15.0.9.0
[I18N] Update translation terms from Transifex