urls /privacy and /terms getting defaults instead of Site Settings defined pages

[morganalori]

Hi, got a question about privacy/terms and Site Settings. Why do the /privacy and /terms pages not redirect to the Site Settings specified pages when available instead of the built in generated ones? There is no way currently to prevent default generated /privacy and /terms from displaying, except creating a page with that exact page name.

I did find #6373 which is related, but different.

DNN Version: 9.13.3

Site Settings has entries for Terms and Privacy pages (introduced for GDPR with #2369). Currently the Site Settings: PortalSettings.PrivacyTabId and PortalSettings.TermsTabId, are only used/honored by the DNN controls Terms.ascx/Privacy.ascx as part of a dnn theme/skin. However if someone goes to the /privacy or /terms urls, they get the DNN built in one from DNN Platform\Website\App_GlobalResources\GlobalResources.resx instead of the Terms/Privacy page specified by the site manager in the Site Settings.

[valadas]

It looks like sending the user to the custom page for terms/privacy was handled in the skinObjects and not the URLs. I'd open an issue about it mentioning it is the URL and not just clicking the skinObjects.