And why with all the mighty development power of the DNN team can't they just take the existing release, fix the notification bug, and release it? That would shutup 99.999% of the comments here. The ajaxy bells and whistles version Chris P has been sitting on could then be completed in another year for all I care.
Keep in mind that I have switched our site to Active Forums and have to say its great. The cost is minimal, performance, features, and support is great.
That said, I do still care about the state of the Core forum module. It is important that the DNN team is more aware of the community's input. Why have a black eye like this? Why let an issue like this drag out when the fix is so easy?
Forget Chris. If he's busy and can't release (understandable as a volunteer), then someone else should step up, spend the 2 hours to fix the notification bug, and release. Chris can then release the new version at his leisure.
Notice that no one is clamoring for the release because of the new features; everyone just wants a module that is NOT BROKEN.
DavidToohey wrote
I do think the issue is that we have been here to offer support as best we can, and show our appreciation for what has and is being done... but how can we seriously continue to show support and appreciation when we are continually treated like this?
That is not rhetorical. I really do want to know!
For a good year + we've been strung along waiting for a bug fix and told how it is imminent, can see it working fine with the fix at dnnforums.com but for months we've been shown absolutely no respect by leaving it completely open and up in the air.
What can't someone at DotNetNuke not tell us the actual situation, what is happening, and what the hold up is when it seems a fix has been made?
Again... not rhetorical. I just don't understand why this can't be answered properly.