Hi there,

We've recently upgraded to 4.04.00, and are experiencing this editor when the DNN tect editor is trying load up on the screen.  The problem is intermittent, and sometimes it will work for hours, and at other times not at all. Most commonly however, it will fail the first time you try and load the texteditor, and then work fine after that.

It is most commonly happening on the Forum and Blog module, but other system editors like the language editor all seem to work fine.  We have some custom built modules that use a different html editor, and they work without a hitch.

Any clues on this problem would be greatly appreciated.

Hi Crispy,

The problem is that when you go to add or edit a postig into the forum, the system bugs out with a critical error and a message that says "Object reference not set to an instance of an object." Underneath this message it returns you to the forum home.

The problem is intermittent most of the time, none existant at other times, and full on for the remainder. When trolling the net for answers to this problem it appears there might be a caching problem, or the return of a null object.. See

http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/36/threadid/12539/scope/posts/Default.aspx

In the mean time we have changed the DNN configuration to memory, rather than disk caching, and set the level to heavy and this seems have almost eliminated the problem. 

I was just wondering if anybody had experienced this problem, and if so what was the fix? I'm not suggesting a change to code for the forum module, as I know a new one is due out soon, and this is probably not a code issue. I'm certain is it something to do with the configuration of our server, but I was just after some ideas.

Cheers Greg

 

I get that error all the time and have figured out that I only get it when making an update to a module and only if I'm impatient and click something else before the page is finished loading. I've solved it by "growing" some patients (a hard thing for me). I haven't run into the error since.