74 results found

1. 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

2. InDesign Scripting bug? Master Pageitems of specific Layer as Collection

   I want to see all 'master' page items of all master spreads on a specific layer using code like this:

   app.activeDocument.layers.itemByName('existLayerName').pageItems.everyItem().getElements();

   Even such a layer contains 'master' page items, this code always returns an empty array!

   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  ·  Java Script  ·  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. Events: 'afterSelectionAttributeChanged' (LayoutWindow)

   The event 'afterSelectionAttributeChanged' (LayoutWindow) has the "Event" class, but logically its class should be "MutationEvent", since it is not clear which attribute of the object has been changed...

   The mutation event in most classes that have an addEventListener method does not work.

   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  ·  Java Script  ·  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. Update Indesign script to support ES6

   Update Indesign to support modern ES6.

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

5. Separate the indesign scripting forum from the indesign community support forum

   With the relaunch of Adobe's community support forums, the indesign scripting forum was merged with the general indesign forum. Please separate the two so users can find the most relevant content.

   45 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

   19 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
   Partial Fix  ·  amaarora responded

   Hi,
   1. The majority of InDesign Scripting threads were merged and archived at first.
   2. After a month or so, InDesign Scripting re-appeared as its own topic in the new forums.
   3. David K. started un-archiving older threads last week, a few at a time, very slowly and by hand, because of odd server-side limitations.
   4. There is no “Direct Link” to the Scripting Topic at this time, but this ought to be fixed with the current sprint from the forums team. The internal bug number is: ALFD-1530

   While we wait for ALFD-1530, there is a backdoor way to find direct links to topics. You can follow a topic then look at your follows… or just use these links:

   • InDesign Scripting: https://community.adobe.com/t5/forums/filteredbylabelpage/board-id/indesign/label-name/scripting
   • InDesign SDK: https://community.adobe.com/t5/forums/filteredbylabelpage/board-id/indesign/label-name/sdk
   • InDesign Server Developers: https://community.adobe.com/t5/forums/filteredbylabelpage/board-id/indesign/label-name/server%20developers

   Thanks

6. fos az egesz

   szar

   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  ·  Java Script  ·  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. BUG - Scripting: multiple paragraph styles for multiple paragraphs in one text box not working correctly

   Paragraph styles are not being applied correctly when setting more than two paragraph styles for more than one paragraph in a text box.

   For three or more paragraphs, paragraph n is set to paragraph style n, and paragraphs 1 through n-1 are set to paragraph style n-1. The expected behaviour would be that paragraph 1 is set to paragraph style 1, paragraph 2 is set to paragraph style 2, paragraph 3 is set to paragraph style 3, ..., paragraph n is set to paragraph style n.

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

8. Bug When Overriding Master Page Items: Unexpected Shift of Master Page Objects

   When overriding page items by script, those items are unexpectedly shifted and do not stay in the x/y position, they are on the master page. This differs widely from the UI-behaviour of InDesign.

   There is a very good view and analysis of this bug from Marc Autret, which can be found here:
   http://www.indiscripts.com/post/2014/06/indesign-scripting-forum-roundup-6#hd1sb2

   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

   7 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

9. Setting stroke weight to 0 by script results in 1 pt

   Given a frame (graphic or text) with stroke color set to 'None' and stroke weight set to 0, the jsx command "app.selection[0].strokeWeight = 0" sets the weight to 1pt and stroke color to the default swatch.

   Steps to reproduce:

   1. Create a new Document.
   2. Create a new Text (or Graphic) Frame.
   3. Set the stroke weight to 0 and color to 'None' if necessary
   4. Select the frame with the Selection tool.
   5. Start a script with a following one line: app.selection[0].strokeWeight=0

   Expected result: no change
   Actual result: stroke weight set to 1pt and color to the default swatch.

   Note:
   Setting stroke weight to any other value behaves as expected.

   InDesign CC2018 v13.0.1

   Given a frame (graphic or text) with stroke color set to 'None' and stroke weight set to 0, the jsx command "app.selection[0].strokeWeight = 0" sets the weight to 1pt and stroke color to the default swatch.

   Steps to reproduce:

   1. Create a new Document.
   2. Create a new Text (or Graphic) Frame.
   3. Set the stroke weight to 0 and color to 'None' if necessary
   4. Select the frame with the Selection tool.
   5. Start a script with a following one line: app.selection[0].strokeWeight=0

   Expected result: no change
   Actual result: stroke weight set to 1pt and color to the default swatch.

   Note:
   Setting stroke weight to… more

   7 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

10. [15.0.0.155] New property Alternate Text for Hyperlinks is not supported by Scripting, IDMS and IDML

    Hi,
    I see no new property for a new feature with InDesign 2020 version 15.0.0.155:
    Alternate Text for Hyperlinks.

    The feature is also missing with IDMS and IDML.

    Regards,
    Uwe Laubender
    ( ACP )

    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

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

    Thanks for reporting the issue. We are reviewing it

    -InDesign Team

11. 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.

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

12. Allow keyboard shortcuts to be assigned by script

    Add the ability to assign keyboard shortcuts do built-in InDesign menu actions or panel menus by javascript.

    14 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

13. 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

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

14. 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

15. app.activeBook

    When more than one book is open, selecting the book tab (when they're tabbed), doesn't work for app.currentBook in scripting. It's needed to click inside the book panel to have it targeted. Just the tab selected doesn't work.

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

16. GREP Find and replace Script not working CC2019

    We are getting below error while running the GREP script in InDesign CC2019, but same is working fine in CS6 version. Please check and fix this bug quickly to migrate CC2019 version.

    Error: User canceled this action

    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

    5 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

17. Scripted iterative document open/close fails to close files

    Note: my sample code is jsx, but the problem may not be limited to jsx. Change the filetype of my provided files from txt to jsx prior to using!

    We have multiple products that sometimes show a problem with document.close() not actually closing the file, leading to incorrect functioning, memory bloat, slowdowns, and we believe some crashes. I provide a test script that takes a currently open document and iteratively copies it, opens the copy, then closes the copy -- after the loop is finished, the copy files are removed.

    Important: If run from the ESTK or Scripts Panel, the script works as expected -- no problems. If run from a custom menu (setup script also provided), the problem happens every time.

    We believe we've seen this in cases where a custom menu is not the launch mechanism, and may be intermittent in those cases.

    We believe we've seen this in InDesign Server as well. My scripts have been tested in CC 2019 and CC 2020 and on both Win and Mac.

    In order to run the "Test_menu.jsx" script for using a custom menu, the "Documents left open on close.jsx" script must be in a "TestScripts" folder in your 'home' or 'user' folder (i.e., inside of "~/TestScripts").

    This problem is a real headache and is difficult to work around. It affects multiple product areas; we urge prompt attention to this problem.

    Thanks.

    Note: my sample code is jsx, but the problem may not be limited to jsx. Change the filetype of my provided files from txt to jsx prior to using!

    We have multiple products that sometimes show a problem with document.close() not actually closing the file, leading to incorrect functioning, memory bloat, slowdowns, and we believe some crashes. I provide a test script that takes a currently open document and iteratively copies it, opens the copy, then closes the copy -- after the loop is finished, the copy files are removed.

    Important: If run from the ESTK or Scripts Panel, the… more

    • 

    • 

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

18. Scripting | graphicLayerOptions : Changing visibility of graphicLayer will change ID number of placed graphic

    Problem Description:
    If you change the visibility of a graphicLayer of a placed graphic, could be a PDF, a PSD, an InDesign page or a AI file, the ID number of the placed graphic will change. The result of this is, that "everyItem().doSomething" with object graphicLayer will not work at all.

    Steps to Reproduce:
    1. Place a graphic with some graphic layers.
    2. Access the graphic layers of the graphic by scripting and try to change eg. currentVisibility for all graphic layers in one go.
    Frame holding the graphic is selected. The script snippet below should do this easily. However, it is not!

    Note:
    In case of a placed InDesign page or a PDF exported from an InDesign document with layers intact, all InDesign layers are nested in one "layer group" so we have to look after graphicLayers[0] (that's the "layer group") and add graphicLayers.everyItem() to access all sub-layers.

    app.selection[0].graphics[0].graphicLayerOptions.graphicLayers[0].graphicLayers.everyItem().currentVisibility = false;

    Actual Result:
    Error message thrown. In my German InDesign this is:
    "Die angeforderte Aktion konnte nicht ausgeführt werden, da das Objekt nicht mehr existiert."
    This is the $ID/ObjectDeletedError

    Expected Result:
    No error message. The visibility of all graphic layers should change.

    Any Workarounds:
    Loop the graphic layers. But do so that every time you do not access a reference to the graphic by its ID number.

    Something like that will work:

    var layerLength = app.selection[0].graphics[0].graphicLayerOptions.graphicLayers[0].graphicLayers.length;

    for(var n=0;n<layerLength;n++)
    {
    $.writeln( n+"\t"+app.selection[0].graphics[0].id );
    app.selection[0].graphics[0].graphicLayerOptions.graphicLayers[0].graphicLayers[n].currentVisibility = false;
    };

    The following will NOT work:

    var graphicLayers = app.selection[0].graphics[0].graphicLayerOptions.graphicLayers[0].graphicLayers.everyItem().getElements();

    for(var n=0;n<graphicLayers.length ;n++)
    {
    graphicLayers[n].currentVisibility = false;
    };

    Why will that not work?
    See into the results in the JavaScript Console with $.writeln( n+"\t"+app.selection[0].graphics[0].id ); from the loop that is working.
    Everytime you change currentVisibility of a graphicLayer the ID of the graphic is changing. That means the object is not itself anymore.

    Here some sample output from the JavaScript Console with one of my sample files:
    /*
    Result:
    0 325
    1 331
    2 337
    3 343
    4 349
    */

    You can see that the graphic began with a ID number of 325, after changing currentVisibility of the first graphic layer it suddenly became ID 331 and so on.

    Read about this scripting issue in the InDesign Scripting Forum here:

    "Place specific pdf layer into indesign with javascript"
    Yuliascript 18.06.2018
    https://forums.adobe.com/message/10452540#10452540

    Also here a thread from 2012:
    "Activating object layers basing on document layers"
    Marco Lugli 14.12.2012
    https://forums.adobe.com/message/4920745#4920745

    Also see attached documents with a placed sample PDF:

    PlacedPDFwithLayers-13.1.0.76.zip

    Download link from my Dropbox:
    https://www.dropbox.com/s/hfsspv5ddxaakvy/PlacedPDFwithLayers-13.1.0.76.zip?dl=0

    FWIW: Did this bug report also at Bug ID - ID-4208697.

    Regards,
    Uwe Laubender
    ( ACP )

    Problem Description:
    If you change the visibility of a graphicLayer of a placed graphic, could be a PDF, a PSD, an InDesign page or a AI file, the ID number of the placed graphic will change. The result of this is, that "everyItem().doSomething" with object graphicLayer will not work at all.

    Steps to Reproduce:
    1. Place a graphic with some graphic layers.
    2. Access the graphic layers of the graphic by scripting and try to change eg. currentVisibility for all graphic layers in one go.
    Frame holding the graphic is selected. The script snippet below should do this easily. However,… more

    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

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

    Thanks for reporting the issue. We are reviewing it

    -InDesign Team

19. Scripted iterative document open/close fails to close files

    Note: my sample code is jsx, but the problem may not be limited to jsx.

    We have multiple products that sometimes show a problem with document.close() not actually closing the file, leading to incorrect functioning, memory bloat, slowdowns, and we believe some crashes. I provide a test script that takes a currently open document and iteratively copies it, opens the copy, then closes the copy -- after the loop is finished, the copy files are removed.

    Important: If run from the ESTK or Scripts Panel, the script works as expected -- no problems. If run from a custom menu (setup script also provided), the problem happens every time.

    We believe we've seen this in cases where a custom menu is not the launch mechanism, and may be intermittent in those cases.

    We believe we've seen this in InDesign Server as well. My scripts have been tested in CC 2019 and CC 2020 and on both Win and Mac.

    In order to run the "Test_menu.jsx" script for using a custom menu, the "Documents left open on close.jsx" script must be in a "TestScripts" folder in your 'home' or 'user' folder (i.e., inside of "~/TestScripts").

    This problem is a real headache and is difficult to work around. It affects multiple product areas; we urge prompt attention to this problem.

    Thanks.

    Note: my sample code is jsx, but the problem may not be limited to jsx.

    We have multiple products that sometimes show a problem with document.close() not actually closing the file, leading to incorrect functioning, memory bloat, slowdowns, and we believe some crashes. I provide a test script that takes a currently open document and iteratively copies it, opens the copy, then closes the copy -- after the loop is finished, the copy files are removed.

    Important: If run from the ESTK or Scripts Panel, the script works as expected -- no problems. If run from a custom menu (setup… 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  ·  Java Script  ·  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

20. Bug with index entry

    If you select a word after a table (»sit« in InDesign document: https://adobe.ly/2X0wXOi) and create an index entry using script, the page reference will be created after the word (under certain circumstances).

    var _doc = app.activeDocument;
    var _docIndex;

    if(_doc.indexes.length === 0) {
    _docIndex = _doc.indexes.add();
    } else {
    _docIndex = _doc.indexes.firstItem();
    }

    var textObj = app.selection[0];
    var _parentTopic = _docIndex.topics.add("Topicname");
    var _pageRef = _parentTopic.pageReferences.add(textObj);

    – word before that, everything's correct.
    – tables with 3 or more rows
    – the more table rows the more offset

    •  

    •  

    •  

    •  

    •  

    7 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

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

    Thanks for reporting
    We are reviewing the issue

    -InDesign Team