And I'd like to thank you for putting in all this work with testing, and to tip my hat to Steve. However, at the end of the day, we have a module that doesn't work.

I'm a little shocked that a module in such disrepair would be released. I've had nothing with trouble with it and had to come to the Forums to discover that it's not me, it's the module. Having a core feature of DNN broken like this is not good. For me, tyring to put together a website under severe deadline pressure, it has been disastrous.

I want notifications like everyone else, but I wish that the Events module at least worked with these features turned off. It doesn't. I can't delete any created events--what is with that?

If I sound frustrated, it's because I'm deeply frustrated. I think DNN is great overall and am enjoying working with it, but a broken core module is bad news.

Jack

---

Jackson San Francisco, CA

First off this is not an excuse, but an explanation. The project teams are supposed to work as autonomous, independant teams, with a coreteam liason who is their contact when necessary. Previously we had periods where work was held up greatly as decisions had to be made/ratified by key people who were snowed under in work, so the decision was made to form project teams who work independantly. When this independance works, it's works well (e.g. the user defined table team have had 15 releases in the past year), however when a project is unattended for any reason it can be a period of time before we notice (I get 100+ emails per day and I don't monitor the project's apart from blogs and UDT).

I will raise this as an issue in this weeks coreteam chat.

Cathal

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

Ok.  I've worked over the past three days on re-writing the events notification component.  It will be implemented as a part of the next release.  It seems the issue of not sending notifications was a problem with sending HTML type email messages from the scheduler module.  I have re-written the component to send "plain text" email instead of HTML email.  I verified this issue, because I could make the previous code work every time, if I added the machine\ASPNET account to the machine Administrators role, added the machine\ASPNET to the SMTP local machine "operators" role, then restarted IIS.  So, it is fixed and I changed the code to be more intiutive for users wishing to subscribe to notifications.