We have moved to GitHub Issues
Created by Tom Steer 03 Dec 2014, 15:49:36 Updated by Robert Lewis 04 Jun 2015, 19:19:24
There seems to be an issue with multi level doctype inheritance by where 2nd (possibly deeper as well) level doctypes aren't getting the properties from the top level doctype.
I've attached a screenshot of an example, you will notice that the Home node doesn't have the SEO tab yet it is present on the Base doctype.
Are you using compositions for this? Please note that in the final version of 7.2 the compositions option will be more strict in what you can and cannot compose together. This is to prevent circular dependencies from happening which is too easy in the RC version. You might not be able to build the doctype structure that you're building now in the final version of 7.2.
No this isn't using any compositions, it was originally but then i changed it back to just using inheritance as you can see from the screenshot attachments.
Could you do me a favor and export Base (just right-click it and export) and attach it here so I can have a look?
Just attached it :)
Ah, I was hoping that would also include menu and home but it didn't, could you export those as well please? :)
Sorry Seb had a bit of a hectic day with servers today. Here are the exports for Menu & Home.
Seems others are experiencing this too: http://our.umbraco.org/forum/umbraco-7/using-umbraco-7/59555-Umbracpo-v72-Doc-Types-lose-inherited-properties
From the tree we see that Base is the parent of Menu and Menu is the parent of Home. Yet looking at the UDT files, we see that Home is composed of Menu, but Menu is not composed of anything. This is not normal, as a data type should always at least be composed of its own parent.
There was a possibility in 7.2.0 pre-RTM releases (betas & RC) to remove the parent from the compositions, but that should not be possible anymore with the RTM version.
Can you confirm that you obtained this situation with pre-RTM releases?
Now, on how to fix it... it it tricky because the UI will not let you check/uncheck the parent in the compositions list. Best (prob. only) way to just fix (as opposed to re-create everything) would be by adding a row in the DB - let me know if you want instructions.
Confirmed: create Type1 > Type2 > Type3 and then save Type2, it looses the Type1 composition though Type1 remains the parent. Working on it.
Committed 9dcba6a67929aca0dc4a60c33275e3da25b266f6 to 7.2.1 - should fix the issue.
Just as an FYI: There is a manual way to fix this in 7.2.0 and that is to go into the cmsContentType2ContentType table and add the parent/child combinations back that are missing. However, if you then save a document type in the interface this problem will occur again so you'd need to fix it in the database again.
Testing the fix now.
This seems to work now. For people to whom this already happened, you will have to recreate the links between document types in the database. If you copy in the attached umbraco.dll then you can safely update your doctypes from the interface until we release 7.2.1.
So this is the exact same umbraco.dll that shipped with 7.2.0 final with the fix for this issue applied, no other changes, just the fix for this issue.
This happened to me this morning. However after relinking the document types all the data that was recorded for the document type against the parent is all gone :( The hotfix returns the property fields but none of the data as I suspect Umbraco was helpful and saw that the document type no longer had the property so no longer needs the data so dropped all that :(
Going back to a DB backup to try and recover the property data for the lost fields.
One other thing. After re-establishing the connection and putting your properties back the Cache doesnt update. Im fighting through this one at the moment will report how I fixed it once I have it fixed up.
Ok it does update the one on disk but not in memory. Had to touch the web.config to get it bring back the cache.
Back to normal again with 300 pages of screwed up content restored. It may help others train of thought when trying to fix it so thought I would add my process here. The process to get back on track required some real messing around.
This bug bit us too this morning. No major harm done (it only affected a few pages so reentering the data was trivial) but it really should be brought up on the blog and in a mail together with the hotfix as it could potentially mean huge data losses for people.
A fix, plus fix for U4-5986 is going out today.
What happens if my client doesn't have a backup of the database and all they SEO etc has gone?
Backwards Compatible: True
Affected versions: 7.2.0
Due in version: 7.2.1