Yes, I submitted a ticket (with a patch) when I found the solution a while ago: http://open.silverstripe.org/ticket/6382

I've submitted tickets before but unfortunately they always seem to be glossed over.

I've submitted tickets before but unfortunately they always seem to be glossed over.

Thanks for the ticket, usually we try and review the tickets every month or so but everyone gets super busy! If you submit patches to the new github account we try and merge those much quicker. Or you can do like simon_w and bug the core devs constantly on IRC till it gets merged which works somewhat better.

I assume this is not an issue in the new 3.0 as that behavior has been removed, so the patch will likely go into branches/post 2.4 which may or may not include an actual release.

Thanks for finding that, just ran into the same problem

Bug still exists.

You saved my day.
Wondering that this bug still exists.

Thanks Gene!

You're a legend!

I am also the beneficiary of this fix just today, many gratitude forthwith.

Hi,
I just want to report that the bug still exists in SS 3.0.3. It doesn't occur on local development computers or on the test environment (which lies in a subdomain of the production site) although all files, except _ss_environment.php and the .htaccess are rigorously identical.
This occurs after I have upgraded the website from 2.4.13 with the intention of catching up with the latest 3.1.x release.