134 results found

1. InDesign hangs when placing text

   This bug has been around for a long time. It would be nice to have it fixed.

   Steps to Reproduce:
   1. Install the Adobe font family, Source Han Sans TW, on your computer.
   2. Create a folder: c:\Temp and give everyone full permissions.
   3. Download Script1.jsx and place it in "C:\Users<User>\AppData\Roaming\Adobe\InDesign\Version 19.0-J\en_US\Scripts\Scripts Panel"
   4. Start ID 2024 running in the CJK region.
   5. Open the scripts panel and run Script1.jsx
   6. Wait as long as you would like.

   Actual Result: Usually InDesign hangs (i.e. freezes). Sometimes InDesign crashes and submits and crash report to Adobe.

   Expected Result: That the script would place text and then terminate normally.

   Wordaround: Use InDesign 2024 Debug. Unfortunately, InDesign 2024 Debug gives many failed assertion messages and they quickly become annoying. It's interesting that InDesign 2024 Debug places the text and the script terminates normally, except, of course, for all the failed assertions.

   Here's a video, for what it's worth:

   https://www.loom.com/share/5536719355a0432fb0069513ccb1d0df?sid=0f285aff-7589-4860-bc62-736f7452f3f8

   I had to rename Script1.jsx to Script1.txt in order to upload it. This is a forum for scripting problems which doesn't allow people to upload scripts!!

   This bug has been around for a long time. It would be nice to have it fixed.

   Steps to Reproduce:
   1. Install the Adobe font family, Source Han Sans TW, on your computer.
   2. Create a folder: c:\Temp and give everyone full permissions.
   3. Download Script1.jsx and place it in "C:\Users<User>\AppData\Roaming\Adobe\InDesign\Version 19.0-J\en_US\Scripts\Scripts Panel"
   4. Start ID 2024 running in the CJK region.
   5. Open the scripts panel and run Script1.jsx
   6. Wait as long as you would like.

   Actual Result: Usually InDesign hangs (i.e. freezes). Sometimes InDesign crashes and submits and crash report to Adobe.

   Expected Result: That the script… more

   5 votes

   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

   6 comments  ·  Java Script  ·  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

2. ScriptUI: Opening Dialog while dialog is open breaks InDesign

   I posted that bug in gerneral Bugs section. Belongs to Scripting though:
   https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/37298593-scriptui-opening-dialog-while-dialog-is-open-brea

   5 votes

   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  ·  Java Script  ·  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
   FIXED  ·  amaarora responded

   Hello All,
   Thank you for reporting the issue to us.
   We have fixed the issue in the 14.0.3 version of InDesign

   Please upgrade your InDesign application to the latest version to try out the fix. The latest version of InDesign is 15.0

   If you face any problems with the new update, do let us know in the comments.

3. INumberConverter being ignore when exporting PDF

   I am using CC 2017, but it has been an issue for multiple versions.

   I have a custom plugin that implements INumberConverter on kPageNumberingStylesService Boss for a custom numbering format. This works beautifully until I try to export to PDF. If I print to PDF Distiller it works fine, but when I export to PDF it exports with default numbering style.

   This is similar to an old stubborn bug, when exporting book to PDF would not do the numbering correctly. I don't know that it is related, but they both seem to say that the numbering on export is decoupled from the way it is calculated for regular viewing of the PDF.

   I am using CC 2017, but it has been an issue for multiple versions.

   I have a custom plugin that implements INumberConverter on kPageNumberingStylesService Boss for a custom numbering format. This works beautifully until I try to export to PDF. If I print to PDF Distiller it works fine, but when I export to PDF it exports with default numbering style.

   This is similar to an old stubborn bug, when exporting book to PDF would not do the numbering correctly. I don't know that it is related, but they both seem to say that the numbering on export is decoupled… more

   5 votes

   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  ·  C++ SDK  ·  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

4. Epub toc links are not created when a document's toc is created by a script

   To create a (navigable) Epub TOC you check the 'Make text anchor in source paragraph' checkbox. The links are created correctly when the TOC is created manually, but when the TOC is created by a script, the links are not created.

   To confirm, please open the attached document and run this very simple script:

   app.documents[0].createTOC (app.documents[0].tocStyles.item('Epub'), true);

   The used TOC style ('Epub') has the 'Make text anchor in source paragraph' box checked.

   Then export the document to reflowable Epub. In the Export dialog's General tab, select 'Multilevel (TOC Style)' at 'Navigation TOC' and at 'TOC Style, select the Epub style. Click OK.

   Expected result: An error-free export and a valid Epub file.

   Actual result: An error message saying "Found TOC hyperlinks which lack target text anchor information. Please update TOC with 'Make text anchor in source paragraph' option turned on."

   To verify that this is a scripting problem, re-open the document and export it manually. The error does not occur, and the epub has a valid html TOC.

   To create a (navigable) Epub TOC you check the 'Make text anchor in source paragraph' checkbox. The links are created correctly when the TOC is created manually, but when the TOC is created by a script, the links are not created.

   To confirm, please open the attached document and run this very simple script:

   app.documents[0].createTOC (app.documents[0].tocStyles.item('Epub'), true);

   The used TOC style ('Epub') has the 'Make text anchor in source paragraph' box checked.

   Then export the document to reflowable Epub. In the Export dialog's General tab, select 'Multilevel (TOC Style)' at 'Navigation TOC' and at 'TOC Style, select the Epub style.… more

   5 votes

   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  ·  Java Script  ·  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

5. UXP Multipanel-Plugin Flyout Bug

   Product: Adobe InDesign
   Version: 20.5
   Forum post: https://forums.creativeclouddeveloper.com/t/flyout-menu-with-mutli-panel-plugins/11436/2

   When creating a multi-panel UXP plugin and attaching a flyout menu to one of the panels, the flyout menuappears on a different panel than the one to which it is defined.

   Steps to Reproduce
   1. Create a UXP plugin for InDesign with multiple panels.
   2. In the plugin’s entrypoints.setup, define a flyout menu for one of the panels.
   3. Load/activate the plugin so all panels are present.
   4. Look to which panel the flyout-menu gets attached. It's probably not the one defined in the entrypoints.setup.

   Expected Result
   The flyout menu appears at the panel where it was defined (i.e. the menu is bound / attached to the correct panel).

   Actual Result
   The flyout menu instead attaches to a seemingly random panel, not necessarily the one in which it was defined. It may be possible that it's randomly placed at the correct panel, though in my cases it was always wrong. It's not always the last panel defined (in one case it was the third panel with a total of four, though the menu was attached to the first panel in the entrypoints.setup.

   Additional Notes
   • The issue appears specific to InDesign. According to the forum post, the same plugin works correctly in Photoshop: each panel gets its proper flyout menu. 
   • Bug was affirmed by another user in the forum post

   I was going to upload a test-plugin demonstrating the issue. But weirdly I can neither upload a zip file nor a ccx file, which is weird for the official place to report bugs. You can get the test file from the forum post though.

   Product: Adobe InDesign
   Version: 20.5
   Forum post: https://forums.creativeclouddeveloper.com/t/flyout-menu-with-mutli-panel-plugins/11436/2

   When creating a multi-panel UXP plugin and attaching a flyout menu to one of the panels, the flyout menuappears on a different panel than the one to which it is defined.

   Steps to Reproduce
   1. Create a UXP plugin for InDesign with multiple panels.
   2. In the plugin’s entrypoints.setup, define a flyout menu for one of the panels.
   3. Load/activate the plugin so all panels are present.
   4. Look to which panel the flyout-menu gets attached. It's probably not the one defined in the entrypoints.setup.

   Expected Result
   The flyout menu appears at… more

   4 votes

   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  ·  UXP plugins  ·  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

6. macOS error -2740: Enable access to helpful InDesign scripts (Accessibility & more)

   Since macOS Sequoia, AppleScript calls in JSX scripts – especially those using curl or doShellScript – are blocked by the system. This prevents tools like Octopus from running (error -2740), even when installed correctly and granted full accessibility permissions.

   This is especially critical in light of the upcoming European Accessibility Act: Octopus greatly supports the creation of accessible PDF/UA documents by automating ALT text management, export tags, and other metadata – all of which are still very manual in native InDesign.

   Beyond accessibility, Octopus also offers powerful features for GREP automation, quality control, and editorial workflows.

   Suggestion: Adobe should either provide a system-friendly way for such scripts to work – or even better: integrate key Octopus functionalities directly into InDesign, e.g. as an official accessibility panel or workflow tool.

   Since macOS Sequoia, AppleScript calls in JSX scripts – especially those using curl or doShellScript – are blocked by the system. This prevents tools like Octopus from running (error -2740), even when installed correctly and granted full accessibility permissions.

   This is especially critical in light of the upcoming European Accessibility Act: Octopus greatly supports the creation of accessible PDF/UA documents by automating ALT text management, export tags, and other metadata – all of which are still very manual in native InDesign.

   Beyond accessibility, Octopus also offers powerful features for GREP automation, quality control, and editorial workflows.

   Suggestion: Adobe should either… more

   4 votes

   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

   0 comments  ·  Java Script  ·  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

7. [ExtendScript/UXP] Position layoutWindow viewport

   I would like to be able to specify a layoutWIndow viewport's center.

   In Illustrator, we can position the center of the window's (a View, in Illustrator) viewport in document coordinates, so we can, for example, center a page item in the window.

   I would much appreciate this addition to Indesign scripting.

   4 votes

   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  ·  Java Script  ·  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

8. Some plug-ins compiled for InDesign 2021 16.0 crash InDesign 2021 16.1 - the 16.0 and 16.1 SDK are incompatible

   When a plug-in relies on the embedded Boost framework to support regular expressions, it can cause a crash because of unresolved dependencies.

   The issue is that the 16.0 SDK uses Boost 1.65 and the 16.1 SDK uses Boost 1.72

   Plug-ins compiled against the 16.0 SDK that use regular expressions will try to access an entry point __ZN5boost16re_detail_10650018get_default_syntaxEh (unmangled: boost::re_detail_106500) when handling regular expressions.

   The problem is that this entrypoint's name is dependent on the Boost version (1.65).

   This entry point is provided by the (on Mac) embedded framework

   /Applications/Adobe InDesign 2021.app/Contents/Frameworks/boost_regex.framework/Versions/A/boost_regex

   When a plug-in compiled against SDK 16.0 is used with InDesign 2021 16.1, this entry point does not exist any more.

   Instead, the equivalent entry point is now boost::re_detail_107200 and boost::re_detail_106500 does not exist in InDesign 2021 16.1

   That causes the plug-in to crash InDesign.

   As a result, plug-ins that use boost_regex that are compiled for 2021 16.0 are incompatible with 2021 16.1 and vice-versa.

   When a plug-in relies on the embedded Boost framework to support regular expressions, it can cause a crash because of unresolved dependencies.

   The issue is that the 16.0 SDK uses Boost 1.65 and the 16.1 SDK uses Boost 1.72

   Plug-ins compiled against the 16.0 SDK that use regular expressions will try to access an entry point __ZN5boost16re_detail_10650018get_default_syntaxEh (unmangled: boost::re_detail_106500) when handling regular expressions.

   The problem is that this entrypoint's name is dependent on the Boost version (1.65).

   This entry point is provided by the (on Mac) embedded framework

   /Applications/Adobe InDesign 2021.app/Contents/Frameworks/boost_regex.framework/Versions/A/boost_regex

   When a plug-in compiled against SDK 16.0 is… more

   4 votes

   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

   0 comments  ·  C++ SDK  ·  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

9. Can't retrieve XMP-metadata from Cloud-stored files

   Hello Adobe and hello Community,

   I'm having a problem with a Javascript I wrote to retrieve XMP metadata from linked files, that are stored in a Creative Cloud Library (Bought from Adobe Stock -> stored in a Library, because i was unable to download the files).

   Ultimately, the script retrieves the Creditline of all the linked graphics in an InDesign-file / InDesign-files in a folder by bulk processing.

   I have to accesse the XMP to retrieve the correct copyrightinfo.
   @Adobe: On Adobe Stock you guys put the information to give credit to the creator in the XMP field "Creditline" (creator - stock.adobe.com). In InDesign you cannot retrieve that field by out-of-the-box extendscript methods like: Link.linkXmp.copyrightNotice
   Please add the method to retrieve the correct field in extendscript!

   The Script I'm running works perfectly fine for links, that are located on my local drive or server but it doesn't work for Assets that are linked in the document from Adobe Creative Cloud.

   My Script looks something like this:

      if ( !ExternalObject.AdobeXMPScript ){
       try{ExternalObject.AdobeXMPScript = new ExternalObject('lib:AdobeXMPScript');}
       catch (e){alert('Unable to load the AdobeXMPScript library!');}
   }
   
   
   var myFile = File(app.selection[0].graphics[0].itemLink.filePath);
   alert(myFile.fsName);
   xmpFile = new XMPFile(myFile.fsName, XMPConst.UNKNOWN, XMPConst.OPEN_FOR_READ);
   var myXmp = xmpFile.getXMP();
   xmpFile.closeFile(XMPConst.CLOSE_UPDATE_SAFELY);
   
   
   var myPsCredit = myXmp.getProperty(XMPConst.NS_PHOTOSHOP,"Credit");
   var myDcCredit = myXmp.getProperty(XMPConst.NS_DC,'rights[1]');
   if (myPsCredit) {
       var output = myPsCredit;
   } else{
       var output = myDcCredit;
   }
   
      alert(output);
   
   
      if( ExternalObject.AdobeXMPScript ){
       try{ExternalObject.AdobeXMPScript.unload(); ExternalObject.AdobeXMPScript = undefined;}
       catch (e){alert('Unable to unload the AdobeXMPScript library!');}
   }
   

   In this line I'm getting an error:

   errornumber: 1000

   errorstring: XMP Exception: OpenFile returned false

      xmpFile = new XMPFile(myFile.fsName, XMPConst.UNKNOWN, XMPConst.OPEN_FOR_READ);
   

   I'm reading from this, that the XMP of that file which is located in the Creative Cloud, cannot be opened.

   Is there a way for still retrieving the XMP-data from those files?

   Unless there is a way to bulk-download all the Assets from the cloud and automatically re-link them in all the files i want to check (which Adobe also does not support. You can only download one file at a time from the Creative Cloud App. Great job, well done, users are sooooo happy about that), I have to access the XMP in the Cloud-stored files.

   If there is no other way to access the needed XMP-data, please implement a fix to do so.

   Also posted here, but so far I didn't receive an answer: https://community.adobe.com/t5/indesign/retrieving-xmp-data-from-cloud-asset-throws-error/m-p/11522046?page=1

   Hello Adobe and hello Community,

   I'm having a problem with a Javascript I wrote to retrieve XMP metadata from linked files, that are stored in a Creative Cloud Library (Bought from Adobe Stock -> stored in a Library, because i was unable to download the files).

   Ultimately, the script retrieves the Creditline of all the linked graphics in an InDesign-file / InDesign-files in a folder by bulk processing.

   I have to accesse the XMP to retrieve the correct copyrightinfo.
   @Adobe: On Adobe Stock you guys put the information to give credit to the creator in the XMP field "Creditline" (creator… more

   4 votes

   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  ·  Java Script  ·  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

10. Collapse Treeview not working

    On Indesign CC (Win or Mac) :
    Treeview with multi levels can be expand with recursive function;
    But collapse operation seems to be not working with similar function;

    On Indesign CS6 (Win or Mac) :
    Treeview with multi levels can be expand.
    Collapse operation runs halfway. But items (not node) on first level are indented too much.

    Run Script treeviewexpandcollapse.jsx to test it

    • 

    4 votes

    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  ·  Java Script  ·  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

11. Bug in IXMLOutStream.h header file

    InDesign2020SDK/source/public/interfaces/xmedia/IXMLOutStream.h:499

    void WriteName(const UTF16TextChar* name, bool16 newLine = kFalse)
                  { this->WriteName(name, newLine); }
    

    This function calls itself. It leads to a stack overflow on Windows but the code analyzer in Xcode catches it and reports an error during compilation. It can be changed to:

    void WriteName(const UTF16TextChar* name, bool16 newLine = kFalse)
                  { this->WriteName(WideString(name), newLine); }
    

    and it will work (it calls the previous function in the file instead).

    4 votes

    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  ·  C++ SDK  ·  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
    FIXED  ·  AdminRavi Kiran (Admin, Adobe InDesign) responded

    The fix for this issue is now available in the latest versions of InDesign – version 16.0 and above.
    Please update to this version to get the fix.

    —
    Adobe InDesign team

12. InDesign crashes when converting a table

    In the attached document, when I (try to) convert the tabbed text to a table, InDesign crashes.

    Steps to reproduce:

    1. Open the document from the attached zip file.
    2. Select the text frame.
    3. Run the following one-line script:

    app.selection[0].parentStory.texts[0].convertToTable ('\t', '\r');

    Expected result: a table.
    Actual result: InDesign crashes.

    Note: the crash does not happen when the tabbed text is converted manually:

    1. Select all the text
    2. Table > Convert Text to Table
    4 votes

    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

    4 comments  ·  Java Script  ·  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
    FIXED  ·  Abhinav Kaushik responded

    Hello All,
    Thank you for reporting the issue to us.
    We have fixed the issue in the latest version of InDesign, Id 15.0

    Please upgrade your InDesign application to the latest version to try out the fix.

    If you face any problems with the new update, do let us know in the comments.

    You may also follow the below given link for the list of all fixed issues in Id 15.0
    https://helpx.adobe.com/indesign/kb/fixed-issues.html

    -InDesign Team

13. pdfComment -- no way to find relevant text in the document

    There has to be a way to get the relevant text in the document -- or else there's no point to making the pdfComments available

    4 votes

    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

    0 comments  ·  Java Script  ·  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

14. Preflight for books

    You can preflight books: myBook.preflight()
    But there is no corresponding function to preflight individual documents. Please add the preflight() function to the document object.

    4 votes

    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

    0 comments  ·  Java Script  ·  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

15. Indesign crash with findGrep()

    findGrep() causes a crash with the following terms:
    "w?"
    “\w?”
    “h?”
    “w?i?”
    ...

    e.g.:
    app.findGrepPreferences = NothingEnum.nothing;
    app.changeGrepPreferences = NothingEnum.nothing;
    app.findGrepPreferences.findWhat = "w?";
    var _result = app.activeDocument.findGrep();

    4 votes

    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

    6 comments  ·  Java Script  ·  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
    FIXED  ·  Abhinav Kaushik responded

    Hello All,

    Thank you for reporting the issue to us.
    We have fixed the issue in the latest version of InDesign, Id 14.0.3

    Please upgrade your InDesign application to the latest version to try out the fix.

    If you are unable to see the update yet, go to Creative Cloud desktop application, open the menu (three dots) from the top-right corner and click on ‘Check For App Updates’.

    If you face any problems with the new update, do let us know in the comments.

    You may also follow the below given link for the list of all fixed issues in Id 14.0.3
    https://helpx.adobe.com/indesign/kb/fixed-issues.html

16. InDesign 2026 crash on UXP plugin shutdown – regression bug

    This bug appeared in InDesign 2025 v20.4.1, then was fixed in InDesign 2025 v20.5 (see this thread: https://indesign.uservoice.com/forums/913162-adobe-indesign-sdk-scripting-bugs-and-features/suggestions/50122545--id-4265726-error-during-shutdown-uxp-plugin-inde).

    The bug is present again in InDesign 2026 v21.0

    Philip

    3 votes

    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  ·  UXP plugins  ·  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

17. [ID-4265726]Error during shutdown UXP plugin (InDesign 20.4.1)

    If you try to access indesign.app when shutting down a plugin, an error is thrown and causes InDesign to freeze. Specifically, in the lifecycle hook »hide« and »destroy«.

    The error occurred with version 20.4.1

    ---

    Exception: Error: Shutting down in progress, can't process! at Object.cleanup (/Users/<username>/Desktop/UXP-Panel-Dummy/pkg/panel/hide.js:26:24) at ./main.js:58:31 at new Promise (<anonymous>) at e.exports.hide (./main.js:57:16) at e.exports.destroyPanel (uxp://uxp-internal/pluginmanagerscripts.js:2:38052)
    app: Application {conditionalTextPreferences: undefined}
    docCount: <unreadable>

    this: Object

    A dummy plugin can be downloaded here:
    https://kdrive.infomaniak.com/app/share/1606376/3efc4813-cd2e-40a1-9844-193d31807628

    How to reproduce the error:
    1: Load plugin in UDT
    2. Unload plugin in UDT

    Here is a report from another user: https://forums.creativeclouddeveloper.com/t/indesign-20-4-1-issue-with-the-destroy-lifecycle-hook/11133

    •  

    3 votes

    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  ·  UXP plugins  ·  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
    Closed: Fixed  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

    The fix of the issue is now available in the latest InDesign 2025(v20.5.0.048). We recommend you upgrade to the latest version for the fix.

    If you are unable to see the update, go to the Creative Cloud application click on the context menu on the top right, and click on Check for App Updates.

    —

    Adobe InDesign Team

18. InDesignServer - All Layers are allways unlocked

    InDesign Server 2021 and 2022 do unlock all Layers every time a document is opened.
    There is no way to know the initial state of the layers. They are always unlocked for the Scripting.
    Furthermore, this change is also saved to the document, removing the locks the user did.
    I tested this with following script:

    var file = new File("C:/Test/Test.indd");
    var doc = app.open(file);
    for (var i = 0; i < doc.layers.length; i++) {
    var layer = doc.layers[i];
    app.consoleout("Layer " + layer.name + " Locked: " + layer.locked + " Visible: " + layer.visible);
    }
    doc.close(SaveOptions.YES);

    I've already posted this into the community forum for InDesign, were the issue was confirmed.

    https://community.adobe.com/t5/indesign-discussions/indesignserver-all-layers-are-allways-unlocked/m-p/12894915#M474444

    Affected Versions: (As far a i could test it)
    2021 and 2022
    It works correctly in InDesignServer 2020

    InDesign Server 2021 and 2022 do unlock all Layers every time a document is opened.
    There is no way to know the initial state of the layers. They are always unlocked for the Scripting.
    Furthermore, this change is also saved to the document, removing the locks the user did.
    I tested this with following script:

    var file = new File("C:/Test/Test.indd");
    var doc = app.open(file);
    for (var i = 0; i < doc.layers.length; i++) {
    var layer = doc.layers[i];
    app.consoleout("Layer " + layer.name + " Locked: " + layer.locked + " Visible: " + layer.visible);
    }
    doc.close(SaveOptions.YES);

    I've already posted this… more

    3 votes

    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

    0 comments  ·  InDesign Server  ·  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

19. Text variable instances. Please change TextVariableInstance::resultText from read only to read/write for modifying with scripts

    It would also be nice to plug a script to modify the text replacement from the text variable dialog.

    Such an opportunity is needed, for example, for alternatively replacing paragraphs that are too long with a shortened version.

    3 votes

    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

    0 comments  ·  Java Script  ·  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

20. Add an Application Event for "failedToOpen", similar to "beforeOpen" and "afterOpen"

    It would be useful to be able to create an Event Listener that would fire when a document failed to open. It would be great if we could cancel the default behavior using the PreventDefault.

    My use case is the following. We offer a script that adds a custom menu item to allow users to select, convert, and open files that aren't usually supported by InDesign. We want to be able to offer the same type of functionality if the user attempts to open one of our supported file types through the standard Open Dialog (File->Open).

    We would set up an Event Listener for "failedToOpen," which would validate that the file is one we support. If so, we would PreventDefault and prompt the user, asking if they'd like the file converted. If we didn't support the file type, we would allow the default behavior.

    It would be useful to be able to create an Event Listener that would fire when a document failed to open. It would be great if we could cancel the default behavior using the PreventDefault.

    My use case is the following. We offer a script that adds a custom menu item to allow users to select, convert, and open files that aren't usually supported by InDesign. We want to be able to offer the same type of functionality if the user attempts to open one of our supported file types through the standard Open Dialog (File->Open).

    We would set up… more

    3 votes

    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

    0 comments  ·  Java Script  ·  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