Hi there
I've just applied the July 2017 update to Quark 2016.
I am in the process of simply putting a series of images onto a page (rather like a Contact Sheet) and want to use the "Place Name" script to add the file name underneath each image.
However, when I try this, selecting just one box – which contains a CMYK TIF image, and where neither the box nor the image has been rotated – I get a warning message pop up saying "Please select a single picture box containing an image [-2700]".
(The same thing happens when I try "Crop Marks and Name", but with a different warning about unrotated and unskewed boxes only.)

I believe it was working before the update, but I cannot honestly say it was so. It is a while since I have had to do this particular job that requires the names underneath pictures, and I have added a new machine to the office recently, so it is entirely possible that the last time I had to do this action I did it on the older machine which was still running Quark 8 in Mac OS Snow Leopard!

The recent 2016 update did solve another big problem I'd had with the Fill Characters in Tabs not lining up, so I'm very happy there, but it's a bit annoying, however, that the "Place Name" script isn't working though!

Well I have the July update installed too and the script "Place name" works for me. I checked the script and you only get the error when:
- no box is selected
- the selected box is not a picture box
- the selected box is empty

I've checked and triple checked that I'm doing everything the same way that I have done it hundreds (if not thousands) of times over the years, and I've just run the same process on another older Mac I've got here (running Quark 8.6), and everything works as it should on that!

Hi,
I'm having this same exact issue. How is it possible that this was addressed in a newer version of QXP, but not addressed for the version in which the problem originated? My company uses 2016. Are you saying that there will be no patch to correct the issue in a version build prior to QXP 2017? Where does that leave users of 2016?

I have this problem too...while I'm not holding out hope there will be a patch available for QXP 8.5.1, I'd like to confirm that it's fixed in a supported version of QXP so I can tell my client "that's a Quark problem that's addressed in QXP 2016"