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.
Here is what is considered trivial and minor changes :
TRIVIAL :
* changing node type orderableChildNodes flag;
* changing node type primaryItemName value;
* adding non-mandatory property/child node;
* changing property/child node protected flag;
* changing property/child node onParentVersion value;
* changing property/child node mandatory flag to false;
* changing property/child node autoCreated flag;
* changing child node defaultPrimaryType;
* changing child node sameNameSiblings flag to true;
* weaken property valueConstraints (e.g. by removing completely or by
adding to existing or by making a single constraint less restrictive);
* changing property defaultValues.
MINOR:
* changing specific property/child node name to *;
* weaken child node requiredPrimaryTypes (e.g. by removing);
* changing specific property requiredType to undefined;
* changing property multiple flag to true.
Every other change is major. Currently, only trivial modifications work.
Frédéric Esnault - Ingénieur R&D
Legisway
60 boulevard de la mission Marchand
92400 Courbevoie La Défense
-----Message d'origine-----
De : news [mailto:[EMAIL PROTECTED] De la part de Christoph Kiehl
Envoyé : mercredi 13 juin 2007 10:53
À : [email protected]
Objet : Re: Reregistering node types
Nicolas Dufour wrote:
> I have a little problem : If I try to reregister the same node type but
> with
> a added property I received a nice message such as : not implemented !
> I'm using 1.2.3. Does 1.3 solve this problem ? If not how to workaround ?
Most probably you change more than just adding a property. Most of the times
this message occurs if you remove a property or a child node from the nodetype
definition, because removal of those is not supported yet.
If you use 1.3 you will at least get a better error message pointing out which
change is unsupported.
Cheers,
Christoph
