"nb Setting the cache time to 0 seconds clears the problem. So it's definately a caching problem.

Thanks

Alex"

Thanks so much for figuring out the issue with the events. I had the exact same problem and setting the cache back to '0' solved the problem. I dreaded coming in here and trying find a fix. Between the search taking minutes to process and so many problems / issues / bugs going unanswered this was a pleasant surprise.


So many times the people in the 'know' here at DNN are pointing fingers (read guessing) as to where the problem could be, all the while the problem is right under their nose. Yet they ignore such and leave the problem unresolved. Nice for a change to see a problem actually resolved. Well not resolved but a work-around. I wish some of the people who claim to be in the know would look at this post and rethink.

Thanks again for saving me hours of research.

Chris

PS My events was a completly fresh install with zero events.

Sorry, I had a lot of difficulties formatting with the FCKEditor...

The code should have read:

'****DO NOT CHANGE THE NEXT SECTION FOR ML CODING ****
' Used Only to select view dates on Event Month View...NOTE: SelectedDate is NOTE!!!
Dim initDate As Date = New Date(Me.SelectedDate.Year, Me.SelectedDate.Month, 1)

'KS fix bug where date has not been selected yet, so set to first of current month
If Me.SelectedDate.Year = 1 Then
    initDate = DateAdd(DateInterval.Day, (1 - Today.Day), Today)
End If

startDate = initDate.AddDays(-10) ' Allow for Prev Month days in View
' Load 2 months of events. This used to load only the events for the current month,

Cheers

I've noticed this issue is still not entered into Gemini, and I'm definitely still experiencing it with the latest releases: DNN 4.8 and Events module: 3.03.08.

Sure you can disable caching as a workaround, but I didn't learn that until wasting a good 4 hours diagnosing the problem.  At the very least, caching should be disabled so you can't accidentally kill your portal (and webserver), or ultimately it would be nice to see the module actually implement caching correctly.

Has anyone tried to find the problematic code at least?  I don't have much time on my hands, but I can try if the devs or testers are having trouble reproducing this.