I'm running DNN 4.3.4 and I have a page (several in fact) defined as a navigation link to another page in my site. In cases where DNN renders links to these pages everything is ok, DNN renders the page links to directly reference the linked-to page names, however, if one of the linked-from pages are requested directly the link isn't followed. That is:

Page "A" is defined as a link to page "B". If a link to page A is rendered (say on a menu) it's rendered to request page B directly. However, if you request page A by typing in the URL for page A you get page A, not page B.

It appears the navigation-link parameter on a page is honored by the NavigateURL function, but not by the actual page renderer. If the page renderer gets a request for a page that is a navigation-link to another page it ignores that fact and simply renders the requested page.

Am I missing something here? I've "hacked" a fix for this by modifying the default.vb code to check if the ActiveTab.Url property is non-blank, but I would have thought this was already handled. If I'm missing something point me in the right direction, if not, I'll cleanup the fix and contribute it.

-Walden

Not to be thick, but where it that "well explained" I didn't see anything in the downloaded PDFs or the online help. As for the support site, were you pointing me to a specific issue, or suggesting that I report it as a bug?

-Walden