I upgraded a site from Umbraco 7.2.4 to 7.4.1 ... afterwards I upgraded Nested Content package from v. 0.1.1 to v. 0.2.0, but due new changes to support multiple doc types, Nested Content doesn't map the data for the existing content and therefore no items in the editor, although umbraco.config has the old json.
Is it possible to map the old values for doc type, tab and name template for the new multi-items config?
At the moment I have to manually select the doc type in dropdown, an enter the values for tab and name template.
I've been looking over the source-code for the multi-doctype feature, which I thought was backwards-compatible... (it's been a while since I've looked at the code - eek!)
I mean that the new multi-doctype settings in Nested Content datatype config isn't set with the old values.
So before I had a doc type chosen and value for "name template", but these are not selected/set in the config - so the property editor view didn't display the values even the umbraco.config contains the "old" json property value.
But after I manually set the values of the doctype and name template in datatype config, I got the data into the property editor view in content section.
So when I open Nested Content in LeBlender it doesn't render anything because the old JSON doesn't work anymore. I could write some code which updates all Grid conten, but is there maybe an easier way to do this?
I have a solution using LeBlender and Nested Content 0.1, and are approaching the need for an upgrade. So just want to check if you ever got yours upgraded, and if it went ok :)
Map data when upgrading package to v. 0.2.0
Hi..
I upgraded a site from Umbraco 7.2.4 to 7.4.1 ... afterwards I upgraded Nested Content package from v. 0.1.1 to v. 0.2.0, but due new changes to support multiple doc types, Nested Content doesn't map the data for the existing content and therefore no items in the editor, although umbraco.config has the old json.
Is it possible to map the old values for doc type, tab and name template for the new multi-items config?
At the moment I have to manually select the doc type in dropdown, an enter the values for tab and name template.
/Bjarne
Hi Bjarne,
I've been looking over the source-code for the multi-doctype feature, which I thought was backwards-compatible... (it's been a while since I've looked at the code - eek!)
v0.2.0 should update the v0.1.1 data...
https://github.com/leekelleher/umbraco-nested-content/blob/0.2.0/src/Our.Umbraco.NestedContent/Helpers/NestedContentHelper.cs#L46
... which should get called when Umbraco gets the value from the database ... hmm, I'm a bit confused why it's not being called.
Can you raise an issue on our GitHub repo?
https://github.com/leekelleher/umbraco-nested-content/issues
Thanks,
- Lee
Hi Lee
Okay, I'll raise an issue on the Github repo..
Thanks, /Bjarne
Thanks Bjarne.
I think I misread your post, do you mean the content (property) value isn't being mapped, or that the DataType's prevalue isn't being mapped?
Cheers,
- Lee
Hi Lee
I mean that the new multi-doctype settings in Nested Content datatype config isn't set with the old values.
So before I had a doc type chosen and value for "name template", but these are not selected/set in the config - so the property editor view didn't display the values even the umbraco.config contains the "old" json property value.
But after I manually set the values of the doctype and name template in datatype config, I got the data into the property editor view in content section.
/Bjarne
I'm having the same issue. Is there a way to keep the content from the 0.1 version in combination with LeBlender? Topic: https://our.umbraco.org/projects/backoffice-extensions/leblender/bug-reports/81981-leblender-nested-content-and-umbraco-75
Jeroen
The problem is that it's Nested Content inside LeBlender which saves it inside the Grid. So for Nested Content 0.1 the JSON inside the Grid is this:
And for Nested Content 0.2 or 0.3 the JSON inside the Grid is:
So when I open Nested Content in LeBlender it doesn't render anything because the old JSON doesn't work anymore. I could write some code which updates all Grid conten, but is there maybe an easier way to do this?
Jeroen
There is also a Twitter conversation about this: https://twitter.com/j_breuer/status/811237916609544197
For now I'll keep using Nested Content 0.1 because I don't need the new features and I don't have time for a custom upgrade script.
Jeroen
Hi Jeroen
Are you still on 0.1?
I have a solution using LeBlender and Nested Content 0.1, and are approaching the need for an upgrade. So just want to check if you ever got yours upgraded, and if it went ok :)
Sorry I didn't solve it because using LeBlender and Nested Content 0.1 was good enough for us.
Jeroen
Hi Jeroen
I needed to upgrade, so wrote a script for migrating. Created a gist if anyone would be interested: https://gist.github.com/skttl/7b6b02bb4506ef89d45db76904427e23
is working on a reply...