8 results found

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

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

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

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

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

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

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

   Thanks for reporting the issue. We are reviewing it

   -InDesign Team

8. nextItem() doesn't work

   Instructions:

   1. Load Script4.txt into ExtendScript CC
   2. Open ID CC 2019
   3. Connect ExtendScript CC to ID CC 2019
   4. Run the script
   5. Observe that line 8 gives an "Object is invalid" error. That's because the nextItem() on line 6 didn't work.

   To see this more clearly:

   1. Load Script4.txt into ExtendScript CC
   2. Open ID CC 2019
   3. Connect ExtendScript CC to ID CC 2019
   4. Comment line 6 and uncomment line 7.
   5. Run the script
   6. The script runs fine. It prints out "2", the name of the second page.

   In other words, nextItem() is broken. The work around (in this case) is to use an index of "Page_263.index+1". I think, in other situations, the work around will require a loop.

   Instructions:

   1. Load Script4.txt into ExtendScript CC
   2. Open ID CC 2019
   3. Connect ExtendScript CC to ID CC 2019
   4. Run the script
   5. Observe that line 8 gives an "Object is invalid" error. That's because the nextItem() on line 6 didn't work.

   To see this more clearly:

   1. Load Script4.txt into ExtendScript CC
   2. Open ID CC 2019
   3. Connect ExtendScript CC to ID CC 2019
   4. Comment line 6 and uncomment line 7.
   5. Run the script
   6. The script runs fine. It prints out "2", the name of the second page.

   In other words, nextItem() is broken. The work around (in this case) is to use an… more

   • 

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Java Script  ·  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  ·  AdminRavi Kiran (Senior Lead Quality Engineer, Adobe InDesign) responded

   We’re reviewing this issue.

   —
   Adobe InDesign team