11.0 website multi theme port from 10 - #450
Conversation
* [FIX] point inherit to copied views Otherwise theme_customize doesn't work when we have chain of views like in theme_clean: theme_clean.option_bg_shade_light2 inherits theme_clean.less theme_clean.less inherits website.assets_frontend without this update, website_multi_theme copies theme_clean.option_bg_shade_light2 but keeps inherit_id the same (i.e. to theme_clean.less, which is not used, because it has a copy) * [LINT] remove unused arguments, add semicolon
Current implementation disabled all backend views from a theme addon when converting it to multiwebsite mode. This is now fixed, and includes a migration script to make things work again if you hit this situation in your database.
New field "auto" in "website.theme.asset" to distinguish assets created from theme and ones created in xml. It's needed, for example, for non-module themes (like Demo theme) be handled in _convert_assets (before this update such themes were skipped) [REF] field multi_theme_generated is replaced with origin_view_id [IMP] apply default theme after installation [IMP] reload themes on installing new modules with customize_show [CI] Website always have Multi-Theme now. Also, increase default timeout (10 sec) to 60 sec, because it may take more time now
on installing module with customize_show Reload is done automatically
|
Is not migrated already? Check #398 |
|
This is a recent improvement. |
|
@emagdalenaC2i #398 was made by me 😉 |
closes OCA#410 [CI] test coverage for duplicated snippets
which avoids recursive reloading
* new name for res.config * move snippets lower, because website's tour use 4th element
|
This error is randomly shown on travis checks |
|
I'd like to set status "Needs review" to this issue and postpone with #456 which is not merged yet |
|
now #456 is in this PR too, i.e. all updates from 10.0 are here |
Also, change 127.0.0.1 to 0.0.0.0 because latter is used in odoo for second demo website
|
Checked internally and found misunderstanding about Multi-footer. I've added a note to documentation in latest commit |
yajo
left a comment
There was a problem hiding this comment.
@yelizariev Is this ready to merge then?
|
@yajo yes, it's ready. We did all we can. We will continue to test it with |
|
Please squash a bit some unneeded commits and I'll merge. Thanks for the work checking these rough edges. |
|
I found and done another thing that was in discussion #409 (comment) |
|
@pedrobaeza most commits were cherry-picked. I think it's better to keep them to easy comparing with 10.0 branch. |
| <odoo> | ||
|
|
||
| <record model="ir.module.category" id="base.module_category_theme"> | ||
| <field name="exclusive" eval="False"/> |
There was a problem hiding this comment.
I can't believe it was so simple! Could you backport this to v10? 🤔 Or was it hardcoded in v10?
There was a problem hiding this comment.
Yes, it's hardcoded and the only way is rewrite (not inherit) one method
WIPWe will check it internally first.