Bug in book’s Update Numbering feature

Guru ,
Nov 28, 2019

Copy link to clipboard

Copied

Dear forum,

 

Every time we are completing the current issue of our magazine we suffer from — as I call it — ‘the update numbering in the book’ bug.

Usually, we have enough time to check and fix the problems, but with the latest issue — the day before yesterday — things went a wrong way: at the last moment, I had to move pages in the book and update numbering. As the result, three images changed their position a little and PDF files went to the printers with the glitches unnoticed. I saw it but was thinking it was OK because in previous issues this was done intentionally: pics were moved over the spine on the opposite page a little — deliberately. Other coworkers who were working on these docs didn’t notice the change: most probably, they were too tired by the end of the working day.

Luckily, nothing terrible has happened: the RIP guys removed unnecessary pieces on the fly from the imposed PDF. But I would like to sort it out: why this happens and how to avoid it in the future.

Here, on my site, I wrote a detailed description of what happens illustrated with screenshots and included files for testing in case someone is willing to play with it.

Thank you in advance!

 

Regards,
Kasyan

Adobe Community Professional
Correct answer by Laubender | Adobe Community Professional

This reply will get rather lengthy. It is showing jumps of objects that touch the jump zone. Touching the jump zone means the edge of an object lies within the zone. The edge of an object is defined by the visibilty of the object. Applied strokes to a rectangle will count! Nested objects like tables that run outside a text frame will not count. Anchored object that are touching the zone will not jump if the parent, the text frame with the anchor, is not touching the zone.

 

Let's illustrate this with a couple of screenshots.

 

A facing pages document where horizontal margins are set where the inner margins' values differ from the outer margins' values.

 

Master A: Inner margins are smaller than outer margins

191202-1-Master-A.PNG

 

Master B: Outer margins are smaller than inner margins ( that's the case with your document! )

191202-2-Master-A.PNG

 

Page 1 of the document with some rectangles on the page:

191202-3-Page-1.PNG

 

Pages 2-3 of the document:

On the left-hand page master A is applied, on the right-hand page master B is applied.

191202-4-Page-2-3.PNG

 

Pages 4-5 of the document:

In this case the margins from the master are overridden:

191202-5-Page-4-5.PNG

 

The next screenshots are showing the proposed jump zones ( yellow zone with guides ) where objects that touch the zone will probably jump:

 

191202-6-Page-1-Show-Jump-Zone.PNG

191202-7-Page-2-3-Show-Jump-Zone.PNG

191202-8-Page-4-5-Show-Jump-Zone.PNG

 

Now I will provoke the bug by doing two things:

1. Change the start page of the document from 1 to 2 so that left-hand pages become right-hand pages and right-hand pages become left-hand pages:

 

191202-9-Change-Numbering-Page-1-to-Page-2.PNG

191202-10-Change-Numbering-Page-1-to-Page-2.PNG

At this time some objects already jumped position. Some did not. When and why is dicussed at the end of this post.

 

2. Now I change the start number of the document back to 1.

This will bring us not back to the original position of all objects on the pages in the document:

 

191202-11-Change-Numbering-Page-2-to-Page-1.PNG

191202-12-Change-Numbering-Page-2-to-Page-1.PNG

 

The results discussed:

 

191202-13-Result-Page-1-Show-Jump-Zone-and-Predictions.PNG

191202-14-Result-Page-2-3-Show-Jump-Zone-and-Predictions.PNG

191202-15-Result-Page-4-5-Show-Jump-Zone-and-Predictions.PNG

 

All files and screenshots can be downloaded from my Dropbox account:

https://www.dropbox.com/s/duov096cu2q481l/Jump-Zones-Explained-Facing-Pages-Documents.zip?dl=0

 

Regards,
Uwe Laubender

( ACP )

 

EDITED: 3 February 2020

1. Did a bug report at Adobe InDesign Uservoice:

Objects on the page jump if a left-hand page becomes a right-hand page and vice versa

Uwe Laubender, December 02, 2019

https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/39165517-objects-on-the...

 

2. Kasyan discovered a workaround:

Lock all items in your document before adding pages, removing pages or moving pages around:

https://community.adobe.com/t5/indesign/bug-in-book-s-update-numbering-feature/m-p/10842790#M170295

 

Topics

Bug

Views

614

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Dec 02, 2019

Copy link to clipboard

Copied

Hi Kasyan,

did a bug report at Adobe InDesign Uservoice:

 

Objects on the page jump if a left-hand page becomes a right-hand page and vice versa

Uwe Laubender, December 02, 2019

https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/39165517-objects-on-the...

 

Please vote for fixing the bug. Thanks.

 

Uwe Laubender

( ACP )

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Guru ,
Jan 08, 2020

Copy link to clipboard

Copied

Hi Uwe,

 

I am terribly sorry for the late reply! For months, I had no access to the e-mail account I was registered here on the forum so, after the forum software update, I didn't get any notifications about new replies.

Only today, I restored access to it and found out your reply.

Thank you very much for your scrupulous research!

 

To solve the problem I wrote a script which I run from my 'batch processor' against the active book twice:

  • On the first run, it records object positions (geometric bounds) using insertLabel()
  • Then, after updating numbering, it reads them using extractLabel() comparing them with the current positions. If something is different, a warning is written into the log file created on the desktop.

 

I am going to share the script on my site.

I voted for your bug report.

Thank you a lot again!

 

Regards,
Kasyan

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Community Professional ,
Jan 08, 2020

Copy link to clipboard

Copied

Hi Kasyan,

thank you for voting to fix the bug!

 

However, I see that only 3 votes are done for now. So we will not see a fix in the near future, I think.

 

It took me a day or two to get all the details of the bug. Also did a script for internal use that is creating the yellow rectangles and some guides to visualize the "jump zones" of a facing-pages document.

 

Regards,
Uwe Laubender

( ACP )

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Guru ,
Jan 08, 2020

Copy link to clipboard

Copied

Uwe,

 

I posted a tweet asking my followers — who are mostly script developers/users — to vote. Also, I  just made a quick test: it doesn't happen with locked objects, but it does happen on locked layers. So, an alternative approach to solve this by the script would be the following:

  1. remember if the object is locked or not
  2. lock all objects
  3. update numbering in the book
  4. unlock the objects locked in step 2

 

— Kas

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Community Professional ,
Feb 03, 2020

Copy link to clipboard

Copied

Hi Kas,

thanks so much. What a cool discovery!

Locking all objects before adding or removing pages to a document is a fantastic workaround.

 

And it's so easy doing this by a ExtendScript (JavaScript):

// WARNING: Here we do not bother if some items are already locked before 
// and should stay locked after unlocking all again:
app.documents[0].pageItems.everyItem().locked = true;

 

The reverse, unlocking all items in the active document:

// WARNING: Here we do not bother if some items were already locked before 
// and should stay locked after unlocking all again:
app.documents[0].pageItems.everyItem().locked = false;

 

Regards,
Uwe Laubender

( ACP )

 

PS: Totally missed your answer here. Just discovered it right now.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Guru ,
Mar 23, 2020

Copy link to clipboard

Copied

Finally, being on lockdown at home because of coronavirus, I found time to post my solution to the problem here on my site.

— Kas

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...