Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Content rating header tag conflictContent rating header tag conflict
Previous
 
Next
New Post
1/4/2007 9:19 PM
 

My query is regarding how one should go about specifying a site content rating meta tag for a particular portal.

I notice that default.aspx already has <meta name="RATING" content="GENERAL"> in the head. That means it's fixed in place for all portals in the instance. '

I can't see a way to add a rating tag for a specifc portal, but there is a place to add header tags per page which would at least be part of the solution.

Apart from the obvious inconvenience of having to set the rating up again for each page, does it even work like this? If I put a tag in there with a different rating than the one in default.aspx, the site ends up with two rating tags in the header.. which is presumably incorrect and ineffective.

I could just remove the one from default.aspx, but I'm hoping there's a smarter way to achieve this.

Thanks for any comments on this.
Rob

 
New Post
1/4/2007 9:52 PM
 

Hi Rob,

Unfortunately those meta items are not configurable.  You might want to log this as an enhancement request in Gemini.

As a workaround, you could remove the meta items completely from default.aspx and use the page header field. This field did have a bug that encoded the output, but I think it was fixed in 4.4

What I would like to see is all of the head field moved to a configuration setting that is controlled through a resource file for default and then optionally modified on each page's settings. Then you could add Javascript links, CSS links and so on in regular html.

Oh, and if you want complete control of the output for each page you could use PageBlaster


DotNetNuke Modules from Snapsis.com
 
New Post
1/4/2007 11:59 PM
 

Thanks for the reply John, I'll go and add it to Gemini as it does seem like something worthy. There's definitely a need to provide portal-specific default page headers.

Rob

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Content rating header tag conflictContent rating header tag conflict


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out