1

Currently Dynamic component unpublishing manages the hyperlink on the website page by removing the hyperlink leaving out the as plain text whereas in case of binary/multimedia component unpublishing the hyperlink remains on the webpage and redirects to 404 page. We want to include similar functionality for binary links i.e hyperlink to be removed, when the linked binary is unpublished. Also, the hyperlink needs to be reactivated then the binary is republished.

Please suggest.

Improve this question

1 Answer 1

Reset to default
1

Unfortunately, binary links are handled very differently from component links for a very basic reason: component links "live" on pages, while binary links have their own URL. In other words, at publish time it's nearly impossible to determine the URL for a regular component (it could be in many different pages, link priority needs to be calculated, etc), while binaries already have a pre-defined URL.

I do not think you can achieve this without custom code, you would need to create some logic yourself that checks if the binary is published while rendering the pages & links. Maybe you can try treating binary links as "regular" component links, but I can't tell without some testing.

Improve this answer
1
  • @puf had a good explanation on TridionWorld years back for how typical binary "publishing" wasn't the same as other content. With templating, binaries are added to packages and removed when the count of items linking to them gets to zero in Content Delivery. However, with a Component Template we can publish and unpublish binaries. Anyways, I also think binaries could be handled with the BinarlyLink tcdl tag. Alternatively, tcdl ComponentLink would need to have Binaries on Pages as Component Presentations.
    – Alvin Reyes
    Commented Feb 16 at 19:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.