I created a BasePage DocType. Then created a GalleryPage DocType based on BasePage.
I added a pageTitle property to the GalleryPage DocType, then later, unwittingly added a pageTitle to the BasePage DocType.
In Settings, when I click on BasePage, I get the following YSOD:-
"InvalidCompositionException - ContentType with alias 'BasePage' was added as a Compsition to ContentType with alias 'GalleryPage', but there was a conflict on the PropertyType alias 'pageTitle'. PropertyTypes must have a unique alias across all Compositions in order to compose a valid ContentType Composition."
I think I'm screwed. Is there a way out of this so I don't have to trash the whole site and start again?
I faced the same issue after upgrading to 7.2.1 because the previous stucture of the ContentTypes I had would currently not be allowed.
I just deleted the faulty entries from the cmsContentType2ContentType, that keeps these type relations, and after recycling the application pool everything worked like a charm.
I have this issue after upgarding to 7.2.2. My backoffice is pretty much gubbed, If i delete the faulty entries does that mean i will need to recreate the content types and all the pages associated will be gubbed and have to be redone?
I know this is a bit of an old topic but for anyone still upgrading from 7.1.6 or so where a previous developer or user added a property on a child type with the same alias as one on the parent type:
Check for these before doing the upgrade and rename the child type property
If it's too late,
delete the offending types from cmsContentType2ContentType table (but keep a note of the IDs before deleting)
Rename the child type property
Re-add the reference to cmsContentType2ContentType table
Don't know if there are more hidden pitfalls but this kept the YSOD at bay
I would suggest running something like this before the update
-- check for duplicate prop alias on parent and child
select CT.nodeId as DocTypeID, CC.parentContentTypeId as ParentID, CT.alias as DocTypeAlias, pt.Alias as PropAlias, PT.id as PropID, PT.Name as propName
from [dbo].[cmsPropertyType] PT
left join [dbo].[cmsContentType] CT on CT.nodeId = PT.contentTypeId
left join [dbo].[cmsContentType2ContentType] CC on CC.childContentTypeId = CT.nodeId
order by pt.Alias
Then look at the duplicate PropAlias and check if any of the DocTypes is the parent of another DocType with the same property alias
If you get the issue after the update you can still run this query which should flag the same doc types referred to on the YSOD
V7.2 InvalidCompositionException
Hi,
I created a BasePage DocType. Then created a GalleryPage DocType based on BasePage.
I added a pageTitle property to the GalleryPage DocType, then later, unwittingly added a pageTitle to the BasePage DocType.
In Settings, when I click on BasePage, I get the following YSOD:-
"InvalidCompositionException - ContentType with alias 'BasePage' was added as a Compsition to ContentType with alias 'GalleryPage', but there was a conflict on the PropertyType alias 'pageTitle'. PropertyTypes must have a unique alias across all Compositions in order to compose a valid ContentType Composition."
I think I'm screwed. Is there a way out of this so I don't have to trash the whole site and start again?
Cheers,
Craig
Looks like it's been seen before and is to be fixed in 7.2.1: http://issues.umbraco.org/issue/U4-5986
However, if there any way of getting out of it so I don't have to trash 12 hours work, I'd appreciate it ;)
Cheers,
Craig
I faced the same issue after upgrading to 7.2.1 because the previous stucture of the ContentTypes I had would currently not be allowed.
I just deleted the faulty entries from the cmsContentType2ContentType, that keeps these type relations, and after recycling the application pool everything worked like a charm.
Oh wow! You just saved my butt. Found the three entries that referrred to the problematic doc type, deleted them and restarted the app pool.
Thanks!!!
Thank you - this saved me having to rebuild my umbraco project #H5yr
I have this issue after upgarding to 7.2.2. My backoffice is pretty much gubbed, If i delete the faulty entries does that mean i will need to recreate the content types and all the pages associated will be gubbed and have to be redone?
S
I know this is a bit of an old topic but for anyone still upgrading from 7.1.6 or so where a previous developer or user added a property on a child type with the same alias as one on the parent type:
Check for these before doing the upgrade and rename the child type property
If it's too late,
Don't know if there are more hidden pitfalls but this kept the YSOD at bay
How would you identify which rows to delete from cmsContentType2ContentType
I would suggest running something like this before the update
-- check for duplicate prop alias on parent and child
select CT.nodeId as DocTypeID, CC.parentContentTypeId as ParentID, CT.alias as DocTypeAlias, pt.Alias as PropAlias, PT.id as PropID, PT.Name as propName from [dbo].[cmsPropertyType] PT left join [dbo].[cmsContentType] CT on CT.nodeId = PT.contentTypeId left join [dbo].[cmsContentType2ContentType] CC on CC.childContentTypeId = CT.nodeId order by pt.Alias
Then look at the duplicate PropAlias and check if any of the DocTypes is the parent of another DocType with the same property alias
If you get the issue after the update you can still run this query which should flag the same doc types referred to on the YSOD
is working on a reply...