Changelog archives

This page contains the changelog information for previous years.

2024

December

Magnolia 6.3.2

Release notes for Magnolia 6.3.2 are available.

Magnolia 6.2.53

Release notes for Magnolia 6.2.53 are available.

November

Custom errors for geofencing

You can now set custom error messages for geofencing. The default message is "Restricted Content".

View from the Cockpit

geofencing

  1. Go to CDN > Geofencing.

  2. Optional If desired, add a custom error message. If left blank, the default message is "Restricted Content".

  3. Click Add rule to add a new geofencing rule.

    1. Select the countries from the menu.

    2. Add the host(s) you want to restrict in the Hosts field.

  4. Click Apply geofencing.

Resetting credentials

You can now trigger the reset process for both passwords and One-time passwords (OTPs) from the Cockpit.

For more, see Admin: Reset user credentials.

reset credentials

Magnolia 6.3.1

Release notes for Magnolia 6.3.1 are available.

Magnolia 6.2.52

Release notes for Magnolia 6.2.52 are available.

October

Magnolia 6.2.51

Release notes for Magnolia 6.2.51 are available.

Updated Helm chart version

We have updated the Helm chart version from 1.15.1 to 1.15.2.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

include::partial$changelog/2024/s_september.adoc[leveloffset=+2]gt stat

August

Updated Helm chart version

We have updated the Helm chart version from 1.14.1 to 1.15.0 for Magnolia 6.3 compatibility.

For more details on moving to Magnolia 6.3, see Upgrading to Magnolia 6.3.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

Magnolia 6.2.49

Release notes for Magnolia 6.2.49 are available.

Updated Helm chart version

We have updated the Helm chart version from 1.14.0 to 1.14.1.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

July

Magnolia 6.2.48

Release notes for Magnolia 6.2.48 are available.

Although Magnolia 6.2.47 was released, some changes introduced in 6.2.47 caused some issues. Because of this, we quickly released Magnolia 6.2.48 in order to resolve the issues. For more details, see the release notes mentioned above.

Updated Helm chart version

We have updated the Helm chart version from 1.13.0 to 1.14.0.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

June

Updated Helm chart version

We have updated the Helm chart version from 1.12.1 to 1.13.0.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

Magnolia 6.2.46

Release notes for Magnolia 6.2.46 are available.

Updated Helm chart version

We have updated the Helm chart version from 1.12.0 to 1.12.1.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

May

Segmented caching

Segmented caching breaks up large files or objects into smaller segments and caches each segment separately, helping optimize content delivery.

For more details, see CDN settings.

Magnolia 6.2.45

Release notes for Magnolia 6.2.45 are available.

April

Updated Helm chart version

We have updated the Helm chart version from 1.11.0 to 1.12.0.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

Set custom errors from Cockpit

You can now set custom error responses for your site from within the Cockpit instead of requesting via a support ticket.

For more details, see CDN settings.

Geofencing

DX Cloud’s geofencing lets you control access to your site content based on a user’s geographic location. This allows you to define country boundaries around your site’s access.

For more details, see CDN settings.

March

Magnolia 6.2.44

Release notes for Magnolia 6.2.44 are available.

Apply CDN restrictions

With Access control in DX Cloud, you’re able to configure rules that prohibit access to certain paths and extensions. This prevents any unintended visits to pages that should be internal or files that should be kept for certain groups or individuals.

For more details, see CDN settings.

Updated Helm chart version

We have updated the Helm chart version from 1.10.0 to 1.11.0.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

February

Magnolia 6.2.43

Release notes for Magnolia 6.2.43 are available.

Magnolia 6.2.42-sp1

A security vulnerability was identified for CKEditor 4.22.1. Magnolia provided a release to address this.

For more details, see Magnolia 6.2.42-sp1.

January

Organisations

You can now create business units called Organisations from the Cockpit.

For more details, see Organisations.

Editing user roles

For some Identity Provider (IDPs), groups are not supported. In light of this, you can now edit an IDP user’s roles from the Cockpit.

For more details, see User types and roles.

Magnolia 6.2.42

Release notes for Magnolia 6.2.42 are available.

2023

December

Updated Helm chart version

We have updated the Helm chart version from 1.9.0 to 1.10.0.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

Magnolia 6.2.41

Release notes for Magnolia 6.2.41 are available.

Updated Helm chart version

We have updated the Helm chart version from 1.8.3 to 1.9.0.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

November

Fastly Waiting Room

Premium feature

The Fastly Waiting Room is a feature to help you manage high traffic volume on your site and prevent site overload. It assigns a delay for new user requests which allows existing users to finish what they’re trying to do.

The Fastly Waiting Room:

  • Prevents site overload by intelligently handling the influx of new visitors.

  • Fairly distributes the site traffic so that each user has equal chance of access. During high-demand events, promotions, or sales, this can be highly useful.

  • Reduces server load so performance is not hindered.

For more details, see CDN settings.].

Updated Helm chart version

We have updated the Helm chart version from 1.8.2 to 1.8.3.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

October

Magnolia 6.2.40

Release notes for Magnolia 6.2.40 are available.

September

Magnolia 6.2.39

Release notes for Magnolia 6.2.39 are available.

Updated Helm chart version

We have updated the Helm chart version from 1.8.1 to 1.8.2.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

August

Magnolia 6.2.38

Release notes for Magnolia 6.2.38 are available.

Certificate updates

With recent changes, when creating a custom certificate, you need to generate a Certificate Signing Request (CSR) from within the Cockpit, which can now be customized. It’s also now possible to renew custom certificates. This is only applicable to certificates created after this feature was released.

For more on this topic, see Adding certificates with PaaS.

July

Updated Helm chart version

We have updated the Helm chart version.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

Magnolia 6.2.37

Release notes for Magnolia 6.2.37 are available.

June

Block IP: bit prefix detection

Now, when you block an IP from the Cockpit, it automatically detects and appends the appropriate bit prefix to the URL.

  • For IPv4, this is /32.

  • For IPv6, this is /128.

For more information, see Block IPs.

Magnolia 6.2.36

Release notes for Magnolia 6.2.36 are available.

Magnolia 6.2.35

Release notes for Magnolia 6.2.35 are available.

Updated Helm chart version

We have updated the Helm chart version.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

May

Magnolia 6.2.34

Release notes for Magnolia 6.2.34 are available.

April

April brings several improvements and updates related to DX Cloud.

Configure redirects settings

You can now configure redirects settings directly in the Cockpit. This allows you to choose either the default backend configuration or a frontend redirect server which will distribute traffic to the servers.

  1. In your Cockpit, go to Networking > Redirects.

  2. Click the Add redirect server button.

  3. In the dialog, choose the settings that best suit your needs.

    1. Choose the number of Replicas you would like. There is a minimum of 2 redirect server replicas.

      You may choose as many replicas as needed. However, if no more memory is available, the system rejects new replicas.

    2. Under Redirects server, choose Backend or Frontend .

      If choosing Frontend, you’ll need to pass the port number you want to use, such as 3000.

    3. Under Load balancing, choose Round Robin or Cookie based load balancing.

      redirects settings
      If choosing Cookie based, you’ll need to give the cookie a name. If you have sticky sessions enabled, this name must be the same as the value in the nginx.ingress.kubernetes.io/session-cookie-name ingress annotation in your values.yml file.

  4. Don’t forget to save your updates.

Configure redirect server
redirects configure redirect server

Once you’ve successfully added a redirect server by following the instructions in [Add redirect server] and saved your updates, the Add redirect server button in the Cockpit changes to Configure redirect server. Clicking this button opens a dialog where you can:

  • Edit the redirect server settings: Modify the existing configuration, such as the number of replicas, redirect server type, load balancing method, or cookie name (if applicable).

    Considerations 🤔

    You can adjust the following settings through the Configure redirect server dialog.

    Consider the following before acting:

    • Number of replicas

      • Increasing replicas: You can add more replicas to handle increased traffic, but sufficient memory must be available. If memory is insufficient, the system will reject the new replicas, leaving your configuration unchanged.

      • Decreasing replicas: Reducing the number of replicas may lower the system’s capacity to manage high traffic loads, potentially degrading performance during peak times.

    • Redirect server type

      • Switching between backend and frontend redirect servers alters how traffic is routed.

      • Switching to frontend: You must specify a valid port (e.g., 3000). If the port is misconfigured or conflicts with other services, traffic may be misrouted, or the service could become unavailable.

      • Switching to backend: This reverts to the default configuration, which may not suit your original intent (e.g., if frontend was chosen for performance or security reasons).

    • Load balancing method

      • Switching to Cookie-Based: You’ll need to provide a cookie name. If sticky sessions are enabled, this name must match the nginx.ingress.kubernetes.io/session-cookie-name in your values.yml file. A mismatch can break session persistence, causing users to lose session data or be routed inconsistently across servers.

      • Switching to Round Robin: This eliminates session persistence, which could disrupt applications that depend on consistent server routing (e.g., those maintaining user sessions).

      • Cookie name: Changing the cookie name requires updating the corresponding ingress annotation in your values.yml file if sticky sessions are enabled. Failing to synchronize these values disrupts session persistence. Additionally, altering the cookie name may invalidate existing sessions, potentially logging users out or resetting their session state.

  • Uninstall the redirect server: Remove the custom redirect server entirely, reverting to the default backend behavior.

    Considerations 🤔

    Choosing to uninstall the redirect server removes the custom configuration and reverts the system to the default behavior (backend redirect server).

    Consider the following before acting:

    • Loss of custom benefits: Any advantages gained from the custom redirect server (e.g., optimized traffic distribution, frontend-specific routing) will be lost.

    • Service disruptions: Applications or services that depend on the custom redirect server may encounter errors or downtime if the default backend configuration doesn’t suit their needs.

For more on this topic, check out our dedicated redirects section.

Magnolia 6.2.33

Release notes for Magnolia 6.2.33 are available.

Cockpit options for all CDN customers

All customers regardless of CDN can now avail of the following tabs in Content Delivery section of the Cockpit.

Previously, these features were only available to customers using Fastly as their CDN.

Redirects are now editable

You can now edit redirects directly from the Cockpit.

For more on this topic, check out our dedicated redirects section.

Fastly Image Optimizer

Customers using Fastly as their CDN can now make use of the Image Optimizer (IO) feature.

For more on this topic, check out our dedicated Fastly Image Optimizer page.

Fastly NextGen WAF

To further improve upon our WAF feature, we’re happy to announce the NextGen WAF has been released into production. See Fastly’s NextGen WAF page for more information from Fastly.

To see dedicated WAF information in the Cockpit, check out our dedicated section Security.

March

Magnolia 6.2.32

Release notes for Magnolia 6.2.32 are available.

Magnolia 6.2.31

Release notes for Magnolia 6.2.31 are available.

Magnolia 6.2.30

Release notes for Magnolia 6.2.30 are available.

Magnolia 6.2.29

Release notes for Magnolia 6.2.29 are available.

February

Create redirects from the Cockpit

You can now add redirects directly from your Cockpit.

  1. Go to Networking > Redirects.

  2. Select the desired Environment from the dropdown list.

  3. Add a single redirect or import a redirect CSV file.

    • Add redirect

    • Import redirects (CSV)

    1. Click Add.

    2. In the dialog, fill out the following.

      1. The Source URL. This is the place to redirect from.

      2. The Target URL. This is the place to redirect to.

      3. The Code. This is the http status code passed with the redirect. Only 3xx http codes are acceptable.

      4. Check Url with regular expression if the URL provided uses RegEx.

        (.*) Why use RegEx?

        Using regex for URL redirects offers several advantages:

        • It provides flexibility for matching patterns across multiple URLs.

        • It reduces the complexity of managing numerous redirects and allows dynamic handling of URL components.

        Using regex for URL patterns better preserve SEO rankings and minimize broken links by accurately mapping old URLs to new ones which enhances user experience and maintains optimal site integrity.

      5. Click Add to complete the action.

    add single redirect

    1. Click Upload/Modify.

    2. Click Choose File to import a CSV file for redirects.

      format
      Id,Source,Target,Code,IsRegex (1)
      1 Only 3xx http codes are acceptable. Id is optional. If an Id is provided, the system tries to match it with an existing record and update it. If blank or no match is found, a new record is created.
      example
      Id,Source,Target,Code,IsRegex
1,https:://www.example.com/[0-9]{2}(bar%7Cbaz),https://www.example.be/barbaz.html,308,true

    3. Select your file.

    4. Click Upload/Modify to complete the action.

    add multiple redirects via csv february2025
Check out the redirects docs here for more details on prerequisites and good-to-knows.

Create cache rules from the Cockpit

You can add cache rules from your DX Cloud Cockpit. Caching reduces requests to Magnolia which helps reduce heavy processing loads and improves performance.

The options in the Cache section aren’t available to satellite clusters.

Expand the image here to see the different parts of adding a rule in the Cockpit and is applicable to both cache types.

Rule anatomy

cache rule anatomy

  1. Add a new rule. Once you click this, a new rule is added to the top of the list.

  2. Naming your rule.

  3. Choosing the cache type which is Never or a duration (in minutes).

  4. Add a voter.

  5. Save changes to your rules. This saves changes to Author.

  6. Publish rules to production. This saves changes to Public.

  7. Move rule up or down. Remember the first to match is accepted.

  8. Delete a rule.

See the cache section on the CDN page for more on creating cache rules.

Updated Helm chart version

We have updated the Helm chart version.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

January

Magnolia 6.2.28

Release notes for Magnolia 6.2.28 are available.

Upload certificates

You can now upload your certificates directly in the Cockpit.

add cert
For more, check out the certificates section.

Updated Helm chart version

We have updated the Helm chart version.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

2022

December

Magnolia 6.2.27

Release notes for Magnolia 6.2.27 are available.

Updated Helm chart version

We have updated the Helm chart version.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

November

Updated Helm chart version

We have updated the Helm chart version.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

Block IPs from the Cockpit

Previously, you needed to make a support request to block a specific IP if you were using Fastly as your CDN. Now, you can block IPs directly from the Cockpit.

For instructions on how to do this, check out the guide here.

Magnolia 6.2.26

Release notes for Magnolia 6.2.26 are available.

October

Magnolia 6.2.25

Release notes for Magnolia 6.2.25 are available.

September

Rancher updates

Dashboard:

Recently, we upgraded to Rancher 2.6. For more on the new dashboard, check out our dedicated Rancher UI Dashboard page.

Copying secrets:

The All namespace is deprecated. However, we understand that you may still use it in some of your deployments. For details on migrating them to Rancher 2.6, see our cloning secrets page.

Magnolia 6.2.24

Release notes for Magnolia 6.2.24 are available.

Magnolia 6.2.23

Release notes for Magnolia 6.2.23 are available.

August

Updated Helm chart version

We have updated the Helm chart version.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

July

Magnolia 6.2.22

Release notes for Magnolia 6.2.22 are available.

Frontend environment metrics

You can now view Frontend environment metrics directly from the Cockpit.

view frontend metrics
For more, see Frontend metrics.

Magnolia 6.2.21

Release notes for Magnolia 6.2.21 are available.

Archetype version update 1.4

The maven archetype version has been updated to 1.4.

For more details, see Create a project using the Maven archetype.

Updated Helm chart version

We have updated the Helm chart version.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

June

Backup and Restore

You can now perform backup and restore operations directly from the Cockpit, giving you the opportunity to copy, download, and restore backups from a point-in-time.

For more details and tips on how to perform these operations, see our dedicated Dev operations (beta) guide.
dev operations overview

Magnolia 6.2.20

Release notes for Magnolia 6.2.20 are available.

Web Application Firewall (WAF)

You can now view log information from your Web Application Firewall (WAF) directly in the Cockpit.

See the Logs page for more details.

waf click request

Updated Helm chart version

We have updated the Helm chart version.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

May

Magnolia 6.2.19

Release notes for Magnolia 6.2.19 are available.

Updated Helm chart version

We have updated the Helm chart version.

The latest helm chart version is 1.17.0.

Check out the Magnolia helm repo for more details.

OpenSearch dashboards

OpenSearch is a powerful open-source search tool derived from Apache 2.0. You can use OpenSearch dashboards to visualize OpenSearch data. This is now available to you in your DX Cloud project.

April

Magnolia 6.2.18

Release notes for Magnolia 6.2.18 are available.

Cockpit

  • You can now view your deployment’s alerts through the Cockpit.

    active alerts

Archetype version update

The maven archetype version has been updated to 1.3.

For more details, see Create a project using the Maven archetype.

February

Magnolia 6.2.17

Release notes for Magnolia 6.2.17 are available.

Cockpit

January

Magnolia 6.2.16

Release notes for Magnolia 6.2.16 are available.

DX Cloud development

We added the shared database blueprint.

Cockpit

  • We added the environment’s URL in the home page.

    environments url

  • We added the Ingress log viewer.

    log viewer ingresses

  • We added the CDN domain log viewer.

    log viewer domains

2021

December

Magnolia 6.2.15

Release notes for Magnolia 6.2.15 are available.

Magnolia 6.2.14

Release notes for Magnolia 6.2.14 are available.

DX Cloud development

Cockpit

Feedback

PaaS

×

Location

This widget lets you know where you are on the docs site.

You are currently perusing through the Magnolia PaaS docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules