Logged In: YES
user_id=149827

I have to concur with this one; I noticed this on upgrading
from 2.0 to 2.1 as well, and would really like to see the
fix rolled back to the 2.x line, at least if 3.0 becoming
"final" is still a ways away.