Jörg, Most good citizen modules will carefully update, and as such should keep your customizations intact. At the very least, if the module update does not know what to do with your modifications (if the "floating column level" property disappears, for instance), it should warn you. There are a couple of exceptions, i.e pop-theme which just blatantly overwrites itself on updates.
That said, yeah, it's probably better practice to move your customization away in custom templates (use "extends"!) and site definition(s). Cheers, -g On 16 Feb 2011, at 18:59, Jörg Schaible wrote: > > Hi, > > what's the best practice concerning for future updates of the STK, if you > have > the need to adjust the values in the STK's template definitions? Am I right > in > my assumption, that an update will reset these values (e.g. floating column > level)? Is it better to take copies of the templates under a new name and > place them into an own node like the STK section templates of the demo > project? > > - Jörg > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
