You could create a node that is hidden from navigation (umbracoNaviHide property true/false) that holds the content you want to reference from different nodes.
Those nodes that reference that node, could have a content picker to point to that node and the template could render the content out.
Thanks for the response. We've done something like this in the past, I was just wondering if there were other ways of doing it. I'll probably stick with creating a special doc type just for selecting other content.
You could hook the publish event and ensure that if a parent was modified then the properties are set on the child for each relateDocumentOnCopy link using the RelationService.
However this will all appear pretty mysterious to users and I don't recommend it. There may be another way to do what you are planning to do which is more visual and intuitive. Can you describe your specific use case / user story for us?
Multiple links - one source
Is it possible to create multiple entries in the site tree but all redirecting to the same content.
I'm looking at the simplest way to re-use authored content in multiple places, but only have to update it once.
Thanks
Paul
Hi,
You could create a node that is hidden from navigation (umbracoNaviHide property true/false) that holds the content you want to reference from different nodes. Those nodes that reference that node, could have a content picker to point to that node and the template could render the content out.
Would that work for you?
Hi siko,
Thanks for the response. We've done something like this in the past, I was just wondering if there were other ways of doing it. I'll probably stick with creating a special doc type just for selecting other content.
Thanks
Paul
The best way to do this would probably be to use Umbraco Relations, though I am still fully understanding them myself: https://umbraco.com/blog/getting-to-know-umbraco-relations/
You could hook the publish event and ensure that if a parent was modified then the properties are set on the child for each relateDocumentOnCopy link using the RelationService.
However this will all appear pretty mysterious to users and I don't recommend it. There may be another way to do what you are planning to do which is more visual and intuitive. Can you describe your specific use case / user story for us?
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.