Hi,
Am Mittwoch, den 16.04.2008, 10:56 +0200 schrieb Bertrand Delacretaz:
> On Wed, Apr 16, 2008 at 10:48 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
>
> > > ...So the content loader should try to overwrite existing nodes and
> > properties ?
> > >
> > Yes. The only problem might be that a user has changed a property and this
> > gets then overwritten by an update. But I think this is an expected
> > behaviour....
>
> Not sure - if people use content from bundles as initial content
> that's meant to be modified after being installed, overwriting their
> changes would be a nasty surprise.
>
> Handling this nicely might be a lot of work, as we'd need to keep
> track of what is untouched initial content and what has been modified.
>
> I don't have a simple solution ATM, but we should at least have a
> prominent warning somewhere when this happens.
This all is actually the reason, why do not overwrite at the moment.
We could of course add a setting to force overwrite:
<Sling-InitialContent>
/content;overwrite:=true
</Sling-InitialContent>
Without this setting (or having it set to false), content is never
overwritten.
WDYT ?
Regards
Felix
