Connector Pack and Special Feature changelog

Connector Packs

Connector Packs complement DX Core. Each Connector Pack integrates Magnolia with an adjacent software category. The packs are optional. You typically need to connect multiple systems when building a best-of-breed digital experience platform. Connector Packs make it all easier.

Analytics Connector Pack

See Analytics Connector Pack for an overview.

Analytics module 1.1

Released on April 6, 2020.

This release delivers a new connector for Adobe Analytics.

Analytics module 1.0

Released on July 9, 2019.

Initial release of the Analytics Connector Pack modules, which provide a framework and connectors to inject your analytics data into the Magnolia UI enabling authors and marketeers to make data-driven decisions. See Analytics Connector Pack for an overview of the functionality provided.

Commerce Connector Pack

See Commerce Connector Pack for an overview.

E-commerce module 1.2.3

Released on December 1, 2020.

Bug fix release.

E-commerce module 1.2.2

Released on November 30, 2020.

This release brings full compatibility with Magnolia 6.2.5 as well as some bug fixes.

E-commerce module 1.2.1

Released on September 16, 2020.

This release brings full compatibility with Magnolia 6.2.3 as well as some bug fixes.

E-commerce module 1.2

Released on August 20, 2020.

SAP Commerce Cloud Connector

This release delivers a new connector for SAP Commerce Cloud (formerly Hybris).

The connector includes a new User endpoint for SAP:

  • /users/{userId}/accessToken — To log in a user and obtain the user’s access token.

  • /users/{userId}/addresses — To handle stored addresses of users.

  • /users/{userId}/paymentMethods — To handle stored payment methods of users.

accessToken
@POST
@Path("/v2/users/{userId}/accessToken")

getUserAddresses
@GET
@Path("/v2/users/{userId}/addresses")

createUserAddress
@POST
@Path("/v2/users/{userId}/addresses")

deleteUserAddress
@DELETE
@Path("/v2/users/{userId}/addresses/{addressId}")

updateUserAddress
@PUT
@Path("/v2/users/{userId}/addresses/{addressId}")

getUserPaymentMethods
@GET
@Path("/v2/users/{userId}/paymentMethods")

updateUserPaymentMethod
@PUT
@Path("/v2/users/{userId}/paymentMethods/{paymentMethodId}")

deleteUserPaymentMethod
@DELETE
@Path("/v2/users/{userId}/paymentMethods/{paymentMethodId}")

Note that the documentation for the new User REST endpoint will be available shortly.

Cart and Checkout endpoint updates

This release provides a V2 of two endpoints:

  • Checkout endpoint — In v2, the checkout endpoint sets the address of a cartId to ensure the correct resource is consistently identified. For example, the v1 /checkouts/address/{cartId} becomes in v2 /checkouts/carts/{cartId}/address.

    setAddress
    @PUT
    @Path("/checkouts/cart/{cartId}/address")
    
    setShippingMethod
    @PUT
    @Path("/checkouts/cart/{cartId}/shippingmethod")
    
    createOrder
    @POST
    @Path("/checkouts/cart/{cartId}/order")
    
    getShippingMethods
    @POST
    @Path("/checkouts/cart/{cartId}/shippingmethods")
  • Cart endpoint — In v2, cartId is a path parameter instead of form parameter in the REST calls. For example the v1 /carts/items becomes in v2 /carts/{cartId}/items. The other parts of the call are unchanged.

    addItem
    @POST
    @Path("/v2/carts/{cartId}/items")
    
    removeItem
    @DELETE
    @Path("/v2/carts/{cartId}/items/{itemId}")
    
    updateItemQuantity
    @POST
    @Path("/v2/carts/{cartId}/items/{itemId}")

The ecommerce-rest-role has been updated to allow the v2 endpoints.

Note that the documentation for both v2 endpoints will be updated shortly.

V1 of the Cart and Checkout endpoints are deprecated from this release on. They will be removed in the next major version of the Commerce Connector Pack.

Product chooser

This release also improves the sample template provided in the Pages app. Magnolia provides a dialog to select the connection, category and product instead of requiring you to manually enter the connection name, definition name and a product ID. If you only have one connection configured, you choose the category and product directly.

List of changes:

E-commerce module 1.1.1

Released on July 7, 2020.

This release introduces compatibility with Magnolia 6.2.2 and an improvement that means images are displayed instead of the URL now in the E-commerce app (see Configuring the images displayed in the E-commerce app). List of changes:

  • [ECOMMERCE-226] - Prod detail sub-app - image field displays image instead of path

  • [ECOMMERCE-295] - Use i18n keys instead of literals for labels in product detail view

  • [ECOMMERCE-254] - Manual tagging action should tag a product even if the product has a tag already

E-commerce module 1.1

Released on April 6, 2020.

This release delivers a new connector for Salesforce Commerce.

E-commerce module 1.0

Released on July 9, 2019.

Initial release of the Commerce Connector Pack for connecting to e-commerce systems such as Magento and commercetools.

See Commerce Connector Pack for an overview of the functionality provided.

DAM Connector Pack

See DAM Connector Pack for an overview.

External DAM module 1.0.4

Released on January 28, 2021.

This release brings full compatibility with Magnolia 6.2.6 and a number of improvements and bug fixes.

Proxy service to protect private asset URLS (Bynder)

To protect the URLs of private Bynder assets rendered in Magnolia, you must use the proxy service provided.

When using the proxy, if you want to make a Bynder asset public, for example an image asset used in the Pages app, you must publish the image as well as the page in Magnolia.

You can enable or disable the proxy service using the proxyMode parameter.

The proxy service is only available with Magnolia Core 6.2.6. If you use an earlier version of Magnolia Core, you must disable the proxy service.

See EXTDAM-160.

Publish S3 assets from within Magnolia

You can now publish S3 assets via the Magnolia UI. By default, all S3 assets are private.

If you want to use S3 assets on a public page, you must publish them to make them public.

See EXTDAM-63.

Enable previewing for S3 assets

When you upload assets via Magnolia to S3, they are set to private by default. If you want to keep the preview functionality available, you must use presigned urls.

See EXTDAM-157.

Folder paths for AWS S3

Your location in the S3 folder hierarchy is now displayed in the bottom left-hand corner of the asset browser.

See EXTDAM-190.

Bug fix: User sessions overlap when browsing S3 assets

When you have two or more users trying to browse assets in S3 the sessions can overlap each other. Users may enter the app in a folder opened by another user in another session instead of the top level folder.

See EXTDAM-210.

External DAM module 1.0.3

Released on December 1, 2020.

This release brings a number of improvements and bug fixes.

Bynder SDK 2.2.1

The Bynder SDK version has been reverted from 2.2.4 to 2.2.1.

This resolves the issue discovered in version External DAM 1.0.3 that blocks users from uploading assets to Bynder via Magnolia.

See EXTDAM-189.

Configuring pagination

You can now configure pagination to improve response times.

See EXTDAM-169.

Publish Bynder assets from within Magnolia

You can now publish Bynder assets via the Magnolia UI.

By default, all Bynder assets are private. If you want to use Bynder assets on a public page, you must publish them to make them public.

Once Bynder assets are marked as published they cannot be unpublished or made private again in Magnolia.

See EXTDAM-62.

External DAM module 1.0.2

Released on November 18, 2020.

This release brings compatibility for Magnolia 6.2.4 and a number of improvements and bug fixes.

We have discovered an issue with Bynder SDK version 2.2.4 and External DAM 1.0.2 that blocks users from uploading assets to Bynder via Magnolia.

Do not use this release if you are a Bynder connector user. External DAM 1.0.3 corrects the issue and will be released soon.

Improved handling of large numbers of S3 assets

Magnolia has improved how large numbers (thousands) of assets in a given S3 folder are rendered.

Magnolia has a specialized method that counts the total number of assets in your S3 system instead of creating the corresponding internal objects. Since S3 only allows batches of 1000 assets to be retrieved in a given call, we iterate as many API calls as necessary to retrieve the assets stored in S3.

For example, Magnolia must make 100 API calls to retrieve 100 000 assets. Depending on your internet bandwidth, cache and other factors, this could take around 1 minute to complete. For better response times, we recommend that you store a maximum of 10 000 assets per S3 bucket.

Configure the maximum search time for S3

You can configure the maximum time Magnolia Periscope spends searching for S3 assets to be displayed in the Magnolia interface using a new parameter called maxSearchTimeInMilis under dam-s3/config.yaml.

By default, the maximum search time is 10 seconds (maxSearchTimeInMilis: 10000).

See EXTDAM-184.

Mime types

If you upload an asset that does not have a suffix, Magnolia now infers the mime type from the binary.

To avoid extra API calls to S3, we recommend you include the suffix whenever possible.

See EXTDAM-126.

Bug fixes

See EXTDAM-167.

External DAM module 1.0.1

Released on June 22nd, 2020.

This release brings compatibility for Magnolia 6.2.1 and a number of minor improvements and bug fixes:

  • [EXTDAM-105] - (Bynder) Allow upload another image when editing

  • [EXTDAM-106] - (Bynder) Set the asset’s name with the name of the upload file

  • [EXTDAM-121 ] - Cache is not applied when browsing through app-chooser

  • [EXTDAM-119] - Adjust to Periscope changes in 6.2.1

  • [EXTDAM-104] - Show notification to the user when an async action started

  • [EXTDAM-108] - (Bynder) Correct notify message with apostrophe

  • [EXTDAM-112] - (Bynder) Edit asset fails with exception

  • [EXTDAM-113] - (Bynder) Changing the image is not reflected in the tree unless the name is updated

  • [EXTDAM-114] - Periscope search is case sensitive

  • [EXTDAM-115] - (S3) Double click on bucket or folder opens the editor

  • [EXTDAM-116] - (S3) Strange behaviour deleting a folder

  • [EXTDAM-120] - (Bynder) The item deletion does not happen immediately

External DAM module 1.0

Released on April 6, 2020.

Initial release of the DAM Connector Pack for integrating with Bynder and Amazon S3, so that you can use your assets directly in Magnolia.

See DAM Connector Pack for an overview of the functionality provided.

Marketing Automation Connector Pack

Marketing Automation module 1.0.2

Released on January 28, 2021.

This release brings full compatibility with Magnolia 6.2.6 as well as a security-related bug fix: MKTAUT-116

We keep the details of security-related fixes private in line with our security policy. Contact our Support team if you need more information.

Marketing Automation module 1.0.1

Released on July 21, 2020.

This release provides bug fixes including a fix for a null pointer exception:

MKTAUT-112 - Reinitialising the connection may cause a NPE

Marketing Automation module 1.0

Released on April 6, 2020.

Initial release of the Marketing Automation Connector Pack for integrating with third-party marketing software solutions, such as Marketo and Salesforce, so that you can use your forms or form fields directly in Magnolia and efficiently collect data about your prospects and customers.

See Marketing Automation Connector Pack for an overview of the functionality provided.

Optimization Connector Pack

See Optimization Connector Pack for an overview.

Siteimprove module 1.1.6

Released October 9, 2020.

This bugfixing release should be used with Magnolia 6.1.

Siteimprove module 1.2

Released May 8, 2020.

This bugfixing release also provides compatibility with Magnolia 6.2.

Siteimprove module 1.1.5

Siteimprove module 1.1.4

The is now part of the Optimization Connector Pack. Siteimprove enables you to perform SEO checks using the cloud-based application Siteimprove. It is a tool to help you score higher ranking in search engines and check how your content is performing over all.

For documentation for the legacy versions of Siteimprove, see Incubator - Siteimprove.

Version 1.1

Updated for Magnolia 6.0 compatibility.

Version 1.0.4

Version 1.0.3

Initial release of the Extensions version of the module.

Special Features

Special Features are additional functionality available for specific needs and use cases such as managing complex multisite installations that share similar content, monitoring performance and scaling up publication. Special Features are optional. You get the best results when using them with guidance and expertise from Magnolia.

Live Copy

See Live Copy for an overview.

Live Copy module 3.2.2

Released on March 3, 2021.

Bug fixing release:

Live Copy module 3.2.1

Released on January 28, 2021.

This bug fixing release also brings full compatibility with Magnolia 6.2.6 and the following improvement:

Protect fields per language

You can protect a field in one language and not another using the language switcher and then clicking on the protect field icon. For example if you want to protect the German version of a given field and not the English version, you switch to German and protect the field. When you switch back to English, the field is not protected.

Links inside composite fields were not being relinked to the live copy pages correctly and continued to point to the master pages. Now, when you click Relink all pages to live copy pages, they are relinked correctly.

Live Copy module 3.2

Released on August 26, 2020

This release brings full compatibility with Magnolia 6.2.2 and the new UI framework as well as some new functionality and improvements:

Improvements

  • [LIVECOPY-108] - Open the Master Page from a live copy

  • [LIVECOPY-42] - Add a open as new window button for each page in the ReferencedPagesField

  • [LIVECOPY-44] - Show if the referenced page has page variations in the ReferencedPagesField

  • [LIVECOPY-145] - When I delete Master, LC still shows link to (and actions) to Master

  • [LIVECOPY-149] - Locking the component when using the Relink live copy function should be optional

  • [LIVECOPY-150] - Only push master content pages to specific pages

  • [LIVECOPY-151] - When pushing master content changes users can auto publish content

  • [LIVECOPY-159] - Fields under composite/switchable/multi fields are protected independently from the parent field

  • [LIVECOPY-190] - Change the color of a partially protected component (only certain fields are disabled)

Bug fixes

  • [LIVECOPY-171] - Protect/unprotect complex fields

  • [LIVECOPY-194] - Push master content changes position of component order

  • [LIVECOPY-195] - Enable/disable updates for component does not update the detail page

Live Copy module 3.1.2

Released on August 20, 2020.

This release provides the following bug fixes:

  • [LIVECOPY-173] - Push master content changes position of component order

  • [LIVECOPY-178] - NPE is thrown when attempting to create a live copy from page

  • [LIVECOPY-217] - Live Copy relink does not work

  • [LIVECOPY-218] - ItemNotFound exception when pushing master content changes

Live Copy module 3.1.1

Released on November 13, 2019.

Live Copy module 2.0.7

Released on September 11, 2019.

Live Copy module 3.1

Released on July 5, 2019.

Live Copy is now a Special Features module. Live Copy helps you manage complex multisite installations that share similar content by creating live copies of master sites.

These are legacy versions of Live Copy, previously available in the Magnolia Professional Services Incubator.

Feedback