I apologize that this hasn't been fixed already. The main problem I'm running into is it behaves differently depending on the server configuration. So, when I finally got it fixed on one it would break on another. So, for 6.0 I'm just totally reconstructing this entire area. No timeframe on a release date yet as it's still pretty early in development.
However, as Brett pointed out those threads will tell you how to remove the offending code so your users won't have this problem.