the error is coming from Umbraco internally when the content type is saved. it is probably that his content type is used as a composition somewhere else and that is where the clash is.
from a uSync point of view - check you are running the latest version as there are some mitigation for issues like this in there
the error comes from a method that checks what groups/tabs are present on a content type
when it does this is also checks all compositions of a content type and anywhere the content type is used as a composition.
if there are tabs/groups with the same name on any of these other content types then they have to be of the same type (e.g a group or a tab) .
you can't for example have a tab in on content type called 'Content' and group in another one called 'Content' too * - if you do then this error is the result.
uSync v9.0.4+ does have some code to try and compensate for this when it happens in a sync, so hopefully updating to the latest version would fix it
*Its not actually the name of the tab/group, its the alias that matters, you can have two with the same 'name' not the same alias
Hi, thanks for your reply. I think it's strange that it does work on my local environment, but not on my staging env. So it does'nt seem that there is something wrong with the Umbraco configuration?
I think its usually around the change from groups to tabs.
when you do the change locally (e.g turn all your 'Content' groups in to 'Content' tabs) then there are multiple changes and things sort of have to happen in a certain order.
once you finish this any pass it over to be synced - uSync has to do a little dance to make this work:
We can't change the group to a tab on only one item in a chain of content types because it will cause a clash either up or down the tree, so uSync changes the group to a tab with a temporary name, once it has done this for all the places that group -> tab happens across all the content types, it flips the temporary name back to the original one.
this current method is how we do it v9.0.4 + pre v9.0.4 it was a little let robust so worked sometime not all.
if this issue is still happening and you are running v9.0.6 then we can take a look at the files and see if we can do anything extra to fix it.
uSync: ContentTypeHandler failed
I don't understand what this means... my doctype does not contain any compositions.
Exception:
Doctype:
Hi
the error is coming from Umbraco internally when the content type is saved. it is probably that his content type is used as a composition somewhere else and that is where the clash is.
from a uSync point of view - check you are running the latest version as there are some mitigation for issues like this in there
the error comes from a method that checks what groups/tabs are present on a content type
when it does this is also checks all compositions of a content type and anywhere the content type is used as a composition.
if there are tabs/groups with the same name on any of these other content types then they have to be of the same type (e.g a group or a tab) .
you can't for example have a tab in on content type called 'Content' and group in another one called 'Content' too * - if you do then this error is the result.
uSync v9.0.4+ does have some code to try and compensate for this when it happens in a sync, so hopefully updating to the latest version would fix it
*Its not actually the name of the tab/group, its the alias that matters, you can have two with the same 'name' not the same alias
Hi, thanks for your reply. I think it's strange that it does work on my local environment, but not on my staging env. So it does'nt seem that there is something wrong with the Umbraco configuration?
I think its usually around the change from groups to tabs.
when you do the change locally (e.g turn all your 'Content' groups in to 'Content' tabs) then there are multiple changes and things sort of have to happen in a certain order.
once you finish this any pass it over to be synced - uSync has to do a little dance to make this work:
this current method is how we do it v9.0.4 + pre v9.0.4 it was a little let robust so worked sometime not all.
if this issue is still happening and you are running v9.0.6 then we can take a look at the files and see if we can do anything extra to fix it.
I've updated my site from 9.4 to 9.6 to be sure, but still the same error. I don't see the issue...
This is my home.config:
The issue is likely not on home, but something that uses home as a composer?
will happily have a deeper look if you want to send me a copy of the uSync folder of the site [email protected]
Hi
Yeah there is nothing wrong with those files 😔 they sync fine on to a clean site.
was their anything on site you where applying these files to before you ran the sync ?
I found something. I deleted the doctypes and content on my staging env, published again and imported again. Now it works.
I now have to turnoff uSync automatic exports at the staging env, because I don't want to change stuff accidentally.
is working on a reply...