The easiest thing to do is to follow the directions at https://support.managed.c...nn-terms-of-use.aspx

You will want to edit both MESSAGE_PORTAL_PRIVACY.Text and MESSAGE_PORTAL_Terms.Text

Depending on your likes, you can make small changes to what is there, or erase everything and enter your own texts.

You will also see how those pages use DNN Tokens to bring in items from the Site Settings, if you want to use them. For a single site, though, it's often smarter to replace tokens with the exact text that you want to use.

And, you see that you have several choices for scope. Usually you would do this for the site in question.

Thanks Joe, but I don't want to change the text, just the name of the entity, which from the template is [Portal:PortalName].

I'd rather not hard-code the name by replacing this tag. Is there another tag or way to do this please?

AFAIR, the name is specified in Global resources, the link title in the TERMS and PRIVACY skin objects should be editable in resources files in folder admin/skin. If you are using language editor in Host or portal mode, your modifications will not be overwritten during DNN Platform upgrades.

Thank you Sebastian. You can see the business need for what I'm asking about? It would be useful if DNN had another Tag called something like Business_Entity_Name that could be used in these types of circumstances, i.e. as compared to the descriptive words used for the Site Name.

Perhaps something to add to the roadmap, if not already under consideration?

Jeff,

I appreciate what you are asking for, but that's not likely to happen short of sponsoring such an addition.

Also, I don't really appreciate the implications. All that you need to do is do a quick edit and replace "[Portal:PortalName]" with whatever you want to appear there. Then you are done. And, you can make this change globally for all portals, or for thus one portal. Simple, quick, works, and it will survive DNN version upgrades.

Maybe you can explain the reluctance to make that simple change. You might be able to change my thinking if I understand your needs better.

Most times my clients have wanted to scrap the boilerplate privacy and terms pages and replace them with verbiage provided by corporate lawyers (!!).

Thanks Joe. In scanning through the resx file, I can see many instances where a tag like Portal:OwnerName would be preferable to where Portal:PortalName is currently used, e.g. signing off on emails. I can also envisage other situations here having such a tag would be beneficial.

I guess if site owners simply have their name as their site title, then no problems. But for SEO, I understand having some descriptive text in the title helps, which is what I've done.

I've now made the changes you suggested, even though I'm usually reluctant to go deep into a product's provided files to make custom changes. But as you say, in this situation, they won't be over-written with an update.

Jeff,

I never use these standard privacy statements and terms of use from the resource files, as it is not easy to edit them. I create two pages (hidden from the menu) for that. In older DNN versions, you had to set the Url for these pages to /privacy and /terms, but now it is possible to set these pages in Settings >> Site Settings >> Site Behaviour, and you cn use a simple HTML module to edit the texts, add images, links to documents etc.

Happy DNNing!
Michael

Posted By Michael Tobisch on 23 Aug 2021 02:03 AM
Jeff,

I never use these standard privacy statements and terms of use from the resource files, as it is not easy to edit them. I create two pages (hidden from the menu) for that. In older DNN versions, you had to set the Url for these pages to /privacy and /terms, but now it is possible to set these pages in Settings >> Site Settings >> Site Behaviour, and you cn use a simple HTML module to edit the texts, add images, links to documents etc.

Happy DNNing!
Michael

I agree with Michael,
Although I can see an advantage in an extra token when using the resx files (I can think of a few more actually), I do think that as soon as you need more flexibility than the current resx option, it's best to just use a custom page with an HTML module.
Especially because editing these resx files is not very accessible for most Admin users

 

Another pro of custom pages: You can easily add a "Last changed" date to be GDPR compliant for the privacy statement (no, there is no token for that afaik, but what's wrong just writing the date?)

Happy DNNing!
Michael