I really LOVE Nested Content, but today found that when I had a Nested Content DocType which uses a "Macro Container" Datatype for one of the properties, it won't save the selected macro values.
It displays on the Content node correctly. I can select the macro and add parameter values, and it displays nicely in the Nested Content control, but when I save the node, the value is not stored. If I come back to the node later, the values are missing, and the property always returns "NULL" via code.
As Robert says, there's a whole discussion about this on our GitHub issue tracker, plus Roberts pull-request.
The underlying discussion for an overall solution is on-going, (abet gone stale / on the backburner at the moment). (We're in discussions of NC going into Umbraco core, so want to involve the core team as much as possible)
The current situation, (as in today) is that Macro Container is a known issue and isn't supported yet. (For reference, Upload and Image Cropper aren't supported too) :-(
Proposed solutions are either applying Robert's pull-request patch, or using Archetype... or going with separate child nodes.
Macro Container DataTypes lose value on save
I really LOVE Nested Content, but today found that when I had a Nested Content DocType which uses a "Macro Container" Datatype for one of the properties, it won't save the selected macro values.
It displays on the Content node correctly. I can select the macro and add parameter values, and it displays nicely in the Nested Content control, but when I save the node, the value is not stored. If I come back to the node later, the values are missing, and the property always returns "NULL" via code.
Hi Heather,
See this issue on the NestedContent repository:
https://github.com/leekelleher/umbraco-nested-content/issues/20
Basically, the content for macro container isn't updated early enough and we need to perform some magic to make sure we save after it's updated.
There's a pull request that gets around this deficiency here:
https://github.com/leekelleher/umbraco-nested-content/pull/22/commits
Hope this helps...
Rob.
Hi Heather,
As Robert says, there's a whole discussion about this on our GitHub issue tracker, plus Roberts pull-request.
The underlying discussion for an overall solution is on-going, (abet gone stale / on the backburner at the moment). (We're in discussions of NC going into Umbraco core, so want to involve the core team as much as possible)
The current situation, (as in today) is that Macro Container is a known issue and isn't supported yet. (For reference, Upload and Image Cropper aren't supported too) :-(
Proposed solutions are either applying Robert's pull-request patch, or using Archetype... or going with separate child nodes.
Thanks,
- Lee
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.