Our site is running DNN 4.x and we are suffering from this bug, I just had to go in an do an emergency delete of our EventLog table, it had 61,000 entries in it all releated to this. We are losing user as our site crashes every 5th page, please, we are trying to run a company on DNN as our framework and we are losing customers. Release a fix or give us an emergency path.

DataCache.GetCache usage pattern causes random Null reference exceptions

http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=2403

Paul,

Telling "My Generation" to just make the changes and recompile is like a brain surgeon telling his patient to just take the tumor out of his own head. Not everyone in the DNN community is proficient enough to mess with the source code and compile it to fix a major bug that crashes their sites.   In fact, it would be fair to say that most people are uncomfortable doing that and are waiting patiently for the DNN core team to finish writing their books, and turn their attention to trivial things like making official releases to fix critical bugs.  I used to be a big advocate of DNN, but not anymore.

- Oliver

ocorpuz,

I understand that there are people that are not comfortable working with the source code and recompiling and if I was just making a general comment i wouldn't have said something like that.  There probably does need to be a patch released.

I was responding to myGeneration who runs mygenerationsoftware and most likely knows more about comping the source code than I do.  I was trying to point out to him that if his site was having such a bad problem he could probably fix it faster than the core team could get a patch released.  I didn't mean to piss anyone off.

Hate me if you must but don't take it out on DNN.  I'm just a user that's trying to be helpful. Sometimes it doesn't come out that way though in my writing.  :) The wonderful thing about opensource software is that while the core team works on the documentation we all want no one really has to wait for new features or fixes, someone in the community has probably already fixed the problem and put the fix up somewhere. You only have to ask.