Hi,

I have this issue: http://support.dotnetnuke.com/project...

It is stated that it is fixed in the DNN CE 7.0.6.77. I've updated my dnn version to the latest version but this is only the DNN 7.0.5. How can I fix this in the 7.0.5 version?

Is there no temporary fix? 

The fix has been made and will be in 7.0.6 - you can see this as it has been marked as closed , so it's gone through the whole verification, triage, checked-in, reviewed and final closed process.

Michael, I understand your frustration with the "moving" versions setup, I don't like it either and have sent a number of mails about it. The thinking behind it is that the triage team meet and select lots of issues for the maintenance team to work on (they always assign more than can probably be fixed, as if the list was too small, the dev's could end up having to wait for a triage team member to become available to assign more). When a release comes out, the unworked items are moved forward to the next release where they'll again be considered -however this has the drawback in that if something is "low" priority/severity, it means it's unlikely to get fixed as there are more important items on the list - whilst that's fine, seeing an issue you're tracking moving from version to version without action is very annoying (more so I think that just seeing the issue sit there and never get assigned to a release). I'll bring this up again with QA and see if there is anyway they can tweak their process to make it less annoying.