83 results found

1. Incorrect word count via script

   At some point (I think v27) Illustrator has changed its word counting/division algorithm.

   So, where previously the results were sensible:
   "This.Was.Four.Words" — word count: 4
   "This.Is.3.Words" — word count: 4
   "I.WF05f.07.AB.000" — word count: 5
   "I.WF05f.AB.07.000" — word count: 5

   In version 27.4 the results are now confused:
   "This.Was.Four.Words" — word count: 1
   "This.Is.3.Words" — word count: 3
   "I.WF05f.07.AB.000" — word count: 4
   "I.WF05f.AB.07.000" — word count: 2

   For a discussion on the topic, and a testing script, see this thread.

   Note: maybe this bug was introduced while fixing this bug.

   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

   1 comment  ·  SDK and 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

2. Scripting window keeps appearing and no way to remove it

   Uninstalling/Reinstalling does not remove prompt. Starting appearing after most recent update to with the new ipad features. Going back to older version, the window doesn't appear.

   •  

   •  

   •  

   •  

   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

   7 comments  ·  SDK and 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
   Under Review  ·  AdminRama (Mgr, Software Development, Adobe Illustrator) responded

   This issue is happening due to a security feature added in Illustrator to inform the user if any external application tries to execute a script in Illustrator.

   Solution: Update your Logitech options app to the latest version – https://www.logitech.com/en-in/product/options

   https://helpx.adobe.com/illustrator/kb/fix-scripting-error.html

   We heard from some users that above solution is not working for them, we are investigating this issue. Meanwhile users can try the below workaround

   Create a JSX file with the following content:
   app.preferences.setBooleanPreference(“ShowExternalJSXWarning”, false);
   Save the above JSX file. Now, go to File > Scripts > Other Script, and choose the newly saved jsx file.

   This will suppress the warning dialog and run the script.

3. Bug: exporting SVG's via exportFile(fileObjSingle, ExportType.SVG, svgOptions). has completely changed since 28.4

   (macOS & Windows, latest versions) Beginning with Illustrator 28.4, SVG files exported via Javascript are in a very different format.

   The following examples are exported with:

   doc.exportFile(fileObjSingle, ExportType.SVG, svgOptions);

   The SVG option for the format of the SVG is STYLEELEMENTS.

   See attached captures for the differences.

   There are many many changes:

   • the style definitions are handled differently
   • ID's now strip out characters like / or < instead of replacing them with entities
   • the original names are included via data-name tags
   • the comment from the 2nd line is now gone
   • clipping paths are handled differently

   I have built a complex program over many years that depends on special characters in the SVG ID's, and it is now completely broken.

   Does anyone know how to get back the previous SVG export format?

   Does anyone know if this is a bug that will be fixed?

   (macOS & Windows, latest versions) Beginning with Illustrator 28.4, SVG files exported via Javascript are in a very different format.

   The following examples are exported with:

   doc.exportFile(fileObjSingle, ExportType.SVG, svgOptions);

   The SVG option for the format of the SVG is STYLEELEMENTS.

   See attached captures for the differences.

   There are many many changes:

   • the style definitions are handled differently
   • ID's now strip out characters like / or < instead of replacing them with entities
   • the original names are included via data-name tags
   • the comment from the 2nd line is now gone
   • clipping paths are handled differently

   I have built a complex program… 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

   3 comments  ·  SDK and 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

4. Plugins Disappeared

   after updating to version 25.1
   the plugins in the "plugins folder"
   don't Load up
   when downgrade back to version 25.0.1
   Its work fine

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

5. Failure to create artboards when reading file with SDK in CC 2018

   Issue occurs in CC 2018 when creating artboards during the GoFileFormat message handler in a plugin that registers its own file format.

   In previous versions you could create artboards up to the size of the canvas using AIArtboard::SetPosition without any errors. In CC 2018 when you call AIArtboard::SetPosition it seems to compare the position to the result of AIDocument::GetDocumentMaxArtboardBounds and if it is outside of the maximum bounds it returns an error code. In CC 2018, the maximum art boards for a new document seem to be based on the /artboard setting in the preferences file, which in turn seems to be based on the documents the user has been working with.

   This means that if you have two users, one who uses small documents and one who uses large documents and they both open the same medium size file using your plugin, it works for the user who has been using large documents but not for the user who has been using small documents. As there is no AIDocument::SetDocumentMaxArtboardBounds function, there seems to be no way the plugin can overcome this issue.

   Issue occurs in CC 2018 when creating artboards during the GoFileFormat message handler in a plugin that registers its own file format.

   In previous versions you could create artboards up to the size of the canvas using AIArtboard::SetPosition without any errors. In CC 2018 when you call AIArtboard::SetPosition it seems to compare the position to the result of AIDocument::GetDocumentMaxArtboardBounds and if it is outside of the maximum bounds it returns an error code. In CC 2018, the maximum art boards for a new document seem to be based on the /artboard setting in the preferences file, which in turn seems… 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

   10 comments  ·  SDK and 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

6. [ExtendScript] PageItem.resize doesn't scale Live Paint strokes

   While scaling Live Paint object correctly scales strokes if done via the UI, it fails to scale strokes if done via the PageItem.resize method in the scripting API.

   MacOS 15.0.1 Illustrator 29.0.

   Steps to reproduce:
   1. New document
   2. Create a Live Paint object including stroked areas.
   3. Select the Live Paint object.
   4. Run the following script:

   var item = app.activeDocument.selection[0];
   item.resize(200, 200, true, true, true, true);
   

   Expected result is that the Live Paint object's stroke widths would double. However they remain the same as before.

   See this user post.

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

7. [ExtendScript] Cannot change `underline` value of some text ranges.

   We cannot successfully set characterAttribute.underline to false in some textRanges.

   (MacOS 15.0 Adobe Illustrator 28.7.1)

   Steps to reproduce:
   1. New document
   2. Make a text frame with contents "ab"
   3. Set the "b" to a different fontStyle, eg. "italic"
   4. Run the below script, and check the console output.

   Expected Result: all tests PASSED, meaning that the underline can be set to true and then to false successfully.

   Actual result, test B on the "b" fails.

   Script:
   ```
   (function () {

   var doc = app.activeDocument,
       tf = doc.textFrames[0];
   
   var results = ['Results:'];
   
   tf.textRanges[0].characterAttributes.underline = true
   results.push('textRanges[0] test A: ' + (true === tf.textRanges[0].characterAttributes.underline ? 'PASSED' : 'FAILED'));
   
   tf.textRanges[0].characterAttributes.underline = false;
   results.push('textRanges[0] test B: ' + (false === tf.textRanges[0].characterAttributes.underline ? 'PASSED' : 'FAILED'));
   
   tf.textRanges[1].characterAttributes.underline = true;
   results.push('textRanges[1] test A: ' + (true === tf.textRanges[1].characterAttributes.underline ? 'PASSED' : 'FAILED'));
   
   tf.textRanges[1].characterAttributes.underline = false;
   results.push('textRanges[1] test B: ' + (false === tf.textRanges[1].characterAttributes.underline ? 'PASSED' : 'FAILED'));
   
   alert(results.join('\n'));
   

   })();
   ```

   See this community forum post.

   Update: User sttk3 discovered that the bug is actually that Illustrator ignores an attempt to set a characterAtrribute property if the value is the same as the applied character style's value for the same attribute.

   We cannot successfully set characterAttribute.underline to false in some textRanges.

   (MacOS 15.0 Adobe Illustrator 28.7.1)

   Steps to reproduce:
   1. New document
   2. Make a text frame with contents "ab"
   3. Set the "b" to a different fontStyle, eg. "italic"
   4. Run the below script, and check the console output.

   Expected Result: all tests PASSED, meaning that the underline can be set to true and then to false successfully.

   Actual result, test B on the "b" fails.

   Script:
   ```
   (function () {

   var doc = app.activeDocument,
       tf = doc.textFrames[0];
   
   var results = ['Results:'];
   
   tf.textRanges[0].characterAttributes.underline = true
   results.push('textRanges[0] test A: ' +

   … 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  ·  SDK and 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

8. [ExtendScript] Line feed \u000A character assigned to text contents is converted to carriage return

   MacOS 13.3.1, Adobe Illustrator 27.4.1
   Also reported on Windows same version of Illustrator.

   Steps to reproduce.
   To see problem, run this script
   ```
   (function () {

   var doc = app.documents.add();
   
   var tf1 = doc.textFrames.add();
   tf1.position = [100, 100];
   tf1.contents = 'Break\u000Ame.';
   alert('Linefeed (10)\n charCode = ' + tf1.contents.charCodeAt(5));
   
   var tf2 = doc.textFrames.add();
   tf2.position = [200, 100];
   tf2.contents = 'Break\u0003me.';
   alert('End-of-text (3)\n charCode = ' + tf2.contents.charCodeAt(5));
   

   })();
   ```
   I would expect the text on the left to have a line feed (u+000A) character, but it is converted to a carriage return (u+000D).
   The text on the right is a workaround, using an unexpected character (u+0003).

   There is a discussion here.

   This silent conversion is unexpected, and never wanted by the user (the scripter).

   MacOS 13.3.1, Adobe Illustrator 27.4.1
   Also reported on Windows same version of Illustrator.

   Steps to reproduce.
   To see problem, run this script
   ```
   (function () {

   var doc = app.documents.add();
   
   var tf1 = doc.textFrames.add();
   tf1.position = [100, 100];
   tf1.contents = 'Break\u000Ame.';
   alert('Linefeed (10)\n charCode = ' + tf1.contents.charCodeAt(5));
   
   var tf2 = doc.textFrames.add();
   tf2.position = [200, 100];
   tf2.contents = 'Break\u0003me.';
   alert('End-of-text (3)\n charCode = ' + tf2.contents.charCodeAt(5));
   

   })();
   ```
   I would expect the text on the left to have a line feed (u+000A) character, but it is converted to a carriage return (u+000D).
   The text on the right is a workaround,… 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  ·  SDK and 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

9. IUStringUnitsToAIReal doesn't recognize comma as decimal separator

   std::string input_ = "1,5"; // From Adobe header: The string to convert, which uses the localized international utilities (IU) decimal separator.
   AIReal n;
   sAIUser->IUStringUnitsToAIReal(ai::UnicodeString(input_), &n);

   This function interprets the text "1,5" as "15" even when the locale is set to a country where the system uses a comma decimal separator. Related functions IUStringToAIReal recognizes the comma, though.

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

10. AIPaintStyleSuite not found

    Trying to update a plugin to use the Illustrator 2020 SDK on Mac. Previously using the 2017 SDK. The SPBasicSuite AcquireSuite function fails to find the AIPaintStyleSuite when building with the 2020 SDK.

    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

    3 comments  ·  SDK and 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

11. GetPresetSettings function doesn't work correctly in CC 2017 and later

    In Illustrator CC 2017 (22.x) and CC 2018 (23.x) the AIDocumentList::GetPresetSettings function is broken. It still returns an error if the preset doesn't exist, but if the preset does exist, it returns 0, but doesn't fill in the AINewDocumentPreset structure.

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

12. [ExtendScript] Cannot set Document.rulerUnits

    There is no way via scripting to set a document's rulerUnits (pts, mm, inch, etc) because the property Document.rulerUnits is—erroneously, surely—read only.

    If Document.rulerUnits was writable, we would simply do this:

      var doc = app.activeDocument;
      doc.rulerUnits = RulerUnits.MILLIMETERS;
    

    This is important because there is literally no way to set this via script, except to create a new document.

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

13. app.preferences.setIntegerPreference() does not work

    app.preferences.setIntegerPreference("rulerType", 0) changes the selection in the GUI but doesn't actually apply the change to the document.

    I still have to go into the GUI preferences, change the units to something else, then back to inches and close for the change to actually apply to the current document.

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

14. [ExtendScript] Incorrect paragraph count when linefeeds are used.

    MacOS 13.3.1, Adobe Illustrator 27.4.1

    To see the issue, run this script:
    ```
    (function () {

    var doc = app.documents.add();
    
    var tf1 = doc.textFrames.add();
    tf1.position = [100, 100];
    tf1.contents = 'Paragraph one\u000DParagraph two';
    
    var tf2 = doc.textFrames.add();
    tf2.position = [200, 100];
    tf2.contents = 'Paragraph one\u0003still paragraph one';
    alert('Paragraph counts\n2 paragraphs: ' + tf1.paragraphs.length + '\n1 paragraphs with forced line break:\n ' + tf2.paragraphs.length);
    

    })();
    ```

    I expect the left text frame to have 2 paragraphs and the right text frame to have 1 paragraph, but the right text frame is incorrectly shown to have 2 paragraphs.

    This discussion revolves around this issue.

    Also, because the issue relates to conflating U+000A and U+000D, this bug may be implicated in this bug, this bug and this bug.

    MacOS 13.3.1, Adobe Illustrator 27.4.1

    To see the issue, run this script:
    ```
    (function () {

    var doc = app.documents.add();
    
    var tf1 = doc.textFrames.add();
    tf1.position = [100, 100];
    tf1.contents = 'Paragraph one\u000DParagraph two';
    
    var tf2 = doc.textFrames.add();
    tf2.position = [200, 100];
    tf2.contents = 'Paragraph one\u0003still paragraph one';
    alert('Paragraph counts\n2 paragraphs: ' + tf1.paragraphs.length + '\n1 paragraphs with forced line break:\n ' + tf2.paragraphs.length);
    

    })();
    ```

    I expect the left text frame to have 2 paragraphs and the right text frame to have 1 paragraph, but the right text frame is incorrectly shown to have 2 paragraphs.

    This discussion revolves around… 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  ·  SDK and 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

15. SVG Export for ExportOptionsSVG does "Save As" and not an "Export As"

    There is no true option for the File -> Export -> Export As for an SVG, doing app.activeDocument.exportFile( fileSpec, 'SVG', exportOptions ) is actually running the equivalent of File -> Save As SVG... Which produces an AI compatible type SVG but not a fully compatible SVG with other programs.

    It'd be nice to have a true "ExportOptionsCompatibleSVG"

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

16. ExtendscriptToolkit is 32bit-only, OSX Catalina is 64bit-only

    I use a script I wrote for an important business function. For the last couple OSX upgrades, it has been warning me that ExtendscriptToolkit is not compatible with future versions of the OS. Specifically, OSX Catalina, which has been seeded to developers, will only support 64bit applications, and ExtendscriptToolkit is a 32bit application. Is that going to be addressed before the OS is released?

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

17. IllustratorSaveOptions in C# .NET is not working anymore as expected

    For more than a decade the following Illustrator script has been applied via C# .NET in combination with all existing Illustrator versions (sourcecode):

    typelib.IllustratorSaveOptions saveOptions = new typelib.IllustratorSaveOptions();
    saveOptions.Compatibility = typelib.AiCompatibility.aiIllustrator8;
    saveOptions.FlattenOutput = typelib.AiOutputFlattening.aiPreserveAppearance;
    DestDoc.SaveAs(sPath, saveOptions);

    All over the internet we see a lot of people using the same code above (applying the exact same idea) also in other programming languages.

    Following test has been done with Illustrator versions CS, CS2, CS3, CS5, CS6, etc. on the latest Windows 10 operating system and VS2012: draw 2 intersecting rectangles: above yellow, the other red. A transparency Difference has been set on the yellow rectangle.

    AI version 8.0 output results via scripted AI 8.0 output:
    using the source code above, in versions up to and CS5, three rectangles are outputted (transparency is being flattened), but later versions (CS6 up to and the latest Creative Cloud Illustrator version) outputs only two rectangles (do not flatten but remove the transparency as if option aiPreservePaths instead of aiPreserveAppearance is active).

    Everything is working well in case the save to AI format 8.0 is done manually from within the Illustrator programs.

    What has been changed that has broken this functionality? Do we have to add something to the code mentioned above, or, has a bug been introduced in Illustrator from version CS5 to CS6 which is still present up to and today? We have no idea why this is not working anymore. Please look into it because this piece of functionality is quite important for our customers.

    For more than a decade the following Illustrator script has been applied via C# .NET in combination with all existing Illustrator versions (sourcecode):

    typelib.IllustratorSaveOptions saveOptions = new typelib.IllustratorSaveOptions();
    saveOptions.Compatibility = typelib.AiCompatibility.aiIllustrator8;
    saveOptions.FlattenOutput = typelib.AiOutputFlattening.aiPreserveAppearance;
    DestDoc.SaveAs(sPath, saveOptions);

    All over the internet we see a lot of people using the same code above (applying the exact same idea) also in other programming languages.

    Following test has been done with Illustrator versions CS, CS2, CS3, CS5, CS6, etc. on the latest Windows 10 operating system and VS2012: draw 2 intersecting rectangles: above yellow, the other red. A transparency Difference has been set on… 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

    1 comment  ·  SDK and 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

18. javascript doc.close() after error

    https://forums.adobe.com/message/9853322#9853322
    for details

    When you close the file in the script
    After that, an error (1346458189 ('PARM')) occurs with high probability.
    Closed processing is closed up to what is not closed or can not be closed
    It looks like a bug.

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

19. Illustrator Version 28.7.1 - xmpfile does not have a constructor ( using Extendscript with Illustrator )

    OS: macOS Sonoma 14.6.1 (23G93)
    Illustrator version 28.7.1

    Prior to this update I have been able through extendscript to read XMP data from a file. After the update I get an error:
    
    "XMPfile does not have a constructor".
    
    on the line of code:
    var xmpf = new XMPFile(.........

    Reverting to the prior version resolves the issue.

    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  ·  SDK and 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
    Completed (Comments Open)  ·  AdminAkshaya Saxena (Admin, Adobe Illustrator) responded

    We have fixed this issue in 29.0 and 28.7.2 releases.

20. AI 28.0 preferences corrupted by 28.1 with some 3rd party plugins

    When updating from Illustrator 28.0 to 28.1, some preference files may be corrupted if AI is running certain 3rd party plugins. These include any written with Hot Door's CORE and incorporating a WebView widget to display a web page, but I have received reports of this behavior with some SDK plugins as well.

    The problem it creates is that new files are not added to the File > Open Recent Files list, and any change to a different workspace is not saved.

    For my macOS Ventura with AI 28.1, deleting these preference files solved the problem: Plug-in Cache and plugincache.bin.

    For Windows 10 I had to also delete Adobe Illustrator Prefs and Adobe Illustrator Cloud Prefs.

    When updating from Illustrator 28.0 to 28.1, some preference files may be corrupted if AI is running certain 3rd party plugins. These include any written with Hot Door's CORE and incorporating a WebView widget to display a web page, but I have received reports of this behavior with some SDK plugins as well.

    The problem it creates is that new files are not added to the File > Open Recent Files list, and any change to a different workspace is not saved.

    For my macOS Ventura with AI 28.1, deleting these preference files solved the problem: Plug-in Cache and plugincache.bin.

    … 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  ·  SDK and 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