75 results found

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

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

   16 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

3. Table footnotes not indexed correctly

   Table footnotes are not indexed correctly in two ways: to the script engine they appear in the wrong order and table footnotes have no .index property.

   The attached document has one text frame with three footnotes in the main text and one table with one footnote. The table footnote is footnote 3. To reproduce the problem, do this:

   1. Open the document.
   2. Run this script against the document (in the ESTK):

   fnotes = app.documents[0].stories[0].footnotes
   for (i = 0; i < fnotes.length; i++) {
   $.writeln (fnotes[i].contents)
   }

   1. Expected output:

   . Note 1.
   . Note 2.
   . Note table.
   . Note 4.

   1. Actual output:

   . Note 1.
   . Note 2.
   . Note 4.
   . Note table.

   Now do this, still with the same document:

   app.documents[0].stories[0].footnotes[3].index

   This returns an error. The error message is 'index'. Footnotes outside of tables correctly return their index as expected.

   Table footnotes are not indexed correctly in two ways: to the script engine they appear in the wrong order and table footnotes have no .index property.

   The attached document has one text frame with three footnotes in the main text and one table with one footnote. The table footnote is footnote 3. To reproduce the problem, do this:

   1. Open the document.
   2. Run this script against the document (in the ESTK):

   fnotes = app.documents[0].stories[0].footnotes
   for (i = 0; i < fnotes.length; i++) {
   $.writeln (fnotes[i].contents)
   }

   1. Expected output:

   . Note 1.
   . Note 2.
   . Note table.
   . Note 4.

   1. Actual output:

   . Note 1.
   . Note… more

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

4. [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 )

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

   Thanks for reporting the issue. We are reviewing it

   -InDesign Team

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

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

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

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

   Thanks for reporting the issue. We are reviewing it

   -InDesign Team

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

   •  

   •  

   •  

   •  

   •  

   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

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

   Thanks for reporting
   We are reviewing the issue

   -InDesign Team

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. TextFrame ExportFile to Snippet fails if source selection is inner text (ex: an insertionPoint)

    Select an insertionPoint, call parent textFrame through
    app.selection[0].parentStory.textContainers[0]
    Then
    call exportFile (snippet) on that object and export fails.
    It seems the scripting engine has kept the initial insertionPoint as reference when exportFile is called leading to an execution error (this export format cannot be applied to this object).
    It should work.
    Bug encountered with several versions/os.

    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

    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
    We are reviewing the issue

    -InDesign Team

11. Add MeasurementEditboxes to ScriptUI

    I'd love to see MeasurementEditboxes to ScriptUI. We had them previously, and I don't know why they were never added to ScriptUI.

    You can read more background here https://forums.adobe.com/thread/1007448

    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

    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

12. XSLX Import partially fails on Windows

    The problem is while manual import of XSLX files is no worries, it partially fails when the placement is called from script on Windows.
    The main issue is that sheetName property seems to be ignored leading to the first sheet always being placed no matter which sheetName has been set.
    The expected behaviour is that the sheetName set in app.excelImportPreferences.sheetname is correctly placed.
    No problem with old xls format or with xlsx on mac.

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

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

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

15. Please expose a PDF's page count to scripting

    I posted this one in the general feature requests section, should have done that here in scripting. Here's the link:

    https://indesign.uservoice.com/forums/601021-adobe-indesign-feature-requests/suggestions/32582917-please-expose-a-pdf-s-page-count-to-scripting

    It got quite a few votes over there. . .

    P.

    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

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

17. Add `parentPage` and `parentTextFrame` of Table Cell and Row

    Please add parentPage and parentTextFrame to cell and row. Up to now it is not possible to determine, on which page or in which text frame a specific table cell/row is located.

    There is a hack with adding an anchored text frame, releasing it an reading its properties. But this is very hacky an time consuming ...
    Or I have to use insertion points inside the cells/rows to get to the parentPage.
    But this is all very clumsy.
    ( See here: https://community.adobe.com/t5/indesign-discussions/extendscript-indesign-2022-return-parentpage-s-of-last-cells-of-all-tables/m-p/12942541#M477149 )

    Thanks,
    Tobias

    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

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

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

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