Maybe somebody from DNN could comment to give us some idea that this is the correct way to fix this problem or whether we should wait for an official fix. Don't want to find this change breaks other things and no comment doesn't instil great confidence.
Does make you wonder how on earth an, allegedly reported, bug such as this could not be fixed before release to the public and even if it wasn't previously reported how this just hasn't been picked up in "testing"!
It's one of the most important aspects of the whole website! Unbelievable!
Looks like a case of you get what you pay for again. Upgrade to Pro and get something that works.

Actually I've just made the change in web.config and it makes no difference to me so I'll continue to wait until DNN do something about this.