Hi all,
I'm seeking a bit of input on the best ways to go about creating 'symbolic link' type functionality for umbraco content.
eg: Create a node which is a symbolic link (aka 'target') for another 'origin' node then every change to the origin appears on the target, this is so content can appear in multiple places in one site, or in multiple websites (assuming the websites share an umbraco instance and are managed via the 'manage hostnames' mechanism).
Any links or nodepickers will keep pointing to the same content.
Gotchas: Tags (we've separated tags into one group per site, so we'll need to manage those somehow)
Ideas
We've done something simiar in the past with a special node-type that is just a placeholder which has a picker on it to piont to the origin, we had custom event handlers to wire all that up, and then all our nav/listing templates have to replace all the 'placeholders' with the origin before rendering.... This solution seems a bit clunky.
I've thought about using umbraco relations (we use them elsewhere in the site) ... This solution makes it more opaque for the users to reason about.
In either case we could either maintain only a link or maintain an entire copy. (I guess a copy has less impact on nav/listing templates)
Creating Symbolic Link Type Functionality
Hi all,
I'm seeking a bit of input on the best ways to go about creating 'symbolic link' type functionality for umbraco content.
eg: Create a node which is a symbolic link (aka 'target') for another 'origin' node then every change to the origin appears on the target, this is so content can appear in multiple places in one site, or in multiple websites (assuming the websites share an umbraco instance and are managed via the 'manage hostnames' mechanism).
Any links or nodepickers will keep pointing to the same content.
Gotchas: Tags (we've separated tags into one group per site, so we'll need to manage those somehow)
Ideas
We've done something simiar in the past with a special node-type that is just a placeholder which has a picker on it to piont to the origin, we had custom event handlers to wire all that up, and then all our nav/listing templates have to replace all the 'placeholders' with the origin before rendering.... This solution seems a bit clunky.
I've thought about using umbraco relations (we use them elsewhere in the site) ... This solution makes it more opaque for the users to reason about.
In either case we could either maintain only a link or maintain an entire copy. (I guess a copy has less impact on nav/listing templates)
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.