> The release notes for 3.0.1 should tell you that this was fixed Thanks Jesse. I wasn't sure which item in the changelog would apply to the problem.