I just submitted a xfprint bug. Since I pulled cvs, and it being the same day as the 4.2.0 release, I figured I'd drop a note here so that there isn't any confusion as to this being a 4.2.0 bug - I didn't get this behaviour in the 20 minutes I had the xfprint module from 4.2.0. ;-) -- -Erik