[Hippo-cms7-user] Update cnd file

Unico Hommes u.hommes at onehippo.com
Mon Dec 3 17:05:47 CET 2012

On Mon, Dec 3, 2012 at 5:01 PM, Frank van Lankvelt
<f.vanlankvelt at onehippo.com> wrote:
> On Mon, Dec 3, 2012 at 9:08 AM, Ard Schrijvers
> <a.schrijvers at onehippo.com> wrote:
>> On Sun, Dec 2, 2012 at 4:02 PM, Marco Di Sabatino Di Diodoro
>> <marco.disabatino at tirasa.net> wrote:
>>> ----- Messaggio originale -----
>>> Da: "Ard Schrijvers" <a.schrijvers at onehippo.com>
>>> A: "Hippo CMS 7 implementation list" <hippo-cms7-user at lists.onehippo.org>
>>> Inviato: Domenica, 2 dicembre 2012 11:10:33
>>> Oggetto: Re: [Hippo-cms7-user] Update cnd file
>>> what kind of cnd change did you made?
>>> I need to add hippotaxonomy: classifiable to my document type
>> You could also only add the mixin to the existing prototypes and have
>> a jcr runner to add the mixin to all existing docs : A mixin is not
>> necessarily needed in the cnd
> yep.  This is the way to go.  New documents will get the mixin
> automatically, existing documents need to get it from the runner.
> You can upgrade the content in this way on a live system.  When the
> content has been upgraded, you can deploy a new version of the site
> that knows how to deal with the mixin.
> If you really want it to be in the primary type, you'll need to
> introduce a new document type.
> Using a runner you can then update the types of the documents using
> Node#setPrimaryType.
> In this way, you do not need namespace upgrader.  These operations can
> even be executed in a production system if your site has been coded
> for dealing with both types at the same time.
>>> You can only reload cnd's when
>>> they contain backwards compatible changes. The message you get imply
>>> you made a non backwards compatible change. We normally ourselves try
>>> to avoid backwards incompatible changes. If really needed, you should
>>> write a namespace upgrader
>>> where can I find some examples to create my namespace upgrader?
>> Note that they can run for a long time if you have a lot of documents.
>> Also, you have to make sure that you run it against a cloned database
>> in case something fails.
> note that namespace updaters are deprecated from 7.8 onwards.  They
> have a very big impact on deployment and as explained above, there are
> alternatives that do not require taking the repository offline.
> cheers, Frank

I guess we need to change the documentation here:



More information about the Hippo-cms7-user mailing list