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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogCSS Styling from module.cssCSS Styling from module.css
Previous
 
Next
New Post
12/16/2008 5:39 PM
 

Ok, that makes sense.

But changing the p tag/class in my skin file in order to affect change in the body of my blog posts?  Here's my dilemma: that changes every p tag in my entire site.  This is "bad," in my opinion.  How is this avoidable in my situation?  What should I do, aside from creating a special container?


Chad Voller -- MCP, DNN Aficionado
Leapwise Media
View my View Chad Voller's profile on LinkedIn
 
New Post
12/16/2008 6:15 PM
 

In order to adjust the styling of a p element within the blog post, add a style with the selector .blog_body p, so that it only applies to the p elements under the div styles with the blog_body class.

Hope that helps,


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
12/17/2008 2:50 AM
 

Hi all,

as you know, the module.css, skin.css, portal.css overriding is intended to help users who cannot alter the module.css file to style their website. This is useful specially under multiportal installs. This also prevents the loss of styles when upgrading the blog module version, and allows as much consistency as possible with the portal styling.

The portal administrators can always override the module.css styles in portal.css, thus styling only the text rendered by the blog module. If you find that some more styles would help you style the blog better, just let us know, and we will consider adding them to the markup and to the module.ccs file, to enhacnce styling possibilities.

Best regards,
Dario Rossa

 
New Post
3/25/2010 5:18 AM
 

 I find this discussion thread a bit confusing.  Here are some of my issues:

1. I run a web site in which unfortunately the blog entry paragraphs in the blog module are different than paragraphs in an HTML module (I was trying to get them to be the same).  Looks like the skin.css Normal section does have control over paragraphs of the HTML, but not the same control over paragraphs in the blog entry.  

2. Modifying blog_body in the module.css file does change the blog paragraphs, but the end result is still different than the paragraphs in an HTML module, even if css values are the same.  Adding blog_body p does the same thing as modifying blog_body.  The problem with blog_body and blog_body p is that now paragraphs look different under Google Chrome and IE (The only way to get the paragraphs to be the same is to actually use inline css for each <p>.  Changing the skin.css, on the other hand, produces consistent Chrome and IE results for the paragraphs in the HTML module and, if I remember correctly, for the blog module, with the only issue that then the blog and HTML modules differ).

My issues are mostly with font size.  I am not looking for a solution, as I am happy to add the font-size css inline, even though that makes my HTML heavier.  I am just mentioning these as they may prove useful for future development consideration.

 

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogCSS Styling from module.cssCSS Styling from module.css


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