Deprecations

This page provides a comprehensive summary of deprecations that have been announced by Magnolia in accordance with our deprecation policy.

Magnolia 5 UI framework (March 27, 2020)

The Magnolia 5 UI framework is now marked as deprecated in the documentation. You are advised to use the updated implementations of Magnolia 6 UI.

In code, this means that every *-compatibility artifact has been deprecated (for example, magnolia-personalization-compatibility). The deprecated classes contain links to their replacements.

The magnolia-ui-framework-compatibility module will be supported until the 6.2 branch reaches end of life. It will be removed from Magnolia completely with the next LTS release. See our end-of-life policy for more information.

Multiple modules replaced with Connector Packs (November 21, 2019)

Magnolia’s new Connector Packs simplify integration with external systems and will supersede the old modules, as we want to focus our offering on current and future market trends.

This announcement provides you with a list of modules that are going into maintenance mode with immediate effect. They will ultimately become deprecated.

Customer data and CRM connectors

We are building a new Customer Data Connector Pack. The pack will include a framework to make integrations easy and will launch with two out-of-the-box connectors: Salesforce CRM and Marketo.

DAM connectors

We are building a new DAM Connector Pack. The pack will include a framework to make integrations easy and will launch with two out-of-the-box connectors: Amazon S3 and Bynder.

Commerce connectors

We launched the Commerce Connector Pack earlier this year. The pack includes a framework and connectors to Magento and commercetools. As we put the modules above into maintenance mode and gradually deprecate them, we will add a new Salesforce Commerce connector to the Commerce Connector Pack.

JavaServer Pages (November 15, 2019)

With the release of Magnolia 6.0, support for JavaServer Pages (JSP) was dropped as the technology is now generally considered outdated.

This means that the Apache Standard Taglibs and the Templating JSP module are not included in our Bundles and webapps and that JSP is no longer available as a page renderer.

If you rely on JSP-based functionalities, see the following links for alternative solutions. Some of the links will take you to the Magnolia Community Wiki.

If you wish to keep using JSP in the 6.0 branch, please contact Magnolia Services first.

Google Analytics Visualization module (June 26, 2019)

The Google Analytics Visualization (GAV) module went into maintenance mode with the release of Magnolia 6.1 and is no longer shipped in our bundles. Maintenance mode is the first step towards deprecation.

The GAV module enabled you to view Google Analytics data within Magnolia. The module displayed performance metrics in the Pages app and other apps. It helped authors make data-driven decisions and avoid having to jump between tools.

We now focus our efforts on a new Analytics framework that connects not only to Google Analytics but also to other third-party analytics providers. The new framework can inject charts and other performance indicators into many places in the AdminCentral UI, effectively replacing the GAV module. The Analytics framework integrates closely with Magnolia 6 UI, offering more flexible placement of metrics that help authors.

Standard Templating Kit (December 31, 2018)

  • Current status: End of life

Standard Templating Kit (STK) has been replaced with Magnolia Templating Kit (MTK), first released with Magnolia 5.4 on July 3, 2015. MTK is quicker to learn than STK and requires fewer skills. MTK is aimed at the increasing number of front-end developers who looked for something leaner and less time-consuming. MTK is front-end framework agnostic, which means you can integrate it with any modern framework such as Bootstrap or Foundation.

STK timeline:

  • 2018: End of life

  • 2017: Deprecation

  • 2015: Maintenance mode

  • 2009: First release

With the release of Magnolia 5.6, we no longer produce preconfigured bundles and webapps with the STK-based demo. If you still rely on STK, you can use it. However, you have to build a bundle or webapp with STK yourself.

Google Sitemap module and app (November 30, 2018)

The Google Sitemap module and app were deprecated with the release of Magnolia 6.0 and are no longer shipped in our bundles.

The module provided very narrow functionality and was not suitable for complex sites. It did not cater to common site configurations and structures.

Alternative: Create a sitemap with Solr

As Magnolia allows Solr-based searches, we recommend using a Solr-based sitemap instead.

WebDAV module (June 22, 2018)

  • Current status: Deprecated

The WebDAV module is now deprecated. The purpose of the module was to access the Magnolia repository through the WebDAV API, typically allowing users to edit resources and templates on the file system. The technology used in the module is obsolete: the WebDAV module depends on the HttpClient 3.x library, which reached end of life; Jackrabbit 2.16 removed the HttpClient3-based WebDAV API completely on May 16, 2018.

Deprecation means we stop bundling the WebDAV module with the product. You can still get the code from our Nexus repository, but we do not recommend using it anymore. The deprecated status lasts for one year. On June 20, 2019, we will remove the module from the product completely and donate it to the community on the Magnolia Forge. The latest documentation for the WebDAV module is available in the WebDAV module page of Magnolia 5.6 documentation.

See the WebDAV section of the Upgrading to Magnolia 5.7.x page where we describe the WebDAV module use cases and how to implement them using more modern ways.

NTLM Connector module (November 21, 2017)

  • Current status: Deprecated

The NTLM (NT LAN Manager) Connector module is no longer supported. The module provided single sign-on (SSO) functionality for Windows systems within a trusted domain environment.

Microsoft no longer recommends the use of NTLM in applications due to security constraints (see Microsoft’s Security Considerations for Implementers):

Implementers should be aware that NTLM does not support any recent cryptographic methods, such as AES or SHA-256. It uses cyclic redundancy check (CRC) or message digest algorithms (RFC1321) for integrity, and it uses RC4 for encryption. Deriving a key from a password is as specified in RFC1320 and FIPS46-2. Therefore, applications are generally advised not to use NTLM.

Following Microsoft’s recommendation, Magnolia ended support for the NTLM Connector module. This means we will not fix bugs related to the NTLM protocol. NTLM is no longer supported on any Magnolia version.

As a replacement, we recommend the LDAP Connector and CAS modules:

CAS module enables Central Authentication Service (CAS) in Magnolia. CAS is a single sign-on (SSO) Web protocol that permits a user to log in once to a system and then automatically gain access to all related systems to which they have been granted permission as per their credentials. This avoids the need to log into each system individually. The Magnolia CAS module handles authentication only. When a user logs into CAS, the system authenticates their identity to participating services because the user has been authenticated to CAS.

Activation module and Transactional Activation module (November 15, 2017)

Since Magnolia 5.6, the Activation module and Transactional Activation module have been deprecated in favor of the Publishing module and the Publishing Transactional module respectively.

Publishing is a refactored version of activation. The driving decision was to have a set of maintainable and extensible components. Another reason was to remove deprecated code. The core activation concepts remain the same. Although the transport layer still uses the HTTP protocol, publishing allows you to easily plug in any type of transport layer.

The new publishing implementation also allows you to define and use custom publishing operations with which you can publish content to a non-Magnolia public instance (for example, a custom API or a content delivery network).

Google Analytics module (November 15, 2017)

  • Current status: Deprecated

The Google Analytics module has been deprecated and removed from EE bundles. The module has modern replacements: Google Universal Visualization Analytics and Marketing Tags, which together provide the same functionality. Another reason for the deprecation of the module is that it used obsolete technology, namely third-party plugins that are no longer actively maintained.

Older versions of Internet Explorer (March 16, 2016)

  • Current status: Deprecated

On January 12, 2016, Microsoft ended support for Internet Explorer (IE) versions 8, 9 and 10. IE 11 is the last version of Internet Explorer and will continue to receive security updates, compatibility fixes and technical support. See Microsoft’s Support for older versions of Internet Explorer ended.

Following Microsoft’s decision, Magnolia ended support for IE 8, 9 and 10. This means we will not fix bugs related to these browsers. IE 8, 9 and 10 are no longer supported on any Magnolia version.

While Magnolia will continue to work with these older browsers, we recommend that you follow Microsoft’s advice and upgrade to the latest version of Internet Explorer for security reasons. We will continue to support IE 11 and Microsoft’s new browser Edge.

Check out the Certified stack page for a list of supported browsers.

Feedback