Changelog

This release added spam, file upload, and attachment link controls to Forms, rebuilt the Single Sign-On and Git Provider pages under Org Settings around tabs, and added warnings for failed syncs or deploys to the Cards in your Sites Browser.

It also addressed several issues, including those affecting Site Mountings that use another Site's build output, Git Provider connections with a failed token refresh, and Inbox captcha providers.

Features & Improvements

• Added Spam protection settings to each Inbox Target, allowing you to stop submissions that our spam detection flags, or that match our spam blocklist, from being sent to that target. The Do not send submissions marked as spam and Do not send submissions matching our spam blocklist options are on the Targets tab of an Inbox, under Org Settings.
  • Both options are off by default for most Targets, so submissions marked as spam are sent.
  • When the Target is an email address, both options are locked on. CloudCannon will never forward spam to an email address, because doing so would eventually get CloudCannon emails blocked by your email provider.
• Added the Accept file uploads setting to the Inbox settings page under Org Settings, allowing you to reject any submission that carries a file.
• Added Links to attached files settings to each Inbox Target, allowing you to choose whether links for files uploaded via Form submission open in CloudCannon or in the simplified Client Sharing Site. For more information, please read our documentation on Client Sharing.
  • Users who access CloudCannon via a Client Sharing password can now view files from a Form submission. This will respect the Site you select, even if an Inbox is shared by multiple Sites.
  • CloudCannon will still list Sites without a Client Sharing password set, but prevent you from selecting them.
• Added support for Slack Workflow Builder URLs on Slack Inbox Targets, allowing you to start a Slack workflow with each submission instead of posting a message to a channel. CloudCannon sends the fields from each submission, and Slack matches them by name to the variables your workflow declares.
• Added tabs to the Git Provider pages under Org Settings.
  • The Authentication tab shows your connected account as a Card, and displays a warning if CloudCannon cannot fetch that account.
  • The Sites tab lists every Site that syncs its files from that Git Provider.
  • GitHub Enterprise Server and Self-hosted GitLab keep their server configuration on a Settings tab.
  • The Danger Zone tab allows you to disconnect your Git Provider.
• Added a Reconnect button to the Git Provider pages under Org Settings, allowing you to reauthorize a connected account without disconnecting it first.
• Improved warning copy for Git Provider settings forms so that failures appear beside the field that caused it.
• Added tabs to the Single Sign-On pages under Org Settings when successfully configured.
  • The Details tab shows the values CloudCannon generates for your Identity Provider, and the Settings tab shows the values you configure.
  • The Danger Zone tab allows you to turn off Single Sign-On for your Team Members.
• Updated the setup fields on Single Sign-On page under Org Settings.
  • The setup steps now cover adding CloudCannon to your Identity Provider, entering your Identity Provider's details, and choosing what happens for new Team Members.
  • The advanced fields are listed with the rest of the form rather than hidden behind a toggle.
• Updated the Site Cards in the Sites Browser to show warnings for failed syncs or deploys. A Site whose sync previously failed without a Git Provider error appeared to have synced normally.
• Added a deploy row to the Cards in your Sites Browser for Sites that deploy their build output, showing when the Site last deployed, or that its last deploy failed.
• Updated the Body field on a Pull Request to a Markdown Input by default, with a toolbar for bold, italic, links, formatting, blockquotes, and bulleted and numbered lists.
• Added the full input configuration to the _inputs key in pull_request_templates, allowing you to configure the Title and Body inputs in a Pull Request Template the same way you configure any other input. For more information, please read our documentation on configuring a Pull Request Template.
• Updated the Source Editor to accept an autocomplete suggestion in your Configuration File when you press the Tab key.
• Updated the Invite Team Members modal on the Team page to allow you to add someone to more than one Permission Group on any Subscription Plan.
• Changed the Inbox and Inbox Target update endpoints in the CloudCannon API so that every field is optional, allowing you to send only the fields you want to change.
• Added allow_uploads to the fields you can set on an Inbox through the CloudCannon API, and removed monthly_quota.

Fixes

• Fixed an issue where, when Team Members had already authenticated by another method, signing in through Single Sign-On would fail. CloudCannon now accepts a stronger authentication method than the one named in your AuthnContext setting, instead of requiring an exact match.
• Fixed an issue where the Name ID Format field in your Single Sign-On settings accepted values other than email address.
• Fixed an issue where a Team Member who signs in through Single Sign-On could not delete their account or their Organization, as CloudCannon would ask for a password they did not have.
• Fixed an issue where a Site Mounting that uses another Site's build output was rejected on the Team Plan. Build output mounts are now accepted on any plan that includes advanced Site Mountings.
• Fixed an issue where an Inbox accepted an unrecognized captcha provider through the CloudCannon API, which then never ran.
• Fixed an issue where failed sync warnings on Sites in your Sites Browser would display the date of the last successful sync, so a Site that had been failing for days could appear to have failed moments ago.
• Fixed an issue causing the graph on the Publishing tab of a Project to overflow.
• Fixed an issue where, after an access token failed to refresh, CloudCannon would not automatically retry a Git Provider connection, so the connection went stale until someone reconnected it. CloudCannon now retries a failed refresh, waiting longer after each failure.
• Fixed an issue where CloudCannon allowed Team Members who did not have write permissions to edit the content of fields on the Git Provider pages under Org Settings, but did not allow them to save those changes. The Self-hosted GitLab server settings are now read-only for those team members, and the Danger Zone tab is hidden.
• Fixed an issue where the GitHub Enterprise Server and Self-hosted GitLab setup forms appeared editable on Subscription Plans that did not support those features. These pages now appear disabled with the upgrade prompt at the top of the page.
• Fixed an issue where CloudCannon reverted a searchable dropdown field to its placeholder text after a search, instead of showing the option you had selected.
• Updated dependencies to patch security vulnerabilities.

This release improved Pull Requests by adding Markdown formatting to the Pull Request body and a shortcut to edit your Pull Request templates in Configuration Mode.

It also addressed several issues, including those affecting line breaks in Pull Request descriptions, dropdown menus, and Editable Regions on Nuxt Sites.

Features & Improvements

• Changed the default Input for the body of a Pull Request to a Markdown Input, allowing you to format your Pull Request description without writing Markdown syntax by hand. The toolbar has controls for bold, italics, links, paragraph and heading formats, blockquotes, bulleted lists, numbered lists, and removing formatting.
• Added an Edit Pull Request Templates button to the Publishing page, allowing you to configure your Pull Request templates without opening your CloudCannon Configuration File in the Source Editor. This button is visible when Configuration Mode is on. For more information, please read our documentation on configuring a Pull Request template.
• Improved the configuration options for Pull Request templates in Configuration Mode.
  • The _inputs key accepts title and body entries only, which matches the fields available on a Pull Request.
  • The title and body entries under _inputs accept the full range of Input configuration options.
  • The body key uses a Markdown Input, and the template_path key is available when you add a new template.

Fixes

• Fixed an issue where pressing Shift + Enter in the body of a Pull Request showed a literal <br /> in the Pull Request description, rather than a line break.
• Fixed an issue where clicking away from an open dropdown menu cleared the name of the selected option, leaving the menu looking empty.
• Fixed an issue where client-side hydration on Nuxt Sites stopped some Editable Regions from working in the Visual Editor.
• Updated dependencies to patch security vulnerabilities.

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.

_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.