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.2.2

Released on September 20, 2021.

This release provides improvements to dragging and dropping widgets around the dashboard and some bug fixes.

Widget drag and drop usability enhancements

To keep the UI uncluttered, widget icons are now hidden until the user mouses over the chart.

A drag and drop handle icon has been added to widgets in the Analytics app and a more obvious frame is displayed so users can better visualize where they are moving the widget.

analytics drag drop

Bug fixes

  • Since Magnolia 6.2.11, widgets with custom views did not display the correct dialog when editing the widget. (ANALYTICS-373)

  • The dashboard layout crashed after opening a chart in full screen mode and dragging and dropping a chart. (ANALYTICS-375) -

  • The Definitions app displayed a severity level of MAJOR when analytics data suppliers were missing credentials. This has now been changed to MINOR. (ANALYTICS-377)

Analytics module 1.1.2

Released on September 20, 2021.

This maintenance release provides the following bug fix:

  • The Definitions app displayed a severity level of MAJOR when analytics data suppliers were missing credentials. This has now been changed to MINOR. (ANALYTICS-377)

Analytics module 1.2.1

Released on July 9, 2021.

This release provides the following bug fixes and an improvement for using Adobe Analytics in an IUX slot:

  • Add widget action in Analytic app does not work with Magnolia 6.2.9. (ANALYTICS-361)

  • Client-secret key not resolved for Adobe supplier in Analytics IUX slot. (ANALYTICS-364)

  • Enable filtering for Adobe supplier in Analytics IUX slot. (ANALYTICS-365)

Adobe Analytics requires specific configuration in Adobe Launch and the Magnolia template to enable filters in the analytics IUX slot.

Analytics module 1.1.1

Released on July 9, 2021.

This release provides the following bug fix and improvement for using Adobe Analytics in an IUX slot:

  • Client-secret key not resolved for Adobe supplier in Analytics IUX slot. (ANALYTICS-364)

  • Enable filtering for Adobe supplier in Analytics IUX slot. (ANALYTICS-365)

Adobe Analytics requires specific configuration in Adobe Launch and the Magnolia template to enable filters in the analytics IUX slot.

Analytics module 1.2

Released on May 7, 2021.

The Analytics module is included in the Magnolia cloud webapp bundle. It is not bundled in the standard DX Core webapp.

Note that, for the time being, Analytics module 1.1 is bundled in the dx-core-cloud-webapp bundle.

New UI for no-code dashboards and widgets

This release delivers a new user-friendly UI to empower editors and marketeers in creating and editing their own dashboards and widgets.

In Analytics module 1.1, only technical users who were able to work with YAML files could build charts and dashboards.

Now users can create a dashboard and add widgets featuring commonly used metrics in just a few clicks. A preview of the widget being created is displayed as soon as metrics are selected. Once added to the dashboard, widgets can be dragged and dropped around, or expanded for better viewing.

See the Analytics app for how to create dashboards and add widgets.

Commonly used metrics out-of-the-box and advanced metrics

Default metrics and dimensions are provided for each third-party analytics tool so that end users can start creating popular widgets as soon as the data supplier is configured.

Users with in-depth knowledge of their analytics data can access all the metrics and dimensions available from their data supplier when adding widgets by clicking the Add metrics button.

Developers can change the default metrics and dimensions available in the Analytics app through decoration in the data supplier definitions.

Analytics data from different sources in one dashboard

A dashboard can contain widgets displaying data from different data suppliers.

You can create widgets from different sources of analytics data, such as Adobe Analytics, file-based data, Google Analytics, Matomo, and display them all in a single dashboard.

Persistent filters

Previously, dashboard filters were cleared when you changed the dashboard layout, added a widget or dragged and dropped a widget.

Now filters persist until you reload the dashboard, select another dashboard, add a dashboard or delete a dashboard.

Dynamic tooltips in charts

To provide more visual information about the data in the widgets, dynamic tooltips are now displayed by default when mousing over charts. The green tooltip is the label for the Y axis.

JSON Path Evaluator

A JSONPath evaluator is provided to help you test and evaluate your JSONPath.

Enable or disable dashboards

Dashboards are available to all users. Instead of deleting them, you can hide them by setting the enable property to false if required.

Backwards compatibility with Analytics module 1.1 charts

Analytics module 1.2 supports the display of dashboards created using the previous version of this module. Dashboards created in version 1.1 can be viewed, but not edited. Users are notified of this limitation in the UI.

We recommend you use the new Analytics app to re-create your 1.1 dashboards and widgets from scratch. However, we provide an example of how to migrate in How to migrate Analytics module 1.1 dashboards to 1.2 if you prefer to reconfigure your charts and dashboards.

Timeline chart supported

A new timeline chart type is provided by the magnolia-analytics-amcharts-samples module. See the amCharts timeline chart demo.

Registries for data suppliers and chart definitions

Previously, dataSuppliers and chartDefinitions were configured in the dashboard yaml definitions and would sometimes need to be duplicated.

Now, Magnolia provides registries for the dataSupplier and chartDefinition configuration.

Data suppliers are defined once under this directory: /<module name>/dataSuppliers/<dataSupplierRegistryFile.yaml>.

The chartDefinition configuration in the dashboard definition yaml file can be included from the chart definitions provided by the magnolia-analytics-ui submodule:

For example:

          timeline-chart:   !include:/analytics-ui/charts/timeline/timeline.yaml

Make sure the chart definitions are known to a registry and are listed under charts in the Definitions app.

Date and decimal formatting for your widgets

You can format dates and decimals that appear in your dashboard widgets under: analytics/config.yaml

dateFormat: dd.MM.yy
decimalNumberFormat: "#0.00"

amCharts version 4.9.17

This release comes with an amCharts^ update from 4.5.3 to 4.9.17.

Addon-commons cache module replaces AnalyticsDataSupplierCache

The AnalyticsDataSupplierCache used in 1.1 has been replaced by the Addon-commons cache module in 1.2.

If you customized your cache configuration in 1.1, update the new cache configuration under /analytics/decorations/addon-commons-cache/config.yaml.

Deprecated classes

  • The class info.magnolia.analytics.google.datasource.GoogleDataSupplierWithDateFormatter provided in Analytics module 1.1 for date formatting has been deprecated in favor of info.magnolia.analytics.google.datasource.GoogleDataSupplier in 1.2.

  • The class info.magnolia.analytics.matomo.datasource.MatomoDataSupplier provided in Analytics module 1.1 for date formatting has been deprecated in favor of info.magnolia.analytics.matomo.datasource.MatomoDataSupplierWithTransformer.

  • The class info.magnolia.analytics.datasource.MostActiveUsersDataSupplier provided in Analytics module 1.1 has been deprecated in favor of info.magnolia.analytics.datasource.MostActiveUsersOnPageDataSupplier due to json data has been changed.

  • The class info.magnolia.analytics.datasource.PeriscopeDataSupplier provided in Analytics module 1.1 has been deprecated in favor of info.magnolia.analytics.datasource.FrequentlySearchAppDataSupplier due to json data has been changed.

  • The class info.magnolia.analytics.datasource.RecentActivitiesDataSupplier provided in Analytics module 1.1 has been deprecated in favor of info.magnolia.analytics.datasource.RecentPageActivitiesDataSupplier due to json data has been changed.

Changelog

See the Analytics Connector Pack 1.2 changelog for all the changes.

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.3.1

Released on October 6, 2021.

This release brings a number of improvements.

New ecommerceLinkField field

A new ecommerceLinkField field (extends Link field) has been introduced.

The ecommerceLinkField replaces the ecommerceChooserField, which is deprecated.

Here are the default configurations for the different e-commerce components provided:

/ecommerce-templating/dialogs/components/category-list-v3.yaml
form:
  properties:
    categoryList:
      $type: ecommerceLinkField
      enableCategorySelection: false
/ecommerce-templating/dialogs/components/product-detail-v3.yaml
form:
  properties:
    productDetail:
      $type: ecommerceLinkField
/ecommerce-templating/dialogs/components/product-list-v3.yaml
form:
  properties:
    productList:
      $type: ecommerceLinkField
      enableProductSelection: false
/ecommerce-templating/dialogs/components/product-teaser-v3.yaml
form:
  properties:
    productTeaser:
      $type: ecommerceLinkField

New validators

New EcommerceChooserValidator classes have been added to ensure the connection, category and product selected are valid when adding e-commerce content to a page.

Connection status message display improved

When you test a connection, the result message is now displayed for longer to make it easier to read.

E-commerce module 1.2.6

Released on October 6, 2021.

This maintenance release:

  • Improves the connection status message: when you test a connection, the result message is now displayed for longer to make it easier to read. (ECOMMERCE-465)

  • Fixes an exception that occurred when selecting a product detail component from the list of previously added products in the dialog. (ECOMMERCE-447)

E-commerce module 1.3

Released on July 21, 2021.

This Magnolia CMS 6.2.9+ compatible release brings improvements and bug fixes:

Intuitive product chooser

A user-friendly product chooser makes finding and selecting categories and products faster and simpler for end users.

Product chooser dialog

Each column provides a filter at the top.

The chooser dialog can also be configured to enable or disable certain columns.

Updated component definitions and template files

You can find component definitions and template files configured under /ecommerce-templating/templates/components.

The components introduced in v1.3 are suffixed with -v3.

Those with no suffix are provided for backwards compatibility with E-commerce v1.2.x.

You can still view and edit the 1.2.x version components but we recommend you recreate your e-commerce pages using the new component definitions to benefit from the new product chooser dialog and other improvements.

E-commerce module 1.2.5

Released on July 21, 2021.

This Magnolia CMS 6.2.2+ compatible maintenance release brings improvements and bug fixes:

Category list and Product list components updated

The sample components Category list and Product list have been aligned with the other e-commerce page components and now provide chooser dialogs for selecting the e-commerce content to be displayed.

The chooser dialogs only store the connectionId property, which consists of {definitionName}/{connectionName}) in JCR instead of the previously stored properties definition and connection.

The related template files category-list.ftl and product-list.ftl were adapted accordingly.

To ensure backward compatibility with the previous template files, an ecommerce-freemarker renderer was introduced and configured for the renderType property in the component configuration yaml files:

  • ecommerce-templating/dialogs/components/category-list.yaml

  • ecommerce-templating/dialogs/components/product-list.yaml

The ecommerce-freemarker renderer parses the definition and connection names from the connectionId property and wraps the component content with the definition and connection properties with the parsed values.

commercetools locale configuration in YAML file

A new locale parameter used for product/category names or descriptions can be set in the commercetools configuration.

See the parameter description in the tab for commercetools.

See the 1.2.5 changelog for all the changes.

E-commerce module 1.2.4

Released on April 13, 2021.

This release brings full compatibility with Magnolia 6.2.7 as well as some bug and security fixes.

Notable fixes:

See the 1.2.4 changelog for all the changes.

E-commerce module 1.2.3

Released on December 1, 2020.

E-commerce module 1.2.3 is a bug-fixing release.

See the 1.2.3 changelog for all the changes.

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.

See the 1.2.2 changelog for all the changes.

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.

See the 1.2.1 changelog for all the changes.

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}")

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.

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:

See the 1.2.2 changelog for all the 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

See the 1.2.1 changelog for all the changes.

E-commerce module 1.1

Released on April 6, 2020.

This release delivers a new connector for Salesforce Commerce.

See the 1.1 changelog for all the changes.

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.1.0

Released on November 15, 2021.

This release brings a number of improvements and bug fixes.

Support for Bynder image derivatives

Bynder provides different image derivatives (referred to as image variations in Magnolia) such as large, medium, small. This functionality is now integrated into Magnolia and can be used via the DAM templating function (damfn).

For example, to retrieve the small Bynder derivative:

damfn.getAssetLink(bynderAsset, "small")
Bynder derivatives do not function in the same way as standard Magnolia image variations as described in Defining image variations. You do _not have to configure the theme to use Bynder derivatives.
You must configure the Bynder proxy service to use variations. Only image assets have variations.

To see which image variations are available for a given Bynder asset, look in the asset details view:

Bynder derivatives information

See Using Bynder image derivatives for more information.

For more information about Bynder derivatives, see Derivatives (Create Smaller Versions of Assets) in the Bynder documentation.

We do not support image variations for S3 assets. You must upload different versions of the same image if you need to use variations.

Improved caching of S3 bucket regions

We have improved S3 caching of bucket regions in Magnolia to fix an issue causing performance problems when using the delivery endpoint for Cloud customers.

Name column filters

When selecting external assets, you can now use a filter at the top of the Name column for both Bynder and S3 to reduce the number of assets displayed.

Name column filter

Note that in the case of S3, you must open the bucket of your choice before filtering within it. Filtering at the root level does not produce results.

AWS Regions are listed by code and unavailable regions are not displayed

When creating an S3 bucket in the Assets app, the list of regions available are ordered alphabetically and unavailable regions are no longer displayed.

Name column filter

For more information about AWS disabled regions, see Managing AWS Regions

Demo Text and External Image component removed

Previously the DAM Connector Pack provided a sample Text and External Image component in the Travel demo to help get users started using external assets in pages.

This sample component has now been removed. We recommend you use the standard MTK Text and Image component instead.

S3 asset names can no longer be edited

To avoid S3 asset link references breaking, it is no longer possible to rename S3 assets in Magnolia.

The Asset name field is now disabled in the asset details view.

Bug fix

  • Sorting by name does not work for S3 and Bynder. EXTDAM-150

External DAM module 1.0.8

Released on Oct 27, 2021.

This release improves S3 caching of bucket regions in Magnolia to fix an issue causing performance problems when using the delivery endpoint for Cloud customers.

External DAM module 1.0.7

Released on June 1, 2021.

This release brings a number of improvements.

From External DAM 1.0.7 (DAM module 3.0.8), you can configure a single asset provider for link fields to limit your users to selecting assets from only one asset provider.

Previously, you had to use the aggregated damLinkField and users had to choose from all the enabled asset providers.

External DAM module 1.0.6

Released on April 26, 2021.

This release brings a number of improvements and bug fixes.

Bynder and AWS S3 subapps disabled by default

By default, the Bynder and AWS S3 subapps are disabled and do not appear in the Magnolia Magnolia Assets app.

You must enable the subapp for your external solution <dam-connector>/decorations/dam.

When upgrading from an earlier version of External DAM, subapps that were previously displayed are disabled until you enable them again.

AWS default credential provider chain

As an alternative to using the static Magnolia Password manager app to store your AWS S3 credentials, you can now use the AWS default credential provider chain.

External DAM module 1.0.5

Released on March 30, 2021.

This release delivers a third party library update:

  • Kotlin Standard Library updated to 1.4.21.

External DAM module 1.0.4

Released on January 28, 2021.

This release brings 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.3

Released on May 6, 2021.

This release brings full compatibility with Magnolia 6.2.4 as well as a bug fix for the marketing form component, which was not working: MKTAUT-130.

Marketing Automation module 1.0.2

Released on January 28, 2021.

This release brings full compatibility with Magnolia 6.2.2 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 Sales Cloud, 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.

A/B/n Testing

See A/B/n Testing for an overview.

A/B/n Testing module 1.0.1

Released on July 26, 2021.

Bug fixing and improvement release.

A/B/n Testing module 1.0

Released on June 17, 2021.

General availability release of the A/B/n Testing Special Feature, which provides native A/B/n Testing to help you make decisions about your content based on real data from your existing traffic.

See A/B/n Testing for an overview of the functionality provided.

Note that A/B/n Testing is compatible with Magnolia CMS 6.2.4 onwards.

Live Copy

See Live Copy for an overview.

Live Copy module 3.2.6

Released on September 23, 2021.

This bug fixing release also brings the following improvements:

Improvements

  • Node names are now protected (propertiesToIgnore added) from master content change pushes. LIVECOPY-290

  • Improved protection of the MultiValueField field. LIVECOPY-283

  • Field transformers are checked before relinking. LIVECOPY-282

Bug fixes

  • Updating a child page makes the parent page appear as updated. LIVECOPY-222

  • Live copy workflows have invalid markup leading to log errors. LIVECOPY-252

  • The defaultLocale property affects the selected language in the Pages app. LIVECOPY-266

  • Protecting fields in a Switchable Field does not work. LIVECOPY-281

  • Protect button does not work correctly if a locale is the default in a live copy tree but not the master default. LIVECOPY-288

Live Copy module 3.2.5

Released on August 9, 2021.

This release comes with a hot fix for version 3.2.4, which you may skip and update directly to version 3.2.5.

This is the recommended version for use with Magnolia 6.2.11.

This bug fixing release also brings the following improvements:

Improvements

Bug fixes

  • Variants are not published. LIVECOPY-237

  • Exception in relink if content does not matching definition. LIVECOPY-256

  • LiveCopy changes the user and timestamp of unedited pages. LIVECOPY-258

  • Two live copies in the same tree are not working. We have disabled some actions (Duplicate page, Copy page and Paste page) for live copies. LIVECOPY-260

  • RichText fields and MultiValueCompositeLinkField are automatically protected. LIVECOPY-263

  • Relink action doesn’t work for a link in switchableField. LIVECOPY-272

  • Relink action doesn’t work for linkField in area. LIVECOPY-273

  • MultiValueCompositeLinkField, MultiValueLinkField cannot relink in StandardRewirePageLinksHelper. LIVECOPY-275

  • MultiValueCompositeLinkField cannot relink in CompatibilityRewirePageLinksHelper. LIVECOPY-276

  • MultiValueCompositeRichTextField, MultiValueRichTextField cannot relink in StandardRewirePageLinksHelper. LIVECOPY-277

  • MultiValueCompositeRichTextField, MultiValueRichTextField cannot relink in CompatibilityRewirePageLinksHelper. LIVECOPY-278

Live Copy module 2.2.1

Released on August 6, 2021.

This is the recommended version for use with Magnolia 5.7.

Bug fixing release:

Live Copy module 3.2.3

Released on March 31, 2021.

Bug fixing release:

  • Publishing does not set the userName property on the task. LIVECOPY-246

  • Push action dialog ignores autoRewire property value. LIVECOPY-247

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.

Live Copy module 3.0

Updated for Magnolia 6.0 compatibility.

Live Copy module 2.1

Updated for Magnolia 5.7 compatibility.

Live Copy module 2.0.6

Live Copy module 2.0.5

POM edited to prevent versioning clash with magnolia-pages-editor-widget.

Live Copy module 2.0.2

Live Copy module 2.0.1

Live Copy module 2.0

Initial release of the Incubator (previously called Extensions) version of the module.

Feedback