54 results found

1. InDesign does not load type library on upgrade

   Similar to the 2020 release (see https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/41072476-type-library-is-not-automatically-created-by-cc202), InDesign 2022 does not install the type library in upgrade. Please include this with the installation, as this will cause errors for many users.

   Error message: Error: Unable to load Adobe InDesign 2022 Type Library (Version 1.0).

   •  

   2 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  ·  Scripting  ·  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

2. Custom menus created by script stay after relaunching InDesign

   There's a bug in InDesign 2022 where custom menus created by a script stay after relaunching InDesign.

   How to reproduce:

   -Run this AppleScript script which will create a menu titled Custom Menu:

   tell application "Adobe InDesign 2022"
   tell menu "$ID/Main" to make submenu with properties {title:"Custom Menu"}
   end tell

   -Relaunch InDesign

   The menu Custom Menu will still be there. While it should NOT be there unless explicitely created by a script again.

   The only way to remove it is to run a separate script that specifically removes the menu.

   It's a big problem for third-party software: for example, where users remove a startup script that created the menu - but the menu doesn't go away.

   There's a bug in InDesign 2022 where custom menus created by a script stay after relaunching InDesign.

   How to reproduce:

   -Run this AppleScript script which will create a menu titled Custom Menu:

   tell application "Adobe InDesign 2022"
   tell menu "$ID/Main" to make submenu with properties {title:"Custom Menu"}
   end tell

   -Relaunch InDesign

   The menu Custom Menu will still be there. While it should NOT be there unless explicitely created by a script again.

   The only way to remove it is to run a separate script that specifically removes the menu.

   It's a big problem for third-party software: for example, where users… more

   1 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

   0 comments  ·  Scripting  ·  Edit…  ·  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

3. "add bullets and numbering option in other languages like hindi"

   • 

   1 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

   0 comments  ·  Scripting  ·  Edit…  ·  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

4. AppleScript Finder communication

   InDesign version 16.3.2 with OSX 10.14.6 or later

   Indesign script‘s with calls to the Finder or other Apple apps work running from Apple’s Script Editor, but break when running from InDesign’s Scripts panel. Get an Not Authorized to Send Apple Events to Finder error.

   This breaks when running from the Scripts panel, but worked with InDesign 2020:

   tell application id "com.adobe.InDesign"
   tell application "Finder"
   activate
   display dialog "Hello"
   end tell
   end tell

   Calls to other Adobe apps are ok, so this still works from the panel:

   tell application id "com.adobe.InDesign"
   tell application id "com.adobe.Photoshop"
   activate
   display dialog "Hello"
   end tell
   end tell

   InDesign version 16.3.2 with OSX 10.14.6 or later

   Indesign script‘s with calls to the Finder or other Apple apps work running from Apple’s Script Editor, but break when running from InDesign’s Scripts panel. Get an Not Authorized to Send Apple Events to Finder error.

   This breaks when running from the Scripts panel, but worked with InDesign 2020:

   tell application id "com.adobe.InDesign"
   tell application "Finder"
   activate
   display dialog "Hello"
   end tell
   end tell

   Calls to other Adobe apps are ok, so this still works from the panel:

   tell application id "com.adobe.InDesign"
   tell application id "com.adobe.Photoshop"
   activate
   display dialog "Hello"
   end tell… more

   •  

   6 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  ·  Scripting  ·  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

5. [ID-4236366]Scripts using BridgeTalk do not work on M1 Macs (regardless of CC version)

   ID version: InDesign CC 2021 (16.3.2)
   OS: macOS Big Sur 11.5.2
   Processor: Apple M1

   When I try to run a script that uses BridgeTalk and works with Photoshop, it does not work.
   Also, a simple script using BridgeTalk will not work as well.
   Those scripts do work in CC 2021 on Intel Mac and macOS Big Sur 11.5.2.

   25 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  ·  Scripting  ·  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
   Under Review  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   Hi,

   The issue is under review.

   —

   Adobe InDesign Team

6. close book in event handler is out of sync

   function closeBooks() {
   var books = app.books.everyItem().getElements();
   var i, ilen = books.length;

   for (i = 0; i < ilen; i++) {
       if (books[i].modified) {
           books[i].close(SaveOptions.ASK);
       }
   }
   alert('done');
   

   }

   if you call the closeBooks function, everything works fine.
   But if the function is used as a handler, the "done" message appears immediately, before the for loop complete.

   try adding a beforeQuit eventListener:
   app.addEventListener('beforeQuit', closeBooks);

   and close InDesign having one or more modified books to see this (strange) behaviour.

   The same function works fine if you target documents.

   InDesign CC2021 16.2.1 on MacOs Catalina 10.15.7

   1 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

   0 comments  ·  Scripting  ·  Edit…  ·  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

7. External Object 'lib:AdobeXMPScript' not exist!

   Try to execute the attached code in the screenshot.
   And you will this error:

   Error Number: 52
   Error String: I/O Error

   •  

   18 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  ·  Scripting  ·  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
   Closed: Fixed  ·  AdminRavi Kiran (Senior Lead Quality Engineer, Adobe InDesign) responded

   This issue was fixed in InDesign version 16.3 that was released some time back.
   Closing this issue.

   —
   Adobe InDesign team

8. Can't read XML attributes from tagged image contained into table

   Can't read XML attributes from tagged image contained into table.

   Hello, I have some problems when I use one script Javascript to read XML attributes of tagged images contained into tables.
   One XML file with data is imported into document with existing XML structure. In attached example there is a simply structure with one tagged text frame. When importing XML data, text frame contain one simply tagged table with one tagged image into one cell.
   In earlier versions of Indesign (up to CC 9.2) this script works fine.
   In later versions this script not read correctly these attributes: in CC2020 version script read container cell attributes; in CC2021 instead script read correct XML element but this element appears invalid.
   If I first import XML file into an empty document and then tag the text frame then there is no problems!

   ---

   Adobe InDesign CC2021(16.1)
   MacOS Mojave 10.14.4 on Mac mini (Late 2014) 3 GHz Intel Core i7

   1) New file from scratch
   2) Add new text frame and tag it with "TEXT"
   3) Import example XML file "imgattrs.xml"
   4) Run script file "imgattrs.jsx"

   EXPECTED RESULT: read XML attributes of tag "IMG"
   ACTUAL RESULT: "IMG" xmlElement is not valid.

   ---

   Javascript:

   var doc = app.documents[0];
   var root = doc.xmlElements.firstItem();
   var frame = doc.textFrames[0];

   var xmlelems = root.evaluateXPathExpression("//IMG");
   var rectxml = xmlelems[0];
   if (rectxml && rectxml.isValid) {
   var attrsnames = rectxml.xmlAttributes.everyItem().name;
   var attrsvalues = rect_xml.xmlAttributes.everyItem().value;
   }

   ---

   XML file to import:

   <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
   <Root><TEXT><Table xmlns:aid="http://ns.adobe.com/AdobeInDesign/4.0/" aid:table="table" aid:trows="3" aid:tcols="2"><Cell aid:table="cell" aid:theader="" aid:crows="1" aid:ccols="1" aid:ccolwidth="82.91338582677166"></Cell><Cell aid:table="cell" aid:theader="" aid:crows="1" aid:ccols="1" aid:ccolwidth="82.91338582677166"></Cell><Cell aid:table="cell" aid:crows="1" aid:ccols="1" aid:ccolwidth="82.91338582677166"></Cell><Cell aid:table="cell" aid:crows="1" aid:ccols="1" aid:ccolwidth="82.91338582677166"><IMG href="file://img.jpg" height="42" width="42" object_style="img_listino" noback="1"></IMG></Cell><Cell aid:table="cell" aid:crows="1" aid:ccols="1" aid:ccolwidth="82.91338582677166"></Cell><Cell aid:table="cell" aid:crows="1" aid:ccols="1" aid:ccolwidth="82.91338582677166"></Cell></Table></TEXT></Root>

   Can't read XML attributes from tagged image contained into table.

   Hello, I have some problems when I use one script Javascript to read XML attributes of tagged images contained into tables.
   One XML file with data is imported into document with existing XML structure. In attached example there is a simply structure with one tagged text frame. When importing XML data, text frame contain one simply tagged table with one tagged image into one cell.
   In earlier versions of Indesign (up to CC 9.2) this script works fine.
   In later versions this script not read correctly these attributes: in CC2020… more

   •  

   1 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

   0 comments  ·  Scripting  ·  Edit…  ·  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

9. script panel blank

   Nenhum Script aparece no painel. Todos sumiram, e todos os scripts estão na pasta do ID.

   2 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  ·  Scripting  ·  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

10. batch open/close documents with script consumes lots of memory

    I have used the script to convert indesign files to idml or vice versa. It works as I expected.

    yet while I want to run another script during batch process to each file the memory which indesign consumes during process dramatically increasing.

    while normal batch process consumes at least 1GB for 100 document, with running script file with some process consumes at least 40-50GB RAM and It causes computer no to respond

    1 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

    0 comments  ·  Scripting  ·  Edit…  ·  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

11. export layers to photoshop

    would be so nice to have a way to export inDesign layers to Photoshop file. (would save hundreds of hours to rebuild all these files!)

    2 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  ·  Scripting  ·  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

12. FindChangeByList not working

    1 The script stopped working. Doesn’t do anything.

    2 Please let the updater copy the FindChangeList.txt from the previous version. In most cases it’s part of a workflow that breaks with each update.

    2 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  ·  Scripting  ·  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

13. Navigation Points Not Available to Scripting in InDesign 2021 (16.0)

    Problem Description:
    Querying navigation points inside a movie trigger errors from InDesign 16.

    Steps to Reproduce:
    1. Query movie.navigationPoints.length or movie.navigationPoints.count() with Extendscript.

    The following script shows this issue(s) with simple document containing a move and one button with a play at navigation point action applied.

    var btn = app.activeDocument.buttons[0];
    var beh = btn.behaviors[0];
    var mov = beh.movieItem;
    var navPts = mov.navigationPoints;
    try{
    alert(navPts.length); /doesn't exist/
    }catch(err) { alert([err,err.line])}

    try{
    alert(navPts.count()); /*Give incorrect error - Error: Request failed because the underlying functionality is no longer available in the current version of the application */
    }catch(err) { alert([err,err.line])}

    alert(navPts.everyItem().getElements().length); /incorrectly says zero, when there are 2 navigation points/

    Actual Result:
    Each produces two separate errors.

    Expected Result::
    Both should be valid queries.

    Any Workarounds:

    No. Expected functionality is simply missing.

    movie.navigationPoints.everyItem().getElements().length at least doesn't produce an error, but it also doesn't include navigation points.

    This feature was added back to InDesign, but the scripting of it was neglected. I've filed a bug in prerelease as well. Posting here so others are aware.

    Problem Description:
    Querying navigation points inside a movie trigger errors from InDesign 16.

    Steps to Reproduce:
    1. Query movie.navigationPoints.length or movie.navigationPoints.count() with Extendscript.

    The following script shows this issue(s) with simple document containing a move and one button with a play at navigation point action applied.

    var btn = app.activeDocument.buttons[0];
    var beh = btn.behaviors[0];
    var mov = beh.movieItem;
    var navPts = mov.navigationPoints;
    try{
    alert(navPts.length); /doesn't exist/
    }catch(err) { alert([err,err.line])}

    try{
    alert(navPts.count()); /*Give incorrect error - Error: Request failed because the underlying functionality is no longer available in the current version of the application */
    }catch(err) { alert([err,err.line])}

    alert(navPts.everyItem().getElements().length);… more

    64 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  ·  Scripting  ·  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
    FIXED  ·  AdminRavi Kiran (Senior Lead Quality Engineer, Adobe InDesign) responded

    The fix for this issue is available in the latest InDesign release 16.2.1
    Please update to this latest version to get the fix.

    —
    Adobe InDesign team

14. ID 2020 bug - checkbox not shown.

    in ID2019 everything is Ok - the checkbox is visible. But in 2020 - not!

    var w = new Window("dialog");
    var list = w.add ("listbox", undefined, ["One", "Two", "Three", "Four"]);
    list.items[1].checked = true;
    w.show();

    •  

    8 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  ·  Scripting  ·  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
    Under Review  ·  amaarora responded

    Thanks for reporting the issue
    We are reviewing it

    -InDesign Team