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
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 :
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
But for # purposes not sure that covers us as can't leverage a contentFinder?
Any other suggestions?
is working on a reply...