$ 0 0 Thanks for the detail. With it I was able to find the bug. It will be fixed in the next release (2.5.19), due in the next week or so.