3 results found

1. CC2018 IDML files not compatible with CS6

   Clients who have CS6 can't open any IDML files I create/export in CC2018. They receive an error message saying the format is unsupported or a plug-in is missing. IDML files created/exported from an earlier version of CC (2017) work fine.

   8 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   24 comments  ·  IDML Export  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Need More Info  ·  amaarora responded

   Please confirm in comments if the issue has been resolved for you with the latest release of InDesign?

   Thanks

2. IDML file exported from InDesign CC 2025 moves objects randomly

   A file exported from InDesign CC 2025 and imported to CC 2024 is corrupted. Some objects (page numbers on parent pages) are randomly relocated. This is pathetic.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  IDML Export  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Need More Info  ·  Adminansjain (Admin, Adobe InDesign) responded

   We would require more information on this.

   Is this happening with all files or some specific files?

   Are only page numbers getting relocated or other elements as well?

   Is this happening with only parent page objects or with objects on normal pages as well?

   An screenshot of indd and idml would also help.

   Please share your OS version.

3. FlexObject Items Invisible in Preview Mode (possible culprit: IDML Roundtrip)

   Bug Report: FlexObject Items Invisible in Preview Mode (probably bugged after IDML Roundtrip)

   Product: Adobe InDesign 2025 (v20.x)
   Feature: Flex Layout / FlexObject (new in InDesign 2025)
   Severity: Major — affects preview mode of the new flex objects
   Date: February 20, 2026

   ---

   Summary

   FlexObject containers and their child items become invisible in Preview screen mode (but remain visible in Normal mode and Overprint Preview) after a document has undergone an IDML export/import roundtrip. The issue also propagates to any copies made from affected objects — even copies placed outside the FlexObject container.

   The root cause was identified as a missing registration of these page items in the internal spread-level page item collection. Items exist in page.allPageItems but are absent from spread.allPageItems, which Preview mode apparently relies on for rendering.

   ---

   Suspected Trigger

   The affected document had previously undergone an IDML roundtrip (export as .idml, then reopen). The document contains FlexObject containers (the new Flex Layout feature introduced in InDesign 2025). The hypothesis is that the IDML reconstruction does not fully re-register FlexObject items in the spread's internal page item hierarchy. Since FlexObjects are a very new feature, it is plausible that the IDML serialization/deserialization path does not yet handle them with full fidelity.

   ---

   Steps to Reproduce

   1. Create a new InDesign document.
   2. Add a Flex Layout container (FlexObject) with several child items (e.g., image frames with the object style "Album in REZI KURZ").
   3. Save and export the document as IDML (.idml).
   4. Close the document and reopen the exported .idml file.
   5. Save as .indd.
   6. Switch from Normal screen mode to Preview screen mode (View → Screen Mode → Preview, or press W).

   Expected: All items remain visible.
   Actual: The FlexObject and all its children disappear entirely.

   Additional observation: Copying an affected item out of the FlexObject and pasting it elsewhere on the page does not fix the issue — the copy inherits the "unregistered" state. Even extracting just the placed image (graphic content) from a frame and pasting it into the document independently produces a new frame that is also invisible in Preview mode.

   ---

   Systematic Exclusion of Common Causes

   The following properties were checked programmatically (via ExtendScript) on all affected objects and confirmed to be not the cause:

   | Property / Setting | Value Found | Would Cause Invisibility? |
   |---|---|---|
   | item.nonprinting | false on all items | No — correctly set |
   | item.visible | true on all items | No — correctly set |
   | item.itemLayer.visible | true | No — layer is visible |
   | item.itemLayer.printable | true | No — layer is set to print |
   | item.transparencySettings.blendingSettings.opacity | 100 on all items | No — fully opaque |
   | Object Style .nonprinting | false on all relevant styles | No — styles do not suppress printing |
   | item.fillColor | "None" (frames are graphic frames) | Not relevant |
   | Geometric bounds vs. page bounds | All items within page boundaries | No — not on pasteboard |
   | Link status of placed images | NORMAL on all images | No — links are intact |
   | Content type of frames | GRAPHIC_TYPE | Correct |

   Key distinction: Items are visible in Overprint Preview (View → Overprint Preview) but invisible in Preview screen mode (the mode that hides guides and pasteboard). This rules out any rendering/transparency issue and points to a metadata/registration problem specific to Preview mode's rendering path.

   ---

   Diagnostic Finding: Missing Spread Registration

   Using ExtendScript, the following discrepancy was discovered:

   // On an affected document:
   spread.allPageItems.length;  // → 0  (WRONG — should contain items)
   page.allPageItems.length;    // → 21 (correct — all items present)
   
   // After creating a NEW rectangle via script on the same page:
   spread.allPageItems.length;  // → 1  (new item registers correctly)
   page.allPageItems.length;    // → 22
   

   All 21 page items (1 FlexObject + 9 Rectangles inside it + 10 Images + 2 loose Rectangle copies) were found via page.allPageItems but none appeared in spread.allPageItems.

   A freshly created Rectangle (via page.rectangles.add()) registered in spread.allPageItems immediately, confirming that the spread collection mechanism itself works — it is specifically the IDML-reconstructed FlexObject items that fail to register.

   This strongly suggests that Preview mode uses the spread.allPageItems collection (or an equivalent internal list) to determine which items to render, while Normal mode and Overprint Preview use a different rendering path that includes all items regardless of spread registration.

   ---

   Workaround

   A manual workaround was discovered and automated via ExtendScript:

   1. Cut the affected top-level item.
   2. Create a temporary Rectangle on the page.
   3. Paste Into the temporary Rectangle (Edit → Paste Into).
   4. Select the pasted item inside the container and Cut it back out.
   5. Remove the temporary Rectangle.
   6. Paste the item back onto the page.
   7. Restore the original geometric bounds.

   This paste-into/cut-out cycle forces InDesign to re-register the item in the spread's internal collection. After this procedure, the item (including FlexObjects with all their children) appears correctly in Preview mode.

   An automated repair script was developed that:
   - Detects all top-level items present in page.allPageItems but absent from spread.allPageItems
   - Applies the paste-into workaround to each affected item
   - Verifies successful re-registration afterward
   - Groups the entire operation under a single Undo step

   ---

   Impact

   • Print production: Items invisible in Preview mode may also be missing from PDF export or print output (not yet verified but likely given the correlation between Preview mode and print rendering).
   • User confusion: Designers may not notice the issue until final proofing, as items appear normal in the default working view.
   • Propagation: The issue spreads to any copies made from affected objects, making it difficult to isolate without programmatic diagnosis.
   • Magazine production affected: The issue was discovered during production of a print magazine (folker magazine, issue 25-4), where FlexObject layouts are used for album review image grids.

   ---

   Requested Fix

   1. Ensure that IDML import fully registers all reconstructed page items — including FlexObject containers and their children — in the spread's internal page item collection.
   2. Consider adding a document integrity check that detects and repairs unregistered page items on document open or IDML import.
   3. Verify that other new object types introduced alongside Flex Layout are also correctly handled during IDML roundtrips.

   ---

   Environment

   • InDesign version: 2025 (v20.x, latest available as of February 2026)
   • OS: Windows
   • Flex Layout feature: Enabled, actively used
   • Document history: Created in InDesign → exported as IDML → reopened → saved as .indd
   • Diagnosis performed with: ExtendScript via JSX execution (InDesign DOM scripting)

   Bug Report: FlexObject Items Invisible in Preview Mode (probably bugged after IDML Roundtrip)

   Product: Adobe InDesign 2025 (v20.x)
   Feature: Flex Layout / FlexObject (new in InDesign 2025)
   Severity: Major — affects preview mode of the new flex objects
   Date: February 20, 2026

   ---

   Summary

   FlexObject containers and their child items become invisible in Preview screen mode (but remain visible in Normal mode and Overprint Preview) after a document has undergone an IDML export/import roundtrip. The issue also propagates to any copies made from affected objects — even copies placed outside the FlexObject container.

   The root cause was identified as a missing… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  IDML Export  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Need More Info  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   Please send the following information to sharewithID@adobe.com :

   • Reproducible Steps – What were you doing when the issue occurred?
   • Video recording of the issue
   • Is(Are) the issue related to a specific document(s)/asset(s)? If yes, could you provide us with the document(s)/asset(s)? Please package the entire document (To package the document, choose File → Package…)

   Also provide answers to follow queries

   1. During IDML workflow , are you opening the indd containing flex in version 20.0-20.5 or you are opening the IDML in version 21.0 onwards?

   2. What type of objects / images you are using?

   3. are you grouping the items or creating nested flex frames?

   4. You are only using object style to flex items or through any other menu?