126 results found

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

   Submit Rating

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

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

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

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

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

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

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

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

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

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

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

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

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

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

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Java Script  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

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

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

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

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

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

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

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

   Suggestion: Adobe should either… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Java Script  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. TypeScript Definitions for InDesign UXP

   Do we have an ETA on when we should expect TypeScript Definition files for UXP in InDesign?

   Currently both Photoshop and Premiere Pro have auto-generated types from their respective teams. This is really crucial for UXP adoption and reliable development.

   Also posted in the forums: https://forums.creativeclouddeveloper.com/t/typescript-definitions-for-indesign-uxp/9098

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  UXP plugins  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

   Submit Rating

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

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

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

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

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

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

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

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

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

   That causes the plug-in to crash InDesign.

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

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

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

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

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

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

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

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

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  C++ SDK  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

   Hello Adobe and hello Community,

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

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

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

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

   My Script looks something like this:

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

   In this line I'm getting an error:

   errornumber: 1000

   errorstring: XMP Exception: OpenFile returned false

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

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

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

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

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

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

   Hello Adobe and hello Community,

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

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

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

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Java Script  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Collapse Treeview not working

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

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

   Run Script treeviewexpandcollapse.jsx to test it

   • 

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Java Script  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Bug in IXMLOutStream.h header file

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

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

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

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

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

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  C++ SDK  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   FIXED  ·  AdminRavi Kiran (Admin, Adobe InDesign) responded

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

   —
   Adobe InDesign team

10. InDesign crashes when converting a table

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

    Steps to reproduce:

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

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

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

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

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    4 comments  ·  Java Script  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    FIXED  ·  Abhinav Kaushik responded

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

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

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

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

    -InDesign Team

11. Indesign crash with findGrep()

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

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

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    6 comments  ·  Java Script  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    FIXED  ·  Abhinav Kaushik responded

    Hello All,

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

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

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

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

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

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

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

    The error occurred with version 20.4.1

    ---

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

    this: Object

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

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

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

    •  

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  UXP plugins  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Under Review  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

    Hi,

    Thank you for reporting the issue. We have been able to reproduce the issue and it is currently under investigation. 

    —

    Adobe InDesign Team

13. [ExtendScript/UXP] Position layoutWindow viewport

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

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

    I would much appreciate this addition to Indesign scripting.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Java Script  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. InDesignServer - All Layers are allways unlocked

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

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

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

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

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

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

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

    I've already posted this… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  InDesign Server  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Make the (Black) Color Swatch a TRUE BLACK

    In the Appearance Panel, the (Black) color swatch is not a TRUE BLACK color and when this color swatch is used and a file is exported to PDF, Rich black is not achieved.

    The attached document shows a few shapes that are black. The top right is a true black color and the color swatch had to be changed from the standard (BLACK) color swatch in order to be achieved when exporting to a PDF. The left and bottom color swatches have the (Black) color swatch from the appearance panel applied.

    Please, Please, Please, make the (Black) color swatch a true rich black color (since users cannot adjust this color).

    Since the standard (Black) color swatch isn't true black, it will take me quite a bit of time to apply a new color to all my previously designed files that use your standard (Black) color swatch.

    In the Appearance Panel, the (Black) color swatch is not a TRUE BLACK color and when this color swatch is used and a file is exported to PDF, Rich black is not achieved.

    The attached document shows a few shapes that are black. The top right is a true black color and the color swatch had to be changed from the standard (BLACK) color swatch in order to be achieved when exporting to a PDF. The left and bottom color swatches have the (Black) color swatch from the appearance panel applied.

    Please, Please, Please, make the (Black) color swatch a… more

    •  

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  InDesign Server  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. IDML resources

    On https://www.adobe.com/devnet/indesign/documentation.html site links are not working at the IDML section. Please fix it!

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  InDesign Server  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Need More Info  ·  amaarora responded

    The links are working fine for me.
    Can you recheck once at your end?

    Thanks

17. How to turnoff Type contextual controls in Indesign CC 2018?

    app.typeContextualUiPrefs.showFractionsUi = false;
    don`t work

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Java Script  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. A reference to panel item 25 breaks a script

    There's a rogue panel that breaks InDesign CC2019 when it is referenced (CC2018 is not affected).

    Open InDesign CC2019, then run this one-line script:

    app.panels[25].name

    Result: Error: 'Invalid object for this request'.

    Now do this:

    app.panels[25].isValid

    which returns true.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Java Script  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Under Review  ·  amaarora responded

    Thanks for reporting the issue. We are reviewing it

    -InDesign Team

19. Inner glow size limited to 144pt

    Setting innerGlow size to larger than 144 pt via script causes an error for invalid value outside an expected range of 0-144. However, the UI allows size up to be over 13 inches. I have not tested all the other effects, but I believe this is the case for inner shadow and feather as well.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Java Script  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. CC2019: Can't update or relink a link when a document is opened by a script.

    A fault introduced in CC2019: can't update or relink a link when a document is opened by a script.

    Steps to reproduce:

    1. To verify that with an existing open document the problem does not occur: a. Start a new InDesign document b. Place a graphic on the first page c. Run this script:

    app.documents[0].links[0].update();

    No error occurs.

    1. To reproduce the error: a. Save the document created in step 1 and close it. b. Run this script:

    s = '/d/test/links.indd'; // Use your string
    app.open (File(s));
    app.documents[0].links[0].update();

    Expected result: The links should be updated.
    Actual result: "Error: This file is already open by another user or another application. This file may be stored on a network server and cannot be opened until the other user closes it."

    Note 1: It doesn't matter that in this example the link doesn't actually need updating. The result is the same with out-of-date links.

    Note 2: The problem is not confined to update(): it also occurs when you relink a link.

    A fault introduced in CC2019: can't update or relink a link when a document is opened by a script.

    Steps to reproduce:

    1. To verify that with an existing open document the problem does not occur: a. Start a new InDesign document b. Place a graphic on the first page c. Run this script:

    app.documents[0].links[0].update();

    No error occurs.

    1. To reproduce the error: a. Save the document created in step 1 and close it. b. Run this script:

    s = '/d/test/links.indd'; // Use your string
    app.open (File(s));
    app.documents[0].links[0].update();

    Expected result: The links should be updated.
    Actual result: "Error: This file is already… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    4 comments  ·  Java Script  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Need More Info  ·  amaarora responded

    Hi,
    Please can you provide some more information related to the issue?
    1. OS
    2. Document and imported file location (local or network)
    3. File system type
    4. Can you share a sample document along with the imported file.
    5. Is the issue reproducible in ID 2020?
    6. A small video will help as well

    Thanks
    amaarora@adobe.com