Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Mike Chambers 636 posts 1253 karma points c-trib
    Nov 21, 2018 @ 11:36
    Mike Chambers
    0

    UrlProvider/ContentFinder and IgnorePublishedContentCollisions

    UrlProvider and Content Finder...

    the Collision detection only looks at the url and not any querystring/hashes..

    Usecase for me.. Content Nodes :

    TabbedContent
      - tabOne
      - tabTwo
      - tabThree
      -etc..
    

    I'd like tabOne.Url to be ../tabbedcontent#tabOne shown on the info page and so links added to the node would show the parent with the page as the active tab.

    I can do this with UrlProvider, but the backend complains about url collision , to be expected as it is directed at the parent.. however the url is made unique by the # (or we could have a querystring alternative again that approach complains about a collision)

    I can see from 7.12.4 that we should be able to do

    contentRequest.PublishedContent = content;
    contentRequest.IgnorePublishedContentCollisions  = true;
    

    But for # purposes not sure that covers us as can't leverage a contentFinder?

    Any other suggestions?

  • 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.

Please Sign in or register to post replies