Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

BUG: ID 18.3 repeatably crashes on cross-reference to an H1 in another file

Engaged ,
Jun 02, 2023 Jun 02, 2023

Hi. Using ID 18.3 (recently updated) with Win 11 (also updated) 64 Gb memory.

This appears to be a bug. Repeatable even after a full cold re-boot. On the last try, I did not "recover" the files (attempting to leave whatever corruption is clinging to them behind). Didn't work. This has occurred as described 6 times. I've sent the report per the crash dialog each time. There have been other crashes of 18.3 (also reported via the crash dialog). This is the worst because I can't seem to get around it.

 

I have a multi-chapter book. I have about 150 hours into the book (that is, the files have collectively been in use for that elapsed period of time, opening, writing, pasting, cross-referencing, saving, closing).

I have been trying to create a cross-reference (paragraph text and page number) from a position in one file to a Head1 in another file of the same book. All files in the book are open in ID and apparently error-free according to Preflight.

  1. I initiate the xref in the xref panel. The xref db displays.
  2. I choose paragraph text and page number.
  3. I choose the other file from the pull down.
  4. I scroll to and click the Head1 style.
  5. Crash.

 

I have tried doing the cross-ref from another place is the referencing file. No dice.

I have done a cold reboot. No dice.

very frustrating.

I have not yet tried to do a different type of Xref or an xref to a different file (because, well, what caused the crash is what I'm actually trying to do).

 

-j

TOPICS
Bug , Performance
408
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Jun 02, 2023 Jun 02, 2023

Update:

The problem appears to be centered on one file. I have successfully done cross-refs to other files without a problem.

On the target file, I saved as IDML, opened the IDML file, put that into the book and attempted to do a cross reference to it.

Crash.

Any suggestions on how to rectify this? I supposed I could cut and paste the text (and illos) of the entire chapter into a new file...

 

-j

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jun 02, 2023 Jun 02, 2023

Did you do IDML on both files, file you're creating it in - and the file you're targeting?

 

If the above fails - then on both documents - here's something to try

  1. Create a new file with the same margins and the same size etc.
  2. On one file that isn't working open it - and move your pages to the new document

Repeat this for the 2nd file (with a new document with the same margins and size etc.)

 

https://www.youtube.com/watch?v=_iW7ZYx7iv0&ab_channel=CreativePro

 

 

In this video, Mike Rankin demonstrates how to move pages from one InDesign file to another. He looks at how master pages are handled during that process and he also shows how to simply move master pages between documents. New videos every week! Expand your skills and stay current with ...
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Jun 03, 2023 Jun 03, 2023

Excellent suggestions (including your links). Thanks.

I did create IDML for both documents and, after re-adding the documents to the book, I attempted to do the Xref once more. This crashed ID yet again (I uploaded the report via the dialog. I think this is time 8 or 9.)

I suspect that something is... um... altered beyond the ability of re-loading from IDML to rescue it. It might be a problem with the book file or some quirkiness I have triggered in 18.3. (I'm thinking it's some odd horizon condition, since it crashes with the same kind of Xref between the same files even after multiple re-boots and IDML saves & reloads).

While Move Pages as explained in the video would be a huge time saver, I suspect that it will also "move" the problem -- whatever that problem is -- since I don't know all that Move Pages moves. I will go with the nuclear option of cutting/pasting into a fresh document that has all styles/running heads/other formatting already in place  (I use a template for each new files). Then comes the fun of re-hooking up all the between-file Xrefs that bear on both files! I will report back. 

Thanks for your tips. In happier times, Move Pages would be a kick. This one wretched Xref has brought production to a halt.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Jun 03, 2023 Jun 03, 2023

Something is seriously wrong.

  1. I created two new files from template - one for the cross-referencing document and one for the target of the cross-reference. I named the new files.
  2. I copy-and-pasted the text from the old documents to their respective new documents, and saved them both under their new names. In this process I sacrificed any existing outside-the-file Xrefs in both files, which I will have to restore.
  3. I created a new book file (just in case it was the book file at fault), and added all chapter files to that new book in their proper order.
  4. I opened all files from the new book (and then saved them with shift-control-alt-S.
  5. I went to the position in the referencing file where I wanted to make the cross-reference.
  6. ...and from the Xref db I selected paragraph text & page number, pulled down the target file name, scrolled to the H1 style, selected it... and CRASH.

At this point I believe I am past easy work-arounds. Production must continue. I will avoid this Xref and see what happens with the NEXT Xref. If anyone has any suggestions about what to try here, I am all ears, as Willie the Shake said.

 

Thanks.

 

-j

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jun 03, 2023 Jun 03, 2023
LATEST

You completely ignored my advice and did it your own way.

 

Will you please try my method?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines