Actually there is a big problem with non trivial changes. The thing is the involved method (checkForConflictingContent), called whenever you want to make a non-trivial modification, is not implemented. The only way to safely change your types would be to implement this method.
The export/import process you talk about implies that YOU do the check for conflicting content when you update your exported data....and good luck to update the system view. I think you'll have to : a/ implement the method; b/ wait for someone to implement it; c/ don't make non-trivial changes... Frédéric Esnault -----Message d'origine----- De : Nicolas Dufour [mailto:[EMAIL PROTECTED] Envoyé : mercredi 13 juin 2007 17:41 À : [email protected] Objet : Re: Reregistering node types Ok so I can change the repository gently, like a slow evolution. And I imagine that if I need to include a non trivial change, I will have to create a kind of migration process with export and reimport. Any ideas for the long term of a repository ? Nicolas On 6/13/07, Christoph Kiehl <[EMAIL PROTECTED]> wrote: > > Frédéric Esnault wrote: > > > Adding a property may cause this problem if the property is mandatory. > > What is possible now is to make a 'trivial' modification of a node type. > > Oh yes, you're right! I forgot about mandatory properies. > > BR, > Christoph > >
