Blossom module release notes
Magnolia 6 UI compatibility
The Blossom module is generally compatible with Magnolia 6 UI apps, including the 6 UI Pages app. For more details, see Blossom module: Updating to Magnolia 6.2. |
Version 3.7.4
Released on August 5, 2025.
BLOSSOM-339 Update dependency to the latest Magnolia core and bundles
Version 3.7.3
Released on August 16, 2024.
This version addresses security issues in the Spring framework. See BLOSSOM-333 for details.
Version 3.7.2
Released on May 15, 2024.
This version fixes an exception in the publication workflow of the legacy Pages app. See BLOSSOM-331 for details.
Version 3.7.1
Released on April 15, 2024.
This version only updates Spring Framework to 5.3.34. See BLOSSOM-330 for details.
Version 3.7.0
Released on March 28, 2024.
You can resolve Blossom dialogs at render time to make use of the component’s model (its dialog fields in the template script or controller).
This is possible due to refactoring of the DialogDefinition
creation by removing the DialogCreatorDefinitionDecorator
.
See BLOSSOM-322 for more details.
Special thanks to Björn Eschle for his contribution.
Version 3.6.7
Released on August 5, 2025.
BLOSSOM-339 Update dependency to the latest Magnolia core and bundles
Version 3.6.6
Released on August 16, 2024.
This version addresses security issues in the Spring framework. See BLOSSOM-333 for details.
Version 3.6.5
Released on April 15, 2024.
This version only updates Spring Framework to 5.3.34. See BLOSSOM-330 for details.
Version 3.6.4
Released on February 23, 2024.
This version only updates Spring Framework to 5.3.32. See BLOSSOM-328 for details.
Version 3.6.3
Released on July 26, 2023.
This version updates Guice to 5.1.0. See BLOSSOM-315 for details.
Version 3.6.2
Released on May 12, 2023.
This version only updates Spring Framework to 5.3.27. See BLOSSOM-312 for details.
Version 3.6.1
Released on March 23, 2023.
This version updates Spring Framework to 5.3.26 (BLOSSOM-311) and fixes in issue where the SpringNode2BeanTransformer
referenced the removed parent constructor (BLOSSOM-308).
Version 3.6.0
Released on June 24, 2022.
Since this version, @DialogFactories
and @TabFactories
can inject Spring-managed beans, as well as parameters resolved through Spring HandlerMethodArgumentResolvers
(including custom resolvers).
See BLOSSOM-295 for details.
Special thanks to Björn Eschle for his contribution.
Version 3.5.1
Released on June 16, 2022.
This version only updates Spring Framework to 5.3.20. See BLOSSOM-301 for details.
Version 3.5.0
Released on April 28, 2022.
Since this version, @DialogFactories
and @TabFactories
support 6 UI definitions. See BLOSSOM-290 for details.
Version 3.4.7
Released on November 15, 2021.
This version merges the samples
Git repository into the blossom
repository and enables a regular, automatic CVE scan for known vulnerabilities.
The following dependencies have been updated:
-
Spring framework to 5.1.18.RELEASE.
-
Spring webflow to 2.4.8.RELEASE.
-
Hibernate validator to 6.1.5.Final.
See BLOSSOM-268 for details.
Version 3.4.6
Released on October 9, 2021.
This version fixes a critical issue affecting the 6 UI Pages app, injecting incorrect node and contextual information into dialogs. See BLOSSOM-282 for details.
Version 3.4.5
Released on August 3, 2021.
This version, brought about by BLOSSOM-276, expands support for the Magnolia 6 UI framework:
-
Node
and node path are now available inDialogCreationContext
, as well as for injection into dialog factories. This facilitates migration to 6.2 and the 6 UI Pages app. -
DialogCreationContext#getItem()
is now deprecated without replacement. -
The
formDialogPresenterClass
in the configuration of the module remains ignored in the 6 UI apps.
Version 3.4.4
Released on November 12, 2020.
This version improves observation, by filtering out JCR changes in content versions. Read on in the 6.2.4 release notes.
-
BLOSSOM-278 CLONE - Version events fired in all workspaces
Version 3.4.3
Released on July 15, 2020.
This version furthers the improvements integrated in version 3.4.2 by enabling dialogs also in custom 5 UI content apps, in addition to support for dialogs in the 5 UI and 6 UI Pages apps. Previously, app names were used primarily due to missing APIs exposing the current AppDescriptor and its type. This limitation in the UI framework has been lifted with MGNLUI-5964 - Expose running app contexts via AppController.
This module version requires Magnolia 6.2.2 or later. |
-
BLOSSOM-274 Dialog creation is no longer supported in custom content apps
Version 3.4.2
Released on June 11, 2020.
This version fixes an error with Blossom definitions in the Definitions app.
In relation to definitions, DefinitionMetadata
’s module name is now inferred as blossom
when @Template
and @DialogFactory
’s id
are not formed as <module>:<name>
.
This does not impact the coordinates in the registries.
The id
attribute is fixed and prevails in Blossom registrations.
Finally, this module update removes a minor definition issue where a non-existing type
property was configured (and ignored) in Blossom’s renderer configuration.
-
BLOSSOM-272 DialogCreatorDefinitionDecorator is wrongly applied in Definitions app, may produce NPEs
Version 3.4.1
Released on June 10, 2020.
Besides improving definition logging, this release fixes an issue affecting the DialogCreationContext
attributes.
The attributes were not initialized properly in the Magnolia compatibility Pages app.
-
BLOSSOM-267 Harmonize the definition logging for Blossom
-
BLOSSOM-269 DialogCreationContext attributes are not initialized
Version 3.4
Released on May 19, 2020.
-
BLOSSOM-257 The module has been adapted for the 6.2 branch of Magnolia.
-
It has been migrated to the 6 UI framework (non-compatibility), but old-style compatibility dialogs can still be registered.
-
The module provides support for simple dialogs configured by code.
-
Dialog factories are forward-compatible with Magnolia 6.2.
-
-
BLOSSOM-261 Usages of the
SiteAwareFreemarkerRenderer
extension (deprecated and removed) replaced with the equivalent site-aware wrapper.-
SiteAwareFreemarkerTemplateViewRenderer
is now deprecated and kept only for backward compatibility. The current equivalent is theFreemarkerTemplateViewRenderer
. Use theSiteAwareFreemarkerTemplateViewRendererFactoryBean
instead. -
The
FactoryBean
does the wrapping of theFreemarkerTemplateViewRenderer
withSiteAwareRendererWrapper
and generalizes its generic typing to theRenderer
interface. -
Similarly for the non site-aware
FreemarkerTemplateViewRenderer
, it must now be registered by its respective factory-beanFreemarkerTemplateViewRendererFactoryBean
. Its constructor now injects Magnolia’sFreemarkerHelper
andRenderingEngine
, and we don’t expose these to Spring by default.
-