61 results found

1. InDesign: Insert authors document's metadata without quotes

   Version
   Adobe InDesign up to 2023.

   Steps to reproduce the issues
   Setting the active document’s metadataPreferences.author with multiple authors, separated by comma or semicolon in a string via extendscript:
   
app.activeDocument.metadataPreferences.author = "Elric Wade; Anne Emu; Sophie Kumpir";


   Expected result
   The authors should be placed into the "Author" metadata field, separated by comma or semicolon.

   Actual result
   The authors are placed into the "Author" metadata field, but all set within double quotes, so they appear to be one author, not multiple authors.

   Test file, screenshot, video or GIF capturing the issue (optional)
   See attached screenshot.

   Please make it possible to add multiple authors (e.g. with not quoting comma or semicolon separated strings, or by letting pass-in an array with names).

   Version
   Adobe InDesign up to 2023.

   Steps to reproduce the issues
   Setting the active document’s metadataPreferences.author with multiple authors, separated by comma or semicolon in a string via extendscript:
   
app.activeDocument.metadataPreferences.author = "Elric Wade; Anne Emu; Sophie Kumpir";


   Expected result
   The authors should be placed into the "Author" metadata field, separated by comma or semicolon.

   Actual result
   The authors are placed into the "Author" metadata field, but all set within double quotes, so they appear to be one author, not multiple authors.

   Test file, screenshot, video or GIF capturing the issue (optional)
   See attached screenshot.

   Please make it possible to add… more

   •  

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Scripting  ·  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. matchPreviewBackgroundToThemeColor resets pasteboardMargins to [0,0]

   In a script, app.activeDocument.pasteboardPreferences.matchPreviewBackgroundToThemeColor to 1 causes app.activeDocument.pasteboardPreferences.pasteboardMargins to reset to [0,0].

   Furthermore, setting the pasteboardMargins doesn't work after setting app.activeDocument.pasteboardPreferences.matchPreviewBackgroundToThemeColor to 1.

   (While matchPreviewBackgroundToThemeColor is set to 0 everything works fine.)

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Scripting  ·  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. Cell object is null!

   I get the third merged cell as null. Why is that?

   Please to get the error First create new document and table 3 by 3 and merge and select cells like screenshot. Execute the script.

   var sel = app.selection[0];
   var queuedCells = getQueuedCells ([sel]);
   function getQueuedCells (deepCells) {
   var queuedCells = new Array;
   if (deepCells.length > 0) {
   targetIndex = null;
   targetIndex = deepCells[0].parentRow.index;
   for (var dcs = 0; dcs < deepCells.length; dcs++) {
   for (var dcc = 0; dcc < deepCells[dcs].cells.length; dcc++) {
   alert ("(deepCells[" + dcs + "].cells[" + dcc + "] != null) " + (deepCells[dcs].cells[dcc] != null));
   if (targetIndex == deepCells[dcs].cells[dcc].parentRow.index) {
   queuedCells.push (deepCells[dcs].cells[dcc]);
   }
   }
   }
   }
   return queuedCells;
   }

   I get the third merged cell as null. Why is that?

   Please to get the error First create new document and table 3 by 3 and merge and select cells like screenshot. Execute the script.

   var sel = app.selection[0];
   var queuedCells = getQueuedCells ([sel]);
   function getQueuedCells (deepCells) {
   var queuedCells = new Array;
   if (deepCells.length > 0) {
   targetIndex = null;
   targetIndex = deepCells[0].parentRow.index;
   for (var dcs = 0; dcs < deepCells.length; dcs++) {
   for (var dcc = 0; dcc < deepCells[dcs].cells.length; dcc++) {
   alert ("(deepCells[" + dcs + "].cells[" + dcc + "] != null) " + (deepCells[dcs].cells[dcc] !=… more

   •  

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Scripting  ·  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. Convert Footnotes and Endnotes problem and a bonus scripting problem with special characters

   Indesign 17 on MacOs 12.3.1

   Convert Footnotes and Endnotes does not work when the footnotes does not have a footnote number.

   I have an Indesign document with footnotes.
   In each footnote I have removed the footnote number and the following tab character. (~F\t)

   I need these footnotes to be endnotes but this is not possible with the command "Convert Footnotes and Endnotes".

   Without the footnote number in the footnotes the command/script does not recognise the footnotes as being footnotes.

   They are however still footnotes and I can continue working with them as footnotes and also address them via scripting but the command "Convert Footnotes and Endnotes" does not work.

   I can reinsert a footnote number in each of the footnotes manually one by one by going through "Special Characters > Markers > Footnote Number.

   This will make the conversion work but this should not be necessary.

   Now to the bonus problem:

   I figured I could simply iterate the footnotes and insert the footnote number with a simple script. Guess what? Not that simple.

   I can insert everything except for the SpecialCharacters.FOOTNOTE_SYMBOL in the footnotes.
   Looking at the undo menu it appears as if indesign thinks it has inserted something as it says: "Undo Insert Text"
   But nothing was inserted.

   So ... I guess that I have two bugs here.

   Please help.

   Indesign 17 on MacOs 12.3.1

   Convert Footnotes and Endnotes does not work when the footnotes does not have a footnote number.

   I have an Indesign document with footnotes.
   In each footnote I have removed the footnote number and the following tab character. (~F\t)

   I need these footnotes to be endnotes but this is not possible with the command "Convert Footnotes and Endnotes".

   Without the footnote number in the footnotes the command/script does not recognise the footnotes as being footnotes.

   They are however still footnotes and I can continue working with them as footnotes and also address them via scripting but… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Scripting  ·  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. anchoredObjectSettings SpaceBelow is missing in the DOM

   The space below is missing for anchored Object Settings

   I can only find this:
   anchoredObjectSettings.anchorSpaceAbove

   (INDD17.1 + Javascript)

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Scripting  ·  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. InDesign does not load type library on upgrade

   Similar to the 2020 release (see https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/41072476-type-library-is-not-automatically-created-by-cc202), InDesign 2022 does not install the type library in upgrade. Please include this with the installation, as this will cause errors for many users.

   Error message: Error: Unable to load Adobe InDesign 2022 Type Library (Version 1.0).

   •  

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Scripting  ·  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. script panel blank

   Nenhum Script aparece no painel. Todos sumiram, e todos os scripts estão na pasta do ID.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Scripting  ·  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. export layers to photoshop

   would be so nice to have a way to export inDesign layers to Photoshop file. (would save hundreds of hours to rebuild all these files!)

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Scripting  ·  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. FindChangeByList not working

   1 The script stopped working. Doesn’t do anything.

   2 Please let the updater copy the FindChangeList.txt from the previous version. In most cases it’s part of a workflow that breaks with each update.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Scripting  ·  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

10. [ID-4273762] Critical bug — Dropdown / <select> / sp-picker not working in UXP plugin under InDesign 2025 (Win & Mac)

    I'm contacting you about a recurring bug I've encountered—and that several other developers have reported—since the Adobe InDesign 2025 update (versions 20.4, 20.4.1, 20.5).

    🔹 Problem Description

    • In a plugin using Adobe UXP (UI HTML or Spectrum), the dropdown elements <select>—or <sp-picker>—no longer respond to clicks: the border may change color, but the list doesn't open, and it's impossible to select an item.

    • Even when using minimal HTML code or testing from UXP Developer Tools (Playground), the problem persists.

    • This bug seems to affect several environments (Windows 11, different versions of InDesign, and possibly macOS as well, according to community feedback).

    • In some cases, events (click, change, keydown, etc.) are no longer emitted for form controls.
      Adobe Creative Cloud Developer Forums

    🔹 Impact

    Existing plugins become unusable — users are unable to enter or select options, thus blocking normal operation.

    Production usage is severely disrupted.

    Loss of confidence in the stability of the UXP runtime.

    🔹 Step to reproduce

    1 - Create starter package
    2 - Add select with options tags
    3 - Use UXP Developer tools or package it
    4 - Open panel in Indesign 2025
    - under 20.4 version, it works fine. We can open option in select
    - upper 20.3 version, select tags, checkbox,... doesn't work

    🔹 What I'm asking

    Can you confirm that this bug has been identified internally?

    Is there a planned fix (future version or update) to restore the behavior of dropdown lists/sp-picker/select in UXP under InDesign 2025?

    If not, is it possible to obtain an official workaround (patch, beta build, directive) for our plugins in production?

    Thank you in advance for your help—this bug seriously compromises the reliability of UXP plugins. I am available to provide code examples, reproductions, or logs if that would be helpful.

    Sincerely,
    Stéphane Senocq

    I'm contacting you about a recurring bug I've encountered—and that several other developers have reported—since the Adobe InDesign 2025 update (versions 20.4, 20.4.1, 20.5).

    🔹 Problem Description

    • In a plugin using Adobe UXP (UI HTML or Spectrum), the dropdown elements <select>—or <sp-picker>—no longer respond to clicks: the border may change color, but the list doesn't open, and it's impossible to select an item.

    • Even when using minimal HTML code or testing from UXP Developer Tools (Playground), the problem persists.

    • This bug seems to affect several environments (Windows 11, different versions of InDesign, and possibly macOS as well, according… 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

    Under Review  ·  3 comments  ·  Scripting  ·  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

11. Error Number: 30619

    When opening InDesign GA 21.0 I am now getting this pop message. I do not get the same thing in Beta version

    •  

    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

    1 comment  ·  Scripting  ·  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
    Resolved For User  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

    Hi,

    As confirmed by the user, the issue is resolved by removing second scrollframe folder

    —

    Adobe InDesign Team

    
    

12. Title: `afterSelectionChanged` triggers "The object no longer exists" error even when a valid object is selected Description: When using th

    Title:
    afterSelectionChanged triggers "The object no longer exists" error even when a valid object is selected

    Description:
    When using the method addEventListener("afterSelectionChanged", ...) in an ExtendScript script for InDesign, the application consistently throws the following error:

    "The requested action could not be completed because the object no longer exists."

    This occurs even when:
    - A single TextFrame is manually selected,
    - The object is valid (isValid === true),
    - The code is wrapped in a try/catch,
    - An idleTask is used to defer execution.

    Steps to Reproduce:
    1. Open an InDesign document.
    2. Add the following script:

    function onSelectionChanged(event) {
    try {
    if (app.selection.length > 0 && app.selection[0].isValid) {
    alert("Selected: " + app.selection[0].constructor.name);
    }
    } catch (e) {
    alert("Error: " + e.message);
    }
    }

    app.addEventListener("afterSelectionChanged", onSelectionChanged);

    1. Select a TextFrame on the page.

    Expected Result:
    The script should display the type of the selected object without error.

    Actual Result:
    An error message appears immediately:
    "The requested action could not be completed because the object no longer exists."

    System Information:
    - InDesign Version: 20.4.1
    - OS: macOS 15.3.2
    - Language: French
    - Script executed from: Scripts Panel

    Comment:
    This behavior prevents reliable use of afterSelectionChanged for interacting with the selection. It appears that the event is triggered before the selection is fully stabilized, making app.selection[0] unusable.

    Title:
    afterSelectionChanged triggers "The object no longer exists" error even when a valid object is selected

    Description:
    When using the method addEventListener("afterSelectionChanged", ...) in an ExtendScript script for InDesign, the application consistently throws the following error:

    "The requested action could not be completed because the object no longer exists."

    This occurs even when:
    - A single TextFrame is manually selected,
    - The object is valid (isValid === true),
    - The code is wrapped in a try/catch,
    - An idleTask is used to defer execution.

    Steps to Reproduce:
    1. Open an InDesign document.
    2. Add the following script:

    … 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  ·  Scripting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. [ID-4260022][ExtendScript] Folder.prototype.create fails on macOS/InDesign 20.1

    Something has broken in ExtendScript's Folder.prototype.create method on MacOS and Indesign 20.1.

    To test yourself, save the following script to your disk, and run it in Indesign.

    
    (function () {
    
        var scriptFolder = File($.fileName).parent;
        var deepFolder = Folder(scriptFolder + '/A/B/C/D');
    
        if (!deepFolder.exists)
            deepFolder.create();
    
        if (deepFolder.exists) {
            alert('Folder created successfully.');
        }
        else {
            alert('Failed to create folder "' + deepFolder.fsName + '".');
        }
    
    })();
    
    

    Expected Result:
    Prior to this bug, this script would successfully create the folder and subfolders, in the same folder as the script is saved.

    Actual Result:
    Each time the script is run, it creates only one more level of sub folder. So the first time run it creates folder "A", then the next time run it creates "B" etc.

    See also this thread on the forum.

    Something has broken in ExtendScript's Folder.prototype.create method on MacOS and Indesign 20.1.

    To test yourself, save the following script to your disk, and run it in Indesign.

    
    (function () {
    
        var scriptFolder = File($.fileName).parent;
        var deepFolder = Folder(scriptFolder + '/A/B/C/D');
    
        if (!deepFolder.exists)
            deepFolder.create();
    
        if (deepFolder.exists) {
            alert('Folder created successfully.');
        }
        else {
            alert('Failed to create folder "' + deepFolder.fsName + '".');
        }
    
    })();
    
    

    Expected Result:
    Prior to this bug, this script would successfully create the folder and subfolders, in the same folder as the script is saved.

    Actual Result:
    Each time the script is run, it creates only one more… 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

    1 comment  ·  Scripting  ·  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

    Fix for this issue is available in the latest InDesign Release version 20.2, available via Adobe CCD app.

    
    

    --

    Adobe InDesign team

14. Dropshadow > Size is limited to 0-144 points within scripting but you can enter higher numbers manually 0-1000 points

    My understanding is indesign dropshadow effect needs to be updated for the option: size within the dropshadow panel to be able to accept 0 - 1000 points for scripts. You can input higher numbers within the size by doing it manually but not with scripts for whatever reason. It will only accepts 0-144 point or 2 inches within the code.

    1. Indesign CC 2025
    2. Run the attached script a 100 in height image and you'll get the error.
    3. On the dropshadow applied to have the distance 5.0 in and size 5.0
    4. Distance: 5.0 in and Size: 0.0694 in
    5. Script attached.

    I have a script to automatically apply dropshadows and we have a formula where we take the height of the image and multiply that by 5% which gets placed in the Distance and Size. This works for smaller images but when there are larger images the number it puts into the distance works but the size seems to be limited to 2 inches. But if I do it manually it can go up to 13.8889″
    for the size

    I get this error: ERROR in applyDropShadow: Error: Invalid value for set property ‘size’. Expected Unit (0 - 144 points), but received “5.0 in”. 13.8889 in = 1000 points

    //@target "indesign"
    //@targetengine "session"

    function isValidObject(obj) {
    try {
    return obj && obj.isValid;
    } catch (e) {
    return false;
    }
    }

    function applyDropShadowByHeightInInches(obj) {
    if (!isValidObject(obj)) return;

    var doc = app.activeDocument;
    var originalH = doc.viewPreferences.horizontalMeasurementUnits;
    var originalV = doc.viewPreferences.verticalMeasurementUnits;
    
    try {
        // Switch the document to inches.
        doc.viewPreferences.horizontalMeasurementUnits = MeasurementUnits.INCHES;
        doc.viewPreferences.verticalMeasurementUnits   = MeasurementUnits.INCHES;
    
        // geometricBounds => [y1, x1, y2, x2] in INCHES now.
        var bounds = obj.geometricBounds; 
        var heightInches = Math.abs(bounds[2] - bounds[0]); // bottom - top
    
        // 5% of height in inches
        var dropShadowInches = heightInches * 0.05;
    
        // Apply the drop shadow
        var ds = obj.transparencySettings.dropShadowSettings;
        ds.mode     = ShadowMode.DROP;
        ds.angle    = 120;                 // Static angle
        ds.distance = dropShadowInches;    // in inches
        ds.size     = dropShadowInches;    // same as distance
        ds.opacity  = 35;                  // example opacity
        ds.noise    = 2.5;                 // example noise %
        ds.xOffset  = 0;
        ds.yOffset  = 0;
        ds.spread   = 0;
    
    } catch (e) {
        $.writeln("Error applying shadow: " + e);
    } finally {
        // Restore original measurement units
        doc.viewPreferences.horizontalMeasurementUnits = originalH;
        doc.viewPreferences.verticalMeasurementUnits   = originalV;
    }
    

    }

    function main() {
    if (app.documents.length === 0) {
    alert("No open documents.");
    return;
    }

    var doc = app.activeDocument;
    if (!isValidObject(doc)) {
        alert("Active document not valid.");
        return;
    }
    if (app.selection.length === 0) {
        alert("No objects selected.");
        return;
    }
    
    var count = 0;
    for (var i = 0; i < app.selection.length; i++) {
        var obj = app.selection[i];
        if (isValidObject(obj)) {
            applyDropShadowByHeightInInches(obj);
            count++;
        }
    }
    alert("Drop shadow applied to " + count + " object(s).");
    

    }

    main();

    My understanding is indesign dropshadow effect needs to be updated for the option: size within the dropshadow panel to be able to accept 0 - 1000 points for scripts. You can input higher numbers within the size by doing it manually but not with scripts for whatever reason. It will only accepts 0-144 point or 2 inches within the code.

    1. Indesign CC 2025
    2. Run the attached script a 100 in height image and you'll get the error.
    3. On the dropshadow applied to have the distance 5.0 in and size 5.0
    4. Distance: 5.0 in and Size: 0.0694 in
    5. Script attached.

    I… 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  ·  Scripting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. do script bug in indesign 2025?

    I have a script (extend script) file that has worked flawlessly in every version of InDesign for the last 15 years or so. Bercause it is used in semi-automated workflow I trigger it from an AppleScript, using the "do script" command.

    InDesign 2025 suddenly incorrectly reports a syntax error "expecting ;"

    The javascript that gets called works as expected, without warnings when run from the script panel.

    This is highly problematic for me, since triggering the script from applescript is an essential part of my workflow.

    Adobe are welcome to contact me for more information

    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  ·  Scripting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Scripting Windows: Add page item after add swatch will delete added swatch

    In ExtendScript on Windows only, adding any InDesign page item after adding a color will delete the color:
    
var doc = app.documents.add();
// adds black CMYK color
sw = doc.colors.add();
// this line will delete the color that was just added on Windows only
var rect = doc.rectangles.add();
alert(sw.isValid);


    This actually manifested for me as a crash bug. This script crashes InDesign 2024 Windows:

    var doc = app.documents.add();
    var sw = doc.colors.add();
    doc.rectangles.add({fillColor: sw});
    

    This crashes because the last line deletes the swatch when it adds the rectangle, then tries to use the swatch.

    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  ·  Scripting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. PlaceGun does not have reference to idms textframe

    Hi,

    I'm trying to place a textframe from an idms file into an indesign document. The actual loadPlaceGun() operation seems to work fine as I'm able to paste the textframe on the page. However, I also want to have a reference to that textframe. I was trying to accomplish this by using

    placeGun.pageItems.everyItem().getElements(), but it doesn't return any elements. I find this odd because I'm using the same method when inserting images and it works fine, so I'm not sure what the issue is. Link with pictures here: https://community.adobe.com/t5/indesign-discussions/placegun-does-not-have-reference-to-idms-textframe/m-p/14530065#M568624

    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  ·  Scripting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. hyperlinkTextSources.add thrown Errornumber 79111 since InDesign 2024

    When creating hyperlinks, a hyperlink is automatically created via a text object. The script ran until InDesign 2023.
    The text objects are returned by a search.

    app.activeDocument.findGrep();

    The hyperlink was created with the steps
    hyperlinkTextSources.add
    hyperlinkURLDestinations.add
    hyperlinks.add

    The first hyperlink is created as expected. In InDesign 2024, error 79111 "The selected object is already being used by another hyperlink" is thrown after the first hyperlink created (hyperlinkTextSources.add).

    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  ·  Scripting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. action feature

    hello, Is there an action feature in InDesign, like Photoshop?
    Is there a script that records the work steps and then applies the steps automatically when clicked?

    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  ·  Scripting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Insertion point with more than one text style range

    An insertion point can have more than one TextStyleRange, e.g.

    InsertionPoint.textStyleRanges.length // Result: 779

    These are the TextStyleRanges of the entire text (of the story) that follows the insertion point.

    Expected is one TextStyleRange for one InsertionPoint.

    InDesign 18.5.1, MacOS, UXP and ExtendScript

    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  ·  Scripting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating