Odoo/addons/website_theme_install/models/ir_module_module.py, branch 14.0

[REF] website, *: merge website_theme_install into website

2019-11-12T15:53:13+00:00

* theme_bootswatch, theme_default, website_theme_install

[FIX] website_theme_install: theme installation

2019-10-10T06:33:16+00:00

Group the upgrade of upstream dependencies with the installation of a
new theme into a single install/upgrade operation.  This fixes cache
misses occurring when accessing the state of a module after having
upgraded other modules.

closes odoo/odoo#38331

X-original-commit: 03b796b9e92e6eeeee877beaea133bdb6de0c6a3
Signed-off-by: Sébastien Theys (seb) 
Co-authored-by: Sébastien Theys

[FIX] website_theme_install: properly attach new views to specific views

2019-10-02T01:02:56+00:00

When a theme declares a view (a 'theme.ir.ui.view') with an inherit_id,
on installation, a view (a 'ir.ui.view') will be created with the
corresponding inherit_id. The problem is that this inherit_id may
reference a view that has been cow'ed at some point and thus the new
theme view will be attached to the non specific view by mistake.

Part of https://github.com/odoo/odoo/pull/37142

closes odoo/odoo#37750

X-original-commit: https://github.com/odoo/odoo/commit/f30b4dfdb90515bc54e691302f894184c9b1c55b
Signed-off-by: Quentin Smetz (qsm) 
Co-authored-by: Romain Derie

[FIX] website_theme_install,*: redirect to frontend after theme install

2019-10-01T16:14:57+00:00

*: theme_bootswatch, theme_default

Before this commit, the first time a website was loading a theme, it would
not be redirected to the frontend afterward (even if that theme was already
installed on another website).
Any other theme installation on that website would redirect to frontend as it
should.

Indeed, the first time it would use the `act_url` returned by `next()` which
would only be called during the first time installation on the website.

All the `ir.action.todo` related to themes can be removed anyway, as you can't
install directly a theme. It can only be installed through website settings >
load a theme.
In which case we will always want to redirect to frontend.

task-2070463

closes odoo/odoo#37306

Signed-off-by: Jérémy Kersten (jke)

[REF] website_theme_install: remove dead code in theme install code

2019-09-30T10:00:51+00:00

closes odoo/odoo#37569

Signed-off-by: Quentin Smetz (qsm)

[REM] *: calls to @api.multi

2019-07-17T12:13:12+00:00

Multi is the default api for methods, it is not necessary to explicitly
decorate methods with it, adds clutter and most people use it because
they see that the rest of the code uses it.

Done with `find . -type f -name '*.py' | xargs sed -i '/@api.multi/d'`

[REF] *: removes datas_fname from ir.attachment

2019-06-05T09:12:13+00:00

This commit removes the field `datas_fname` from `ir.attachment` as
it was unnecessary and most of the time the duplicate of `name` or
`url`.

Task #1909865

closes odoo/odoo#32976

Signed-off-by: Martin Geubelle (mge)

[FIX] website_theme: translate website themes

2019-02-08T12:27:15+00:00

Inspired by l10n_multilang
When a theme is installed, the theme.* records are used to generate actual records.
The same was as we use account.account.template to create account.account, the
translations of  the theme records should be propagated to the new records.

opw-1918120

closes odoo/odoo#29748

[FIX] base,*: add MODULE_UNINSTALL_FLAG to cleanup views

2019-01-09T12:54:47+00:00

* website_theme_install

This commit will add MODULE_UNINSTALL_FLAG to the cleanup methods of themes and
modules.

This is necessary to also unlink inherited views of those we try to unlink.

Before this commit, an error would be raised when trying to delete a view that
still had other inherited views (either created manually by the user, or with
just bad luck in the order of which the views are deleted).

PR: #29753

[FIX] website_theme_install: remove obsolete comment

2019-01-09T12:51:56+00:00

This comment is not true, we originally wanted to code it this way but we changed
our mind and forgot to remove the comment.

PR: #29753