Community mailing list archives

website template in module xml vs. frontend editing [v8]

initOS GmbH, Torsten Francke
- 02/23/2015 10:15:50
hi Community,

we running in a issue, that how to maintain frontend qweb templates.

So from the past, we just put everything in xml, that is included in the
repository. And like having a template for product detail page in
ecommerce module makes scents.
But know we add a new feature, so you update xml in the module and
upgrade the module after deployment.
BUT if the user change something in the fronted the upgrade of the
module revert the change.
So you put noupdate="1" to your module to prevent this, if you don't
want to forbidden your customer to use fronted editing at all. But then
you have manual steps in your deployment step. Syncing changes from live
=> test environment is also an issue.

So i want to share experience if someone figure out a better solution,
some tips, or build some script to handle this.

Kind Regards


Dipl.-Comp.-Math. Markus Schneider

initOS GmbH & Co. KG
An der Eisenbahn 1
21224 Rosengarten

Mobil:   +49 (0)172 2303699
Phone:   +49 (0)4105 5615613
Fax:     +49 (0)4105 5615610


Dipl. Wirt.-Inf. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
Haftende Gesellschafterin: initOS Verwaltungs GmbH

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRA 201840
USt-IdNr: DE 275698169
Steuer-Nr: 15/205/21402