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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Why is DotNetNuke giving itself a black eyeWhy is DotNetNuke giving itself a black eye
Previous
 
Next
New Post
8/20/2008 7:21 PM
 

It is important to note that the issue in question with Firefox and the CSS that controls the buttons in the forum - is only an issue with FF3 - it is not an issue with FF2 or IE7 the two main browsers that were in use at the time of release of this version of the forum.

I am sure that Chris and his team are working hard to get the next version of the Module ready for release.

This site was not the only site affected - over 75% of the Extensions and Themes I had installed in FF2 broke on the upgrade to version 3 - and most are still not updated or are in Beta in the FF3 version.


Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here
MVP (ASP.NET) and
ASPInsiders Member
View my profile on LinkedIn
 
New Post
8/20/2008 10:50 PM
 

I wasn't going to post in this thread anymore and I should probably keep my mouth shut but now I can't help myself.

Edit- I had typed out a long post from being embarassed that a group of obviously very intelligent people whom I respect can't work out their differences to being offended at the accusation of not knowing or appreciating the effort that Crispy has put into the forum module.

But the reality is that people like Andrew, Jeff, Rob, myself, etc. don't own the project, have few if any ways to contribute, and if the powers-that-be aren't concerned about the issues we have talked about then posting here is just a big waste of time.  Rob (I think or Jeff) was right and several corp/core members have made it pretty clear to me in this thread - DNN is what it is - you either accept it as is or find another solution. Don't bitch or try to help because this is an open source app not a community app. I get the big picture now and I still like DNN better than anything else I've seen - it is still open source so I'll be sticking with it (not that I'm important enough to matter)

Now to try and salvage some usefullness - with regards to the FCK editor - I had been looking hard at Cute and RAD and in a thread Sebastian got me looking harder at FCK. There are plug-ins available for FCK that will do most of the things that Cute and RAD will do. i.e. spell checking, image maps, code highlighting, image editing, etc. I've heard that the image map plug-in works but haven't heard anything about the others. However, I think Andrew may have been speaking about the DNN site specifically in regards to the FCK editor - for the answer to that see above.

Last but not least:  Andrew shouldn't feel responsible for stirring up a hornet's nest - it has been going on for some time now.

 

 
New Post
8/21/2008 12:48 AM
 

I would like to suggest one area in which an interested, passionate individual could contribute to the DotNetNuke project.  Granted, it wouldn't be in a development capacity, or jumping directly in as the site webmaster, but it would be of great service nonetheless.

In past team chats, I know the topic of the DotNetNuke entry at Wikipedia was discussed.  http://en.wikipedia.org/wiki/DotNetNuke  Someone had mentioned that the entry was dated, lacking sources, or tagged.

One way to look at this is to say "Shouldn't the marketing team at DNN Corp. be handling the Wikipedia entry?"

Another is to say, "I'm a passionate DotNetNuke community member, with alot of knowledge, looking for my place to chip in.  The Wikipedia entry is the second listed result in Google on a search for the term "DotNetNuke", and it would be of great benefit to the community to make that Wikipedia entry as complete as I can."

There are no barriers to updating listings in Wikipedia.  While there are subtle things to learn about making updates to listings - what is acceptable info, what is neutral info, etc. - anybody can help contribute to the Wikipedia entry for DotNetNuke.  The listing currently needs references added, and certain sections could be added or expanded (ie. architecture, modules, etc.)

The question will likely come up - why should resources be put into a Wikipedia entry, why not build our own wiki?  Answer - even if we do tackle our own wiki, the Wikipedia entry will still remain highly visible and highly-trafficked - and important property for anyone searching for info on DotNetNuke.

So there's one suggestion.

 
New Post
8/22/2008 10:59 PM
 

To correct the original issue, someone with access may want to try adding the following CSS rule to the

http://www.dotnetnuke.com/DesktopModules/Forum/Themes/DNN/dnn.css file:

.Forum_Container {border-collapse:collapse}

This worked when I did it with FireBug here on the site.

 


DotNetNuke Modules from Snapsis.com
 
New Post
8/23/2008 8:44 AM
 

Thanks John.  That fix has been tested and posted.  The forums team along with Timo have been futzing with the CSS for a while to figure it out, nothing I have seen suggested border-collapse was the issue.

 


Joe Brinkman
DNN Corp.
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Why is DotNetNuke giving itself a black eyeWhy is DotNetNuke giving itself a black eye


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