Contributors mailing list archives


Re: Proposal: split of some website modules in _backend and _frontend

- 07/12/2016 18:38:14
I guess that there are exceptions where this can be done, ie. product_brand has all the models and they are useful in the backend, hence, do a backend module, for the front end functionality you have website_product_brand which relies on product_brand.
 > but leave the UI implementation free for the user
In this case, to leave the option to any other developer of using a feature(controllers and models) I think its easier to simply set customize_show="True" to FE view and not force the use of the template via code.
so I have to go -1
Best Regards.

On Wed, Dec 7, 2016 at 11:23 AM, Pedro M. Baeza (Tecnativa) <> wrote:
The module you mentioned has no sense to be decoupled, as recently viewed products are for the website part, not for any backend. If you are thinking about using another frontend apart from Odoo, then you should add it apart from the website one, but not removing or splitting the work in 2 modules. We already have a very long list of modules and dependencies to decouple 2 things that in my opinion should be together.

So -1 for this.


2016-12-07 17:07 GMT+01:00 Nhomar Hernandez [Vauxoo] <>:

On Wed, Dec 7, 2016 at 9:38 AM, Leonardo Donelli <> wrote:
There are some website/ecommerce related modules that would be useful if split between the "backend" part and the UI/view/frontend part.

super +1

but be care there are ones where the backend does not make much sense without the frontend.

Nhomar Hernandez
CEO Vauxoo.
Twitter: @nhomar
Odoo Gold Partner
Skype: nhomar00 (Envia mail previo no lo superviso siempre).
Móvil Venezuela:
+58 4144110269
Móvil México:
+52 1 4773933942

Post to:

Post to:



Ing. Oscar Alcalá Rivera
312-107-1704 ·

Vauxoo SA
Tlf: +52 (477) 773.33.46

Open Source Enthusiast


   twitter linkedIn   Google+  

eco No me imprimas si no es necesario. Protejamos el medio ambiente