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...DotNetNuke mothership a little unstable?DotNetNuke mothership a little unstable?
Previous
 
Next
New Post
8/23/2006 11:19 AM
 
I'm sure the core team are aware of this by looking at the error logs, but for the last couple of weeks I have been receiving numerous sporadic errors on this website - quite often the Forum times out, but this morning I got the yellow error message screen of death (.NET) when I tried to view it.

Are these problems known about?

On a side note - the level of Forum interaction seems to have a reached a new low - the last couple posts I have done (not inc. the ones where I was answering posts obv.) have gone unanswered. Not sure where the problem lies - I was hoping the new 4.3.3+ releases would breathe life into the project. Any one else noticed this? Maybe it's just because the RSS feeds arn't working? These need to be fixed ASAP so that people see and respond to the information that matters to them. Don't even get me started on having to log in here every single time ;)


Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
8/23/2006 11:45 AM
 
<not happy>

Just look at the forum source, it explains alot.

Looks to me as if they despiratly needed a forum to switch from www.asp.net to dotnetnuke.com. And they picked the first one who was willing to trade his source against a core team badge.
There's zero integration with the core, just plain weird design (no .NET design style or DNN design style, just a bunch of stuff that happens to work) and a whole bunch of stuff that's deactivated because it breaks something else.

Anyhow I thrust Crispy will find a way to clean up this mess. But if it were up to me I'd design a new forum from the ground up, tightly integrated with DNN and It's menu/roles system.


The rest of the DotNetNuke site runs like a charm, but tabid 795 is just a pain.

I hate logging in as well, should be configured to at least remember me for a week. Now It's probably less then a day. It's even worse that when I want to reply, the forum doesn't even remember the thread I was viewing after logging in.

Regarding the stability, I now have the habbit of doing ctrl-a, ctrl-c before I try to click update. because I always lose my half a page explanation to a newbie, and I don't feel like explainig things twice on one day. So yet another newbie question ends up unanswered.

</not happy>

Edit your Skin.xml and Container.xml files with:
Yannick's SXE
 
New Post
8/23/2006 1:15 PM
 
I had been pushing for my agency to use DNN as its intranet, but due to all the things you mentioned above, I am abandoning that idea. I have also been thinking about starting a small business with a site based on DNN, but now I'm not so sure about that, either.

I really think the core team needs to do a lot of thinking about what direction they want to take with DNN, and focus on getting that stable.  This new release appears to be a huge mess.
 
New Post
8/23/2006 1:46 PM
 
There are some huge issues that need attention quickly. I visit this site at least 3 times a day to keep a finger on the pulse of DNN. I have used DNN since it's broke away from MS.

During recent visits here (last one-two month) it's really shooting dice as to which error I'll recieve the dreaded compilation error or the slightly more frequent :
A critical error has occurred.
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Although I have no problem with DNN bringing the forums "in-house", but the means to support it don't seem to be available.

It's ashame that something like this could jeopordize a brilliant product.

Just my opinion...


 
New Post
8/23/2006 2:19 PM
 
Don't get me wrong here, DotNetNuke is a wonderfull product. In my opinion the best portal system that exists. The last years I build every project on top of it.


It's the forum module thats bad. I always recommend people that need a (large) forum to buy one of the commercial forum solutions. The module works on small forums, but Dotnetnuke.com is the proof this module doesn't work on large forums.

Edit your Skin.xml and Container.xml files with:
Yannick's SXE
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DotNetNuke mothership a little unstable?DotNetNuke mothership a little unstable?


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