I have a parent document type with a tab holding one property field. It has become apparent that this is only used in one child document type. Can I move this tab without losing the current entered property values?
I dont think there would be an issue (unless anyone can confirm there is but...).
Just remove the tab from the parent and add to the child doc type, then republish your site so that the values for each of the nodes (pages) are updated eg. pages not using the property field are removed and the other nodes are updated.
Just be sure to backup your database before attempting this.
Hmm, dunno what happened there, but the responses from Jason above are actually from me. I seemed to have been logged in as him for some reason.
@Tom, I don't think that will work, as the reference to the property is an ID, so removing a property and rededfining it, will change the ID, and so the current data is stored.
Looking in the database, it looks as though you can just modify the cmsPropertyType, updating the contenTypeId column for the given property. Change it's value from the parent doc type, to the child doc types ID. You should probably clear up any saved values for the doc types that no longer use, but it shouldn't hurt your install if they were left.
If you change the value, you may need to restart your app pool for it to take effect.
Thanks guys. Of course Niels was strictly the right answer.
But, Matt kinda nailed it there. Changing the contenTypeId in
combination with changing contenttypeNodeID in cmsTab has bumped it down
the tree the way I wanted.
Moving a tab to a chile document type?
Can this be done?
I have a parent document type with a tab holding one property field. It has become apparent that this is only used in one child document type. Can I move this tab without losing the current entered property values?
Hi Tony,
Not easily. You'd currently have to do it via the database.
I may look at adding it to my Doc Type Extensions package (http://our.umbraco.org/projects/developer-tools/doc-type-extensions), but due to work load, that doesn't look like it'll be till the new year.
Matt
I dont think there would be an issue (unless anyone can confirm there is but...).
Just remove the tab from the parent and add to the child doc type, then republish your site so that the values for each of the nodes (pages) are updated eg. pages not using the property field are removed and the other nodes are updated.
Just be sure to backup your database before attempting this.
Tom
Yeah, if I remove the tab the property just moves to the generic properties of the parent doc type.
I've tried removing the property type after that and keep getting the conflict of dependencies error.
It's currently NOT possible. We're working on supporting this in JUNO (v4.6)
NA
Hmm, dunno what happened there, but the responses from Jason above are actually from me. I seemed to have been logged in as him for some reason.
@Tom, I don't think that will work, as the reference to the property is an ID, so removing a property and rededfining it, will change the ID, and so the current data is stored.
Looking in the database, it looks as though you can just modify the cmsPropertyType, updating the contenTypeId column for the given property. Change it's value from the parent doc type, to the child doc types ID. You should probably clear up any saved values for the doc types that no longer use, but it shouldn't hurt your install if they were left.
If you change the value, you may need to restart your app pool for it to take effect.
Cheers
Matt
Thanks guys. Of course Niels was strictly the right answer.
But, Matt kinda nailed it there. Changing the contenTypeId in combination with changing contenttypeNodeID in cmsTab has bumped it down the tree the way I wanted.
Thanks!
Ohh am I logged in as someone else?
(No ... :( )
is working on a reply...