119 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. Sample script "PlaceMultipagePDF.vbs" does not work properly

   Related threads in the support community
   https://community.adobe.com/t5/indesign%E3%83%95%E3%82%A9%E3%83%BC%E3%83%A9%E3%83%A0/ct-p/ct-indesign-jp?page=1&sort=latest_replies&filter=all&lang=all&tabid=discussions&profile.language=ja

   The above is a recent event, but the following thread is from 2018. We can assume that the situation is not good and has been going on for several years.
   https://community.adobe.com/t5/indesign-discussions/indesign-placemultipagepdf-script-only-adds-pdfs-to-the-end-of-the-document/m-p/14015164?profile.language=en#M538521

   I can't try it in CS already, but presumably the problem is still the same and bad in all versions since CC.

   The "PlaceMultipagePDF.vbs" set of sample scripts pre-installed in InDesign clearly behaves abnormally compared to the .jsx, .applescripts of the same name.

   Observing the behavior of .jsx and .applescript, it seems that the following processing steps are involved. 1.
   1. display a dialog to select a PDF file
   2. select target document from new or existing documents
   3. if user selects an existing document, select target page from pull-down
   4. place the first page of the PDF on the selected page of the indd document
   5. add a new page immediately after the selected page of the indd document
   6. place the next page of the PDF
   7. loop through 5. and 6. until the PDF page reaches the end

   .vbs behaves differently in the middle.
   4. ignore selected pages in indd document and add pages to the end of indd document
   5. place "second page" of PDF
   6. loop 4. and 5. until the PDF page reaches the end, but the "first page" of the PDF is placed at the end
   7. the last page of the indd document is deleted (where the first page of the PDF is placed)

   Even for Windows users, the user's goal can be achieved by choosing .jsx instead of .vbs.
   However, not all users can determine which is correct. Also, who would expect such different results from different scripting languages, even though they have the same name?
   In any case, the pre-installation of scripts that do not work properly as samples should be taken seriously.
   I think the solution is to fix the contents of the .vbs and reflect them in updates, or else exclude them from the pre-installed packages.

   <Japanese>：にほんご
   サンプルスクリプト「PlaceMultipagePDF.vbs」は正常に動作しない

   サポートコミュニティの関連スレッド
   link
   上記は近日の出来事だが、下記スレッドは2018年のことである。よくない状況が数年間続いていることが推測できる。
   link
   私は既にCSで試すことができないが、おそらくこの問題はCC以降すべてのバージョンで変わりなく不良であると思われる。

   InDesignにプリインストールされているサンプルスクリプト群の “PlaceMultipagePDF.vbs” は、同名の .jsx, .applescript と比較して明らかに動作が異常である。

   .jsx, .applescript の挙動を見守ると、以下の処理工程のようである。
   1. PDFファイルを選択するダイアログ
   2. 新規ドキュメント、または既存ドキュメントからターゲットドキュメントを選択
   3. ユーザーに既存ドキュメントが選択された場合、ターゲットページをプルダウンから選択
   4. inddの選択されたページに、PDFの始めのページを配置
   5. inddの選択されたページのすぐ後ろに新規ページを追加
   6. PDFの次のページを配置
   7. PDFのページが末尾に達するまで5.と6.をループ

   .vbs の挙動は途中で異なる。
   4. inddの選択されたページを無視して、inddのドキュメント末尾にページを追加
   5. PDFの2番目のページを配置
   6. PDFのページが末尾に達するまで4.と5.をループするが、最後にPDFの始めのページが配置される
   7. inddの最後のページが削除される（PDFの始めのページの配置先）

   Windowsユーザーであっても、 .vbs は使用せず、.jsxを選ぶことでユーザーの目的は達成できる。
   しかし、どちらが正しいか、すべてのユーザーは判断できない。また、スクリプト言語の違いでこんなに結果が異なるなんて誰が予想できる？
   いずれにしても、まともに動作しないスクリプトがサンプルとしてプリインストールされることは真剣に問題視するべきである。
   .vbsの内容を修正しアップデートに反映する、さもなくばプリインストールのパッケージから除外してしまうことが解決法だと考える。

   Related threads in the support community
   https://community.adobe.com/t5/indesign%E3%83%95%E3%82%A9%E3%83%BC%E3%83%A9%E3%83%A0/ct-p/ct-indesign-jp?page=1&sort=latest_replies&filter=all&lang=all&tabid=discussions&profile.language=ja

   The above is a recent event, but the following thread is from 2018. We can assume that the situation is not good and has been going on for several years.
   https://community.adobe.com/t5/indesign-discussions/indesign-placemultipagepdf-script-only-adds-pdfs-to-the-end-of-the-document/m-p/14015164?profile.language=en#M538521

   I can't try it in CS already, but presumably the problem is still the same and bad in all versions since CC.

   The "PlaceMultipagePDF.vbs" set of sample scripts pre-installed in InDesign clearly behaves abnormally compared to the .jsx, .applescripts of the same name.

   Observing the behavior of .jsx and .applescript, it seems that the following processing steps are involved. 1.
   1. display… more

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

   This issue has been resolved in the latest version of InDesign 2024(v19.0).  Please update to this version of InDesign from Creative Cloud Desktop application to get the fix.

   --

   Adobe InDesign team

5. HyperlinkTextDestination elements missing from anchored objects in exported icml

   When exporting icml from InDesign, anchored objects with hyperlink text destinations inside of them are missing those destinations.

   Steps to reproduce:

   1. Make a new document with text.
   2. Insert an anchored text frame with text into the story.
   3. Insert a hyperlink text destination into the anchored text frame.
   4. Create a hyperlink from outside of the text frame to inside of it.
   5. Export icml of the story.

   In the exported icml, the hyperlink destination will be missing and the link will be broken.

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

6. InDesign 16.3.2 not authorised to send Apple events to other apps

   I’m using the InDesign do script AppleScript command to instruct another application to do something.
   Since 16.3 this doesn’t work anymore, because macOS prevents the script from running. Previous versions of InDesign worked fine, after the user allowed InDesign to control the target app.

   Usecase:
   I’m the developer of a font manager and want InDesign to report which fonts are used in a document

   macOS version: 11.3.1
   InDesign version: 16.3.2

   Steps to reproduce:

   1. Reset the macOS Apple Event permissions for InDesign in Terminal:
      tccutil reset AppleEvents com.adobe.InDesign

   2. Run the following AppleScript:
      tell application id "com.adobe.InDesign"
do script "tell application \"Finder\" to display dialog \"Hello\""
end tell

   Expected:
   1. macOS asks to allow InDesign to control Finder
   2. After confirming, Finder shows an alert

   Actual:
   AppleScript error: Not authorized to send Apple events to Finder. (-1743)

   Background info:
   InDesign versions before 16.3 worked fine. I’ve been using do script to communicate with my app without issues. When running the script the first time macOS will ask the user to allow InDesign to control my app. After confirming or dismissing this dialog a new entry in System Preferences > Security & Privacy > Automation will show up for Adobe InDesign 2021.app

   If the Automation entry is checked communication is authorised and the script works fine. If the user did not allow control, the entry is unchecked and can be enabled at any moment by the user in System Preferences > Security & Privacy > Automation.

   Since InDesign 16.3 the macOS permission dialog doesn’t show up anymore. The user is not asked to give permissions and the entry will never show up in Automation. This results in all scripts failing due to no authorisation to communicate with external apps.

   If the user had previously allowed control (e.g. using InDesign 16.2), the Automation permission is persistent and works for 16.3 as well. But if it’s a first-time user, or if the Automation permission is reset, InDesign 16.3 will never trigger the dialog anymore.

   To reset macOS Apple Event permissions run the following command in Terminal:
   tccutil reset AppleEvents com.adobe.InDesign

   Solution:
   Looks like adding NSAppleEventsUsageDescription to the InDesign Info.plist solves the issue. Once this key is added the macOS permission dialog will show up correctly again.
   I’ve successfully confirmed this by adding this key to the plist:
   plutil -insert NSAppleEventsUsageDescription -string "This script needs to control other applications to run." /Applications/Adobe\ InDesign\ 2021.app/Info.plist

   And resigning the .app using a custom signing certificate (changing the Info.plist will break the original signing).

   According to https://indiestack.com/2018/08/apple-events-usage-description/ this key is required when linking against the macOS 10.14 SDK. Perhaps that’s what has changed in 16.3?

   If you need any further information to reproduce this issue, or information about the solution please let me know.

   I’m using the InDesign do script AppleScript command to instruct another application to do something.
   Since 16.3 this doesn’t work anymore, because macOS prevents the script from running. Previous versions of InDesign worked fine, after the user allowed InDesign to control the target app.

   Usecase:
   I’m the developer of a font manager and want InDesign to report which fonts are used in a document

   macOS version: 11.3.1
   InDesign version: 16.3.2

   Steps to reproduce:

   1. Reset the macOS Apple Event permissions for InDesign in Terminal:
      tccutil reset AppleEvents com.adobe.InDesign

   2. Run the following AppleScript:
      tell application id "com.adobe.InDesign"
do script "tell application \"Finder\"… more

   9 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  ·  Apple 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. PreflightScope not working

   PreflightOptions.preflightScope in InDesign has not worked since at least CS 5.5. No matter what value is used, preflight checks the whole document. Here is a sample script (error for color image <250 ppi) that the issue can be tested:

   var currDoc = app.documents[0];
   if (app.preflightProfiles.itemByName("export").isValid){
           app.preflightProfiles.itemByName("export").remove();
   }
   var pfProfile = app.preflightProfiles.add({name: "export"});
   var pfResRule = pfProfile.preflightProfileRules.add("ADBE_ImageResolution", {flag: PreflightRuleFlag.returnAsError});
   pfResRule.ruleDataObjects.add("color_min_res", RuleDataType.realDataType, 250);
   currDoc.preflightOptions.preflightScope = '1-2';
   var pfProcess = app.preflightProcesses.add(currDoc, pfProfile);
   pfProcess.waitForProcess();
   pfResults = pfProcess.aggregatedResults[2];
   $.writeln(pfResults);
   

   ––> with a 3-page document with problems on pages 2 and 3, InDesign reports both problems despite the scope been set to ‘1-2’ (same with ‘1’ and ‘1,2’)

   We would very much like to speed our preflight process and get rid of the tedious parsing of preflight results only to discard pages not set in the scope.

   One additional note on its behavior that could be fixed, too: if you define a scope that includes page numbers not in the document, either as
   - a range e.g. "1-5" when document has pages numbers 1,4,5,6,... or
   - e.g. "14" when the document has only 12 pages
   ––> InDesign throws an error "Error 30477: Invalid value for set property 'preflightScope'. Expected PreflightScopeOptions enumerator or String, but received "1-5".", which is quite misleading.

   PreflightOptions.preflightScope in InDesign has not worked since at least CS 5.5. No matter what value is used, preflight checks the whole document. Here is a sample script (error for color image <250 ppi) that the issue can be tested:

   var currDoc = app.documents[0];
   if (app.preflightProfiles.itemByName("export").isValid){
           app.preflightProfiles.itemByName("export").remove();
   }
   var pfProfile = app.preflightProfiles.add({name: "export"});
   var pfResRule = pfProfile.preflightProfileRules.add("ADBE_ImageResolution", {flag: PreflightRuleFlag.returnAsError});
   pfResRule.ruleDataObjects.add("color_min_res", RuleDataType.realDataType, 250);
   currDoc.preflightOptions.preflightScope = '1-2';
   var pfProcess = app.preflightProcesses.add(currDoc, pfProfile);
   pfProcess.waitForProcess();
   pfResults = pfProcess.aggregatedResults[2];
   $.writeln(pfResults);
   

   ––> with a 3-page document with problems on pages 2 and 3, InDesign reports both problems despite the scope been set to ‘1-2’ (same with ‘1’… 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  ·  CEP  ·  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

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

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

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

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

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

13. Ability to identify if a Story is TOC_STORY, which TOC_STYLE is in use

    Using InDesign Server (or scripts in InDesign Desktop) via JavaScript, it would be very helpful if there was an API/mechanism for discovering details for table of contents usage.

    Current Issue:
    It doesn't look like there is a way to see if a TOCStyle is actually used anywhere. A document can contain multiple TOCStyles, but it's possible only one is placed in the document. Likewise, it doesn't appear there is a way to resolve the TOCStyle being used for a Story that is of type StoryTypes.TOC_STORY.

    Proposed solution(s):
    - Add a Stories property to the TOCStyle object that contains references to the Story objects that have that TOCStyle applied.
    - Expose the Story 'AppliedTOCStyle' property via ExtendScipt. This property already exists on the Story IDML object but doesn't appear to be exposed through ExtendScript.

    Thanks for your time!

    Using InDesign Server (or scripts in InDesign Desktop) via JavaScript, it would be very helpful if there was an API/mechanism for discovering details for table of contents usage.

    Current Issue:
    It doesn't look like there is a way to see if a TOCStyle is actually used anywhere. A document can contain multiple TOCStyles, but it's possible only one is placed in the document. Likewise, it doesn't appear there is a way to resolve the TOCStyle being used for a Story that is of type StoryTypes.TOC_STORY.

    Proposed solution(s):
    - Add a Stories property to the TOCStyle object that contains references 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

    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

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

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

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

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

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

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

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