On Thu, 23 Apr 2009, Benjamin Meyer wrote: > This was an unfortunate bug in 4.5 and has been fixed for 4.5.1 Ok -- then I won't have to report it. Fortunately, we've not deployed anything based on 4.5 yet. Boudewijn