6.0.4 Update - fixes nested ID file links info

Question

Hi all,
I got a message from an Adobe development manager letting me know of the 6.0.4 update. Specifically they have (almost) rectified the issue where you could not find out about graphic links inside of ID docs that were placed inside another ID document. The solution is that the placed ID document has an attribute of "links" (list/array) which can then be queried for the number of images and their information. I said "almost" because in a quick test, and verification with the Adobe rep, the Status of a graphic in the place ID file will not show as "normal" - it only shows its status as "out of date" or "link missing". My rep says this may need to wait for a later (6.0.5?) update.
There may be other fixes but this is one of two I really needed. I wanted to let everyone know, I know there are some other people waiting for this.
Here's some Applescript of how I queried some links in nested ID files:
--comment out as needed
tell application "Adobe InDesign CS4"
tell document 1
set subLinkTable to {}
set topLinkStatii to status of every link
if topLinkStatii contains link missing then --link missing is constant
return "missing top level links"
end if
repeat with L in every link
set linkCount to count of links of L
repeat with i from 1 to linkCount
copy ((status of link i of L) as string) & "-" & (name of link i of L) to end of subLinkTable
if status of link i of L is link missing then
return "missing 2nd level links"
end if
end repeat
end repeat
return "great success"
end tell
end tell
Here's a javascript (not written by me) that does some similar querying:
// Iterate through all the links of container document
linksLength = theDoc.links.length;
for (i=0 ; i< linksLength ; i++)
var curLink = theDoc.links[i];
alert("Top level link: " + curLink.name);
childLinksLength = curLink.links.length;
// Iterare through the child links of the placed INDD file
for (j=0; j < childLinksLength; j++)
alert("Child link: " + curLink.links[j].name);
Ciao,
Chris

Answer 1

I've never been working with placed ID documents so I can't comment that. My concern is ordinary images.
The thing that's breaking is the relinking of images in scripts, previously relying on an update and an assignment of the result of the update to a new variable, like this:
            lnk.relink(File(myImagesPath + '/' + newTrail));
            var modifiedLink = lnk.update();
            picture = modifiedLink.parent;
A try/catch, not to disturb customers still in CS3 or not yet updated should take care of the error now.
> I agree it causes us to change scripts; but that does happen from time to time.
Well, major versions of course, but I don't agree that it happens time to time. Absolutely not. This is the first time ever that an ordinary minor (free) update has caused any of our scripts to fail (and we have quite a lot of code, doing scripting since CS2). We might just be lucky but I'd say that Adobe has been very good at not disturbing code by updates, and my guess is that the effect of this update was taken into account when released.