Given that the duplicate and conflicting classes resolved by the
previous commit did still exist at the time new page templates were
introduced in [1], they could not be avoided for new page templates
snippets.
This commit removes those from the new page templates snippets now that
they have been removed from the base snippets.
[1]: https://github.com/odoo/design-themes/commit/80cbee66f6bb4d897dd7e577f1109c75f6f6ad74
task-3562147
X-original-commit: 9984745d3d
Part-of: odoo/design-themes#744
Themes translation in Odoo 16 have been lost, they were not exported on
Transifex anymore (bug).
We just added back the repository on it, and our internal translators
are working on those translations.
They found some typos and bad wording which are fixed here.
Technically, note that we need the themes fully translated for the
chatGPT integration coming in website configurator.
Indeed, if a theme is not (almost fully) translated, it won't be using
chatGPT for text replacement.
This is because if we ask chatGPT to do text replacement and translation
at the same time, it just provides bad results.
See https://github.com/odoo/odoo/pull/137703closesodoo/design-themes#725
X-original-commit: 7cdb6d2ab7
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Signed-off-by: Romain Derie (rde) <rde@odoo.com>
This commit customizes all New Page template designs for every single
theme.
The changes are organized as follow:
When the used blocks are not the default ones:
- the new sequence of block is listed in the `new_page_templates`
manifest entry.
- the blocks are updated in the `new_page_template_sections_..._...`
XML templates accordingly.
After the potential block sequence updates, the `new_page_template.xml`
then first contains the general customization of blocks (those that
apply across all new page templates) then the customization for each
category of page.
Customizations for a specific page are directly below category-wide
customizations of the given block when both exist.
task-3381714
closesodoo/design-themes#692
Related: odoo/odoo#126719
Signed-off-by: Romain Derie (rde) <rde@odoo.com>
Co-authored-by: Benoit Socias <bso@odoo.com>
Co-authored-by: Arthur Detroux (ard) <ard@odoo.com>
This commit extracts the pre-defined section shapes from blocks into
templates that are dedicated to being used by the configurator.
For blocks that are not used in configurator pages, the configurator
templates have not been created.
task-3381714
Part-of: odoo/design-themes#692
Since the redesign of the original banner snippet, the customizations
made in theme_bistro have had to be adapted.
task-3097005
Part-of: odoo/design-themes#687
As steps are encapsuled in an arrow function from
69a5d8e3ce47238 for steps tour definition to avoid
direct Markup(_t()) interpretation, the same is done
for registerWebsitePreviewTour() of
"odoo/addons/website/static/src/js/tours/tour_utils.js"
in this commit.
This is done in anticipation of the use of
_t() (import from @web/core/l10n/translation) with
registerWebsitePreviewTour().
task-3292454
closesodoo/design-themes#678
Related: odoo/odoo#130248
Signed-off-by: Luca Vitali (luvi) <luvi@odoo.com>
Initially, the background shapes were flipped using only CSS. This was
done by adding the classes 'o_we_flip_x' or 'o_we_flip_y' to a shape to
flip it. However, this system caused issues as it sometimes left a gap
between two connected shapes. As a result, the system was changed with
this commit [1], and the classes 'o_we_flip_x' and 'o_we_flip_y' were no
longer used from this point on.
Despite this change, in our themes, we continued to use these obsolete
classes to define whether a shape should be flipped or not. This commit
addresses this by removing all instances of 'o_we_flip_x' and
'o_we_flip_y' classes that were still being used in theme snippets and
replacing them with the new system, where flipping is defined as a
parameter in the background image URL.
Note that in stable versions where we cannot modify theme snippets, we
have added code to automatically adapt the shapes to the new system
(in this commit [2]).
[1]: https://github.com/odoo/odoo/commit/42b3ad10e0b32b7fc72f801e2c67d6baf938c566
[2]: https://github.com/odoo/odoo/commit/256ff539afe331544ccb58848f1ecd0eecbe4daa
task-2824607
closesodoo/design-themes#639
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
This is the direct following of the PR [1].
Some themes "hard code" the background colors of some snippets, which
prevents the user to change it with a preset color without deleting the
current background first.
This commit does two things:
- remove the problematic hard coded background colors;
- replace the colors that are removed by some themes by the ones that
were set in [1] (for the searchbar and text highlight snippets).
[1]: https://github.com/odoo/odoo/pull/90749
task-2824393
closesodoo/design-themes#604
X-original-commit: 7d193e0560
Related: odoo/odoo#103123
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Before this commit, if a theme wanted to define a main font for their
theme and let the "headings", "navbar" and "buttons" ones use the same
they had to add this in their map:
```
'font': XXX,
'headings-font': null,
'navbar-font': null,
'button-font': null,
```
Indeed, without setting the "null" values, those font would use YYY
which is the first font defined in the theme config, which might be
different from XXX. And if forcing XXX 4 times, like most themes do at
the moment, if the user wanted to change them all, he had to change the
4 ones instead of the main one.
Now, only the 'font' value use the first font defined in the theme
config if not explicitly set. So forcing the null values is not
necessary, it will be the default behavior.
The advantage is thus also functional, as most theme forced all their 4
fonts so changing the main one did not change the others.
task-2993054
closesodoo/design-themes#593
X-original-commit: fc64bce81e
Related: odoo/odoo#101068
Signed-off-by: Romain Derie (rde) <rde@odoo.com>
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
See [1], `enable_view()` is now in charge of disabling the already possibly
existing template header (and/or footer).
Disabling `website.template_header_default` was not enough, any of the other
template could have been selected by the user before updating the theme.
Note that when installing a theme the first time on a website, the error won't
occur as `_reset_default_config()` will be called through `_theme_remove()`.
[1]: https://github.com/odoo/odoo/pull/81181
Fixes https://github.com/odoo/upgrade/pull/3048
task-2593407
opw-2680866
opw-2685951
opw-2685124
opw-2679040
closesodoo/design-themes#548
X-original-commit: 9a289ea574
Related: odoo/odoo#81953
Signed-off-by: Romain Derie (rde) <rde@odoo.com>
Before this commit:
- The assets were not enabled or disabled when installing themes because
we searched for assets with the "key" field instead of the "name" field.
- The "Ripple Effect" was not correctly installed on several themes.
Because the variable and the assets were not both activated. Even if the
variable is not used, it is still necessary for the proper functioning
of the option (e.g. _computeWidgetState).
task-2686370
closesodoo/design-themes#546
X-original-commit: 77b2b97f3d
Related: odoo/odoo#81833
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
In Safari (14+) the CSS workaround to make block "readable" over any bg
is broken. By replacing the current CSS workaround by an appropriate
SVG filter in each themes svg, the problem will be fixed.
This commit will add the svg filter.
task-2667028
closesodoo/design-themes#538
X-original-commit: 545cf002ea
Related: odoo/odoo#81190
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
This commit injects for each theme a "preferred" palette into the
website's UI palette list ("Theme" tab).
It also removes '$o-palette-priority-prefix' overrides, letting website
handling the palettes order.
task-2656337
closesodoo/design-themes#514
X-original-commit: 0539787e23
Related: odoo/odoo#77857
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Many themes were overriding the yiq threshold, thus having an impact
on which of the dark or light text is used over a particuler background
by default. This is a tricky value to change and only made some sense
when the Odoo themes were defining their own color palettes. Now that
all palettes can be used in all themes, it makes no sense to change the
yiq threshold as it induces inconsistent behavior for a same palette
used in different themes. Besides, leaving the value by default is most
of the time what you want and when it is not entirely correct, the user
has full control over the color combination text colors anyway.
task-2655730
closesodoo/design-themes#507
X-original-commit: f244035809
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
This commit updates the theme to improve the design with new colors, new
pictures and new snippet customizations.
task-2545200
X-original-commit: ac1f140172
Part-of: odoo/design-themes#501
Those two themes were defining a 'hambuger-type' variable to
'off-canvas', probably a typo of 'hamburger-type'... but the themes
do not even activate the views related to 'off-canvas', so this had
simply no effect and did not create any bug.
closesodoo/design-themes#488
X-original-commit: 4f8139719e
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
If user selects 'schedule appointments' as main objective in the configurator
and if the website_calendar module is installed then the Call To Action of
snippets s_banner, s_cover and s_call_to_action is changed to 'Schedule an
appointment' and redirect user to '/calendar' on click.
task-2518565
closesodoo/design-themes#5
Related: odoo/odoo#71162
Related: odoo/enterprise#18690
Signed-off-by: Jérémy Kersten (jke) <jke@openerp.com>
Benoit Socias