Skip to main content
hamburger menu Created with Sketch.
PHP2Shell - PHP Vulnerability Announcement

Search the Knowledge Base

Troubleshooting: Adobe® InDesign® files

  • Updated

Question:

Troubleshooting: Adobe® InDesign® files

Answer:

InDesign® Packages (ZIP files) are output from Adobe® InDesign® and contain the entire project, including graphics and fonts.

Due to the fact that Vault automatically generates viewable renditions based on InDesign® files, graphics, and custom fonts within the package, it is imperative that users ensure they include all required data in their InDesign® packages.
If users do not include all data, they may notice font substitutions or missing images in Vault. 

Below there's a list of issues encountered when uploading InDesign® files into Vault:

 

Missing Fonts:

When fonts are missing in InDesign® packages, the document does not show the right font in Vault and users are notified that there are missing fonts via email.

Vault does not use any additional fonts outside of what is used by default with Adobe InDesign.

  1. Check the folder Document fonts in the InDesign® package, and see if 
    a) there are any font files that lack size, ratio, or format. 
    missingfont2.png
    b) the font files are not password protected.
    c) the font used is not Type 1 for Mac (or DFONT) 

  2. Substitute the corrupted font file with OTF or TTF font types., and re-upload the InDesign® Package (ZIP file) to Vault. 

     

Modified Links:

When Adobe® InDesign® detects outdated graphics links, users receive a warning message listing the Modified Links which is meant to notify users that a newer version of the images in the file may be available.

Users can upload a new version or leave the Viewable Rendition as is.
 

No Viewable Rendition:

1- Vault is unable to Render the file

Vault only renders InDesign® package files that contain a single .indd file and a single .idml file.  

Users must revise the package method and ensure all needed files are included (see Related Documentation below).
If an additional .idml is needed (e.g. for local markets to be able to amend tables), it should be added into a separate InDesign® Package and then loaded into Vault as separate documents.

2- CLM integration

Users upload a ZIP file and Vault generates a Viewable Rendition when the Vault uses CLM Integration or packaged in Adobe InDesign. 

  • When the Vault has CLM integration the user must check the following:
  1. The document Type is Multichannel Slide.
  2. The ZIP file contains a thumb.png. More on Packaging Custom CLM Content.  
     
  • When the Vault does not have a CLM integration but an HTML file needs to be uploaded, please consider the following options:
  1. Upload a PDF file as the Source Document and use the Attachments section to upload other files.
  2. To upload an HTML file as the Source Document, the Content Creator must ensure all stylings are referenced inside the HTML so that Vault can render a Viewable Rendition. Failing to edit the file as mentioned will return a blank Viewable Rendition in Vault.

 

Viewable Rendition with gray rectangles

When the Viewable Rendition does not show the file correctly (e.g. with gray rectangles), it might be because when packaging the files, InDesign® doesn’t automatically link to the files inside the Links folder. 

The user must link them manually.
 

Related Documentation:

Package the InDesign® Content

About Adobe® InDesign® Package Rendering  

 

Send us your feedback: We are always looking for feedback to help improve our Knowledge Base! Please let us know if this article is helpful or provide feedback on how we can improve your experience by clicking here.

Powered by Zendesk