Recent searches

in

Changelog

Subscribe with RSS to keep up with the latest changes.

On this page

Text alignment options for Rich Text Editors#

This release added an align option for Rich Text Editors, rebuilt the Inbox, Form, and Target setup screens, and clarified the copy for manually scheduled builds.

It also addressed several issues, including those affecting alignment controls in Rich Text Editors, input validation, Subscription banners, asset filtering for DAMs, SSO enforcement, and cache clearing for Sites on a subpath.

Features & Improvements

  • Added the align option to Rich Text Editors, allowing you to align blocks of text without configuring a class name for each alignment. CloudCannon saves alignment as a text-align style by default.
    • The align.left, align.center, align.right, and align.justify keys each enable a control in the toolbar.
    • The align.default key sets the alignment blocks of text have when no alignment is set, which allows a default other than left. Selecting that alignment in the toolbar removes any existing alignment.
    • The align.classes key sets a class name for each alignment instead of a text-align style. The styles for these classes need to be listed in your styles file to take effect outside of the input.
    • Alignment applies to list items as well as other blocks of text.
    • Existing HTML content keeps its inline text-align styles when it loads into a Rich Text Editor.
    • Deprecated the left, center, right, and justify keys in favor of align. Existing configuration using these keys continues to work.
Copied to clipboard
_inputs:
  description:
    type: markdown
    options:
      align:
        left: true
        center: true
        right: true
        justify: true
        default: center
  summary:
    type: markdown
    options:
      align:
        left: true
        center: true
        right: true
        classes:
          left: text-start
          center: text-center
          right: text-end
{
  "_inputs": {
    "description": {
      "type": "markdown",
      "options": {
        "align": {
          "left": true,
          "center": true,
          "right": true,
          "justify": true,
          "default": "center"
        }
      }
    },
    "summary": {
      "type": "markdown",
      "options": {
        "align": {
          "left": true,
          "center": true,
          "right": true,
          "classes": {
            "left": "text-start",
            "center": "text-center",
            "right": "text-end"
          }
        }
      }
    }
  }
}
  • Rebuilt the Inboxes, Forms, and Targets screens in Site Settings and Org Settings to make the relationship between them clearer.
    • The Inboxes page in Site Settings shows a warning when a Site has a default Inbox, explaining that every POST request to that Site is accepted and stored there.
  • Added explanatory labels and your Site's timezone to the manual build form on the Builds page in Site Settings. For more information, please read our documentation on scheduling your builds manually.
  • Updated the format of emails sent to Inbox Targets from Forms on your Site.

Fixes

  • Fixed an issue where the Left align control in a Rich Text Editor could only remove existing alignment, rather than explicitly aligning a block of text to the left.
  • Fixed an issue where selecting all the text in a Rich Text Editor and then changing the alignment left the icon on the alignment control showing the previous alignment.
  • Fixed an issue where the tooltip on the alignment control in a Rich Text Editor read Justify, rather than describing the control.
  • Fixed an issue where leaving a Number or Range Input empty triggered the min and max validation errors, even when required was not set.
  • Fixed an issue where the banner announcing a canceled Subscription stayed on screen after you reactivated that Subscription, until you refreshed the page.
  • Fixed an issue where filtering assets in a DAM returned every asset, rather than only the assets matching your search term.
  • Fixed an issue where removing the SAML configuration from your Organization did not clear the SSO requirement, so Team Members were still required to log in with SSO.
  • Fixed an issue where updating or deleting a Site served from a subpath did not clear the cache for the Site above it, so that Site continued to serve outdated content.
  • Fixed an issue where file_config entries ignored _inputs_from_glob, _structures_from_glob, and other _from_glob keys.
  • Fixed an issue where scrolling the list of Inboxes when connecting one to your Site added a duplicate New inbox option.
  • Fixed an issue where the Visual Editor preview sometimes showed outdated content for Editable Regions.
  • Fixed an issue where Mark as not spam did not move a form submission out of Spam if CloudCannon had automatically marked it as spam.
  • Fixed an issue where verifying an email Target with an expired link showed a decoding error, rather than sending you a new verification email.
  • Fixed an issue where Client Sharing could cause Syncing to fail if you did not specify an email address for commits.
  • Fixed an issue where renewing your Subscription Plan after cancelling did not remove the warning banner until you refreshed the page.
  • Updated dependencies to patch security vulnerabilities.

Billing Permission Group emails#

This release improved Site loading speed, added Subscription change emails for members of the Billing Permission Group, and added a record count and filter options to the Hosting Bandwidth Usage graph.

It also addressed several issues, including those affecting Site transfers to Client Organizations, the Hosting Bandwidth Usage graph, the Builds tab on your Site Dashboard, and image loading in Rich Text Editors.

Features & Improvements

  • Members of the Billing Permission Group will now receive emails when Subscription details change, rather than just Owners.
  • You can now use the environment variable CLOUDCANNON_BRANCH during a Site build to get the name of the Git branch.
  • Improved Site loading speed, particularly for large Sites.
  • Added a label showing the number of loaded records and filter options to the Hosting Bandwidth Usage graph.

Fixes

  • Fixed an issue where, when transferring a Site with connected Team Members or Custom Domains to a Client Organization on an extended Free Trial with fewer than three days left, CloudCannon would end the trial period and request credit card information.
  • Fixed several UI issues affecting the Hosting Bandwidth Usage graph.
  • Fixed an issue where, in some cases, the Builds tab on your Site Dashboard would fail to load after a Build Error.
  • Fixed an issue preventing the image_options.loading configuration in Rich Text Editors from working.
  • Updated dependencies to patch security vulnerabilities.

Sync Errors on the Site Dashboard#

This release added Sync Errors and suggested resolution steps to the Site Dashboard, a new build error suggestion for Sites using Yarn or pnpm with a version of Node that is not preinstalled, and standardized date display and formats across CloudCannon.

It also addressed several issues, including those affecting the Hosting Bandwidth widget in the Organization Browser, CloudCannon in Safari version 27, and Select and Number Inputs.

Features & Improvements

  • The Site Dashboard now shows Sync Errors and suggests steps for resolution.
  • Added a build error suggestion for Sites using a non-preinstalled version of Node, and Yarn or pnpm.
  • Standardized display and formats for dates across the app UI and file formats.

Fixes

  • Fixed an issue where, in some cases, the Hosting Bandwidth widget on an Organization card in the Organization Browser would incorrectly show “Billing overdue”.
  • Fixed an issue causing CloudCannon to freeze in Safari version 27.
  • Fixed an issue where autocomplete for Multi-factor Authentication codes did not work on mobile.
  • Fixed an issue where the tools in a Browser modal (e.g., Snippets Browser modal or Array Item Browser modal) did not stick to the top when scrolling.
  • Fixed an issue where, in some cases, you could not type in a Select Inputs to search options.
  • Fixed an issue where Number Inputs did not accept min: 0.
  • Updated dependencies to patch security vulnerabilities.
Open in a new tab