Softpedia >Mac >Utilities >Adobe Extension Manager >  Changelog

Adobe Extension Manager Changelog

What's new in Adobe Extension Manager CC 7.2.1.6

Jul 1, 2014
  • New features:
  • Supports both CC and CC 2014 products.
  • Supports CEP 5, the latest release of the infrastructure for HTML5/JavaScript extensions.
  • An administrative or root user can now install and remove extensions for other users. 
  • A new command-line parameter, disableSendRequest, turns off the default behavior of printing installation results to standard output.
  • Allows Adobe Exchange to install extensions when a certificate revocation list (CRL) is not available.

New in Adobe Extension Manager CC 7.1.0.113 (Sep 3, 2013)

  • Contains many improvements and fixes, including the ability to access lots more content from Adobe Exchange and update extensions.

New in Adobe Extension Manager CC 7.0.0.347 (Jun 19, 2013)

  • New Features:
  • Meta-content Support:
  • In addition to installing and managing ZXP product extensions, Extension Manager CC also manages meta-content (such as fonts, templates, and images) when it is packaged as a ZXP file. Meta-content is handled like extensions during installation, and is then listed under the category “Others”.
  • Changes in Extension Manager CC release:
  • This release of Extension Manager does not support a number of features that were present in the previous release. Features that are no longer available include the following:
  • Extension Sets: Manually enable or disable each extension.
  • Package Extensions: Use Adobe Extension Packager to package the extensions.
  • Convert MXP extensions to ZXP: Use Extension Manager CS6 for this conversion.
  • MXP extensions: This format does not support signatures, so MXP extensions cannot be published through Adobe Exchange and are no longer managed by Extension Manager. Use Extension Manager CS6 to convert them to ZXP extensions.
  • Fireworks: Install Fireworks extensions with Extension Manager CS6.
  • Undocumented attributes.
  • Rollback of file operations: If an extension installation fails, some files may be left on the computer.
  • Extension Update in application: you can use the command-line tool for this.
  • In this release, the extension name must be unique for all supported Adobe products. If you have installed an extension with a given name in any product, you cannot install one with the same name in another product, unless you remove the first one.
  • This applies to Adobe products that have both 32-bit and 64-bit versions, so they are named accordingly. For example, the pre-installed InDesign extension named "Alignment Panel" for the 32-bit version also has a 64-bit version named "Alignment Panel64", and InCopy versions named  "Alignment Panel IC" and "Alignment Panel64 IC".
  • Extension Manager CC no longer provides the option to install per-user extensions for all users; another user must re-install such an extension in order to use it. A per-user extension is one whose destination (of the whole or of any content) is under the user home directory.
  • Extension Manager CC checks for extension dependencies during installation, and so cannot install any extension that depends on a per-user extension for any other user.
  • For pre-installed extensions, Extension Manager CC loads MXI files from the pre-installed extension folder and ignores any ZXP files for that extension.
  • For hybrid extensions, the MXI file must set "file-type" to "CSXS" for all embedded CEP extensions.
  • For hybrid extensions, Extension Manager CC only validates the signature of the outer extension. The signature of an embedded CEP extension is not validated.
  • A standalone command line tool is provided in the CC release and the command format has changed from the CS6 release.
  • Extension Manager CC allows you to install an extension using BridgeTalk (note that the message body format has changed), but does not support enabling, disabling, removing, or updating an extension using BridgeTalk.

New in Adobe Extension Manager 6.0.5 (Feb 5, 2013)

  • This update provides improvements in installation behavior and tighter integration with Adobe Exchange.

New in Adobe Extension Manager 6.0.4 (Nov 7, 2012)

  • This update provides changes to enable Adobe Exchange Workflows, the changes will not be visible to end users of Adobe Extension Manager.

New in Adobe Extension Manager 6.0.2 (Aug 13, 2012)

  • The "Author" and "Description" fields now handle escape characters correctly. [3286224]
  • Extension Manager no longer hangs on the message "Loading extensions" if the user name contains an apostrophe. [3226968]
  • Extension Manager now correctly renders the XML-encoded character entity ampersand (&) in MXI-based extensions. [3207235]
  • An extension with a soft link can now be installed in Extension Manager CS6 in Mac OS 10.7, and the soft link is maintained in the extension package. [3084978, 3082867]
  • The description link for an extension now correctly appears at the top of the description tab of the license dialog and in the description panel. [3294980]

New in Adobe Extension Manager 6.0.1 (May 21, 2012)

  • This update provides some bug fixes and intellectual property protection for Agora extensions.

New in Adobe Extension Manager 5.5.3 (Apr 12, 2012)

  • This update addresses a critical issue in Extension Manager that prevents InDesign extensions from being imported in OS X Mountain Lion (10.8).

New in Adobe Extension Manager 5.5.2 (Dec 2, 2011)

  • This update addresses a critical bug in Extension Manager that prevents
  • extensions from being installed in Mac OS 10.7.

New in Adobe Extension Manager 5.5.1 (Aug 12, 2011)

  • Adds integration with the Adobe Product Improvement Program.

New in Adobe Extension Manager 5.0.1 (Jan 30, 2011)

  • Adds support for extensions which are signed by Adobe with the new root certificate from VeriSign (V3).