I assume this does not affect 3.0.x. Feel free to explain why this is the case. Similar code likely exists in 3.0.x.
3.0 isn't affected because bug was caused by ticket I linked to. This patch reverts one line of code back to 3.0
Oh, sorry. Missed the ticket link.