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...Skins, Themes, ...Skins, Themes, ...NormalTextBox FrustrationsNormalTextBox Frustrations
Previous
 
Next
New Post
10/15/2009 1:07 PM
 

I am working on a skin and I have defined a class like this..

 

.NormalTextBox {
font-family:Tahoma,Arial,Helvetica;
font-size:12px;
font-weight:normal;
 
New Post
10/15/2009 2:57 PM
 

You are right, it is logged as an issue, but it has not been solved yet.

http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=10705&PROJID=2

 
New Post
10/15/2009 5:45 PM
 

Seems an easy enough fix right? Just seach for NormalTextBox in the admin modules and away we go.  How do we get traction on the issue?  I suppose since it is thus far only seen by me in admin modules it isnt a huge concern?  Any idea why I never get notifications from this board even though the option is checked?

 
New Post
10/20/2009 4:41 AM
 

There are issues with the notifications on the version used here, these should be solved in the new version.

Because the forum has a lot of posts, the upgrade is taking more time then expected..

What could help is an analysis of all the places the issue appears. I currently don't have time for this, if you do please feel free.

IMO it will help to get this issue solved sooner (BTW, I don't have edit rights on the core)

 
New Post
10/21/2009 2:22 PM
 

I think this is a great idea and I know there are a number of other folks who think so also.  It would not be a difficult task to clean up, either... but allow me to explain what makes it complicated... and what needs to be considered before anything is done.

The issue is what would happen to existing websites when they upgraded...

So in order to implement something like this, we need to devise a strategy that will protect existing installations from getting "whacked" by changing all the existing CSS.  The way that usually works in code is to introduce new things that can exist side by side, encourage their uptake over some period of time, and then announce the "deprecation " (removal) of the old stuff in a future version.

Thoughts?


Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...NormalTextBox FrustrationsNormalTextBox Frustrations


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