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
Released on April 6, 2020. This release delivers a new connector for Adobe Analytics. 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.Analytics module 1.1
Analytics module 1.0
Commerce Connector Pack
Released on December 1, 2020. Bug fix release. Released on November 30, 2020. This release brings full compatibility with Magnolia 6.2.5 as well as some bug fixes. Released on September 16, 2020. This release brings full compatibility with Magnolia 6.2.3 as well as some bug fixes. Released on August 20, 2020. This release delivers a new connector for SAP Commerce Cloud (formerly Hybris). The connector includes a new User endpoint for SAP: Note that the documentation for the new User REST endpoint will be available shortly. This release provides a V2 of two endpoints: Checkout endpoint — In v2, the checkout endpoint sets the address of a Cart endpoint — In v2, The 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. 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: 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: Released on April 6, 2020. This release delivers a new connector for Salesforce Commerce. 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.E-commerce module 1.2.3
E-commerce module 1.2.2
E-commerce module 1.2.1
E-commerce module 1.2
SAP Commerce Cloud Connector
/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}")
Cart and Checkout endpoint updates
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")
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}")
ecommerce-rest-role
has been updated to allow the v2 endpoints.Product chooser
ecommerce-rest-role
to allow v2 endpointsE-commerce module 1.1.1
E-commerce module 1.1
E-commerce module 1.0
DAM Connector Pack
Released on December 1, 2020. This release brings a number of improvements and bug fixes 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.03 that blocks users from uploading assets to Bynder via Magnolia.
EXTDAM-198
-
Getting issue details...
STATUS
You can now configure pagination to improve response times.
EXTDAM-169
-
Getting issue details...
STATUS
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. Note that once Bynder assets are marked as published they cannot be unpublished or made private again in Magnolia.
EXTDAM-62
-
Getting issue details...
STATUS
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. 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. You can configure the maximum time the system spends searching for S3 assets to be displayed in the Magnolia interface using a new parameter called By default, the maximum search time is 10 seconds ( 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. Released on June 22nd, 2020. This release brings compatibility for Magnolia 6.2.1 and a number of minor improvements and bug fixes: 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.External DAM module 1.0.3
Bynder SDK 2.2.1
Configuring pagination
Publish Bynder assets from within Magnolia
External DAM module 1.0.2
Improved handling of large numbers of S3 assets
Configure the maximum search time for S3
maxSearchTimeInMilis
under dam-s3/config.yaml
.maxSearchTimeInMilis: 10000
).Mime types
Bug fixes
External DAM module 1.0.1
External DAM module 1.0
Marketing Automation Connector Pack
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 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.Marketing Automation module 1.0.1
Marketing Automation module 1.0
Optimization Connector Pack
Released October 9, 2020. This bugfixing release should be used with Magnolia 6.1.
SIMPROVE-6
-
Getting issue details...
STATUS
Released May 8, 2020. This bugfixing release also provides compatibility with Magnolia 6.2.
SIMPROVE-4
-
Getting issue details...
STATUS
SIMPROVE-5
-
Getting issue details...
STATUS
SIMPROVE-6
-
Getting issue details...
STATUS
SIMPROVE-3
-
Getting issue details...
STATUS
The Siteimprove module 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.Siteimprove module 1.1.6
Siteimprove module 1.2
Siteimprove module 1.1.5
Siteimprove module 1.1.4
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
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: Released on August 20, 2020. This release provides the following bug fixes: Released on November 13, 2019.
LIVECOPY-153
-
Getting issue details...
STATUS
LIVECOPY-69
-
Getting issue details...
STATUS
LIVECOPY-163
-
Getting issue details...
STATUS
LIVECOPY-143
-
Getting issue details...
STATUS
Released on September 11, 2019.
LIVECOPY-69
-
Getting issue details...
STATUS
LIVECOPY-47
-
Getting issue details...
STATUS
LIVECOPY-11
-
Getting issue details...
STATUS
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.Live Copy 3.2
Improvements
Bug fixes
Live Copy 3.1.2
Live Copy 3.1.1
Live Copy 2.0.7
Live Copy 3.1