Thanks for the follow-up. I'm reopening this bug and marking it as 'critical' since it appears to be a regression in a published update.
I believe the developer who prepared the update is away this week, but we'll see what we can do about getting this resolved - if nothing else, by reverting the change in this update.
Sven,
Thanks for the follow-up. I'm reopening this bug and marking it as 'critical' since it appears to be a regression in a published update.
I believe the developer who prepared the update is away this week, but we'll see what we can do about getting this resolved - if nothing else, by reverting the change in this update.