Thanks for the report. The fix for this will be in 2.6b2, and the issue isn't in the current stable release.
Thanks for the report. The fix for this will be in 2.6b2, and the issue isn't in the current stable release.