Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.
Magnolia International Ltd. supports each major release of Magnolia for at least two years after the release of the following major version. For example, Magnolia 4.4 is supported for at least two years after the release of 4.5.
When the supported life of a version ends, we announce end of life (EOL) on this page. We do not provide formal support, bug fixes or security fixes for Magnolia instances that run an EOL version of the product. However, we do our best to assist customers who encounter issues with EOL versions of Magnolia. Enterprise customers who run an EOL version can use their support contract to verify issues, ask questions about the product, and get help with migration to a newer, supported version of the product.
|Supported||Released||End of life|
|Unsupported||Released||End of life|
Versions earlier than those listed above are also in end-of-life status.
Magnolia 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. Technology used in the module is obsolete: the WebDAV module depends on an old HttpClient 3.x library which has reached end of life; and Jackrabbit 2.16 removed the HttpClient3-based WebDAV API completely on May 16, 2018.
Deprecation means that we stop bundling the WebDAV module with the product. You can still get the code from our Nexus repository but we don't 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. Latest documentation for the WebDAV module is available in the Magnolia 5.6 documentation space on the WebDAV module page only until the end of support of the 5.6 branch.
The Magnolia 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:
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. https://msdn.microsoft.com/en-us/library/cc236715.aspx
Following Microsoft's recommendation, Magnolia ends 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.
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.
The Standard Templating Kit (STK) was deprecated on September 15, 2017 and reached end of life on December 31, 2018.
The replacement for STK is 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. MTE is front-end framework agnostic, which means you can integrate it with any modern framework such as Bootstrap or Foundation.
With the the release of Magnolia 5.6 we have stopped producing preconfigured bundles and webapps with the STK based demo. If your still rely on STK, you can use it. However, you have to build a bundle or webapp with STK yourself.
Please follow one of these links:
On January 12, 2016, Microsoft ended support for Internet Explorer versions 8, 9 and 10. Internet Explorer 11 is the last version of Internet Explorer, and will continue to receive security updates, compatibility fixes, and technical support. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support
Following Microsoft's decision, Magnolia ends support for IE 8, 9 and 10. This means we will not fix bugs related to these end-of-life 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.
Magnolia will continue to support IE 11 and Microsoft's new browser Edge.
Check out the Certified stack page for the list of supported browsers.
You can raise issues for supported versions of Magnolia at https://jira.magnolia-cms.com. Getting a fix may require upgrading to a version that includes the fix. Critical security fixes are backported to currently supported versions.
To get extended support for your EOL version of Magnolia, contact firstname.lastname@example.org. Support for EOL instances is provided only under special terms agreed with the client.
Magnolia International provides assistance upgrading your EOL version to a supported version. Contact email@example.com to get help. Our experienced Services team will help manage and implement a smooth migration.