I just happened to notice that the allowed children document types are kind of duplicated in the def.config file. They are only kind of duplicated because for every DocumentType element there is also an empty DocumentType element, such as in this example (note that this has not caused any issues as far as I've seen):
there is a bug in the Umbraco Package APIs that uSync uses to generate the xml when saving a doctype. the bug means that umbraco writes out the tag and doesn't put in the value.
Its actually a post export process that uSync does that then puts in the two DocumentType values with values in. In an attempt to make it future proof (i.e. when this bug is fixed) it checks for the existence of the values before putting them in but (in the current version) it doesn't delete the blank values.
I don't think the blank values will cause a problem - because they are just ignored on import - but the change to remove them is already in the next version which is built for umbraco 7.1 when it is released.
to be honest i keep forgetting about the core bug - I should go submit a Pull request.
DocTypes Duplicated in "def.config" Under "Structure"
uSync 2.0.0rc4 with Umbraco 7.0.4.
I just happened to notice that the allowed children document types are kind of duplicated in the def.config file. They are only kind of duplicated because for every DocumentType element there is also an empty DocumentType element, such as in this example (note that this has not caused any issues as far as I've seen):
Hi yes.
there is a bug in the Umbraco Package APIs that uSync uses to generate the xml when saving a doctype. the bug means that umbraco writes out the tag and doesn't put in the value.
Its actually a post export process that uSync does that then puts in the two DocumentType values with values in. In an attempt to make it future proof (i.e. when this bug is fixed) it checks for the existence of the values before putting them in but (in the current version) it doesn't delete the blank values.
I don't think the blank values will cause a problem - because they are just ignored on import - but the change to remove them is already in the next version which is built for umbraco 7.1 when it is released.
to be honest i keep forgetting about the core bug - I should go submit a Pull request.
is working on a reply...