Changelog

CloudCannon Open Beta: Publishing Conflict Resolution

April 17th, 2025 | Changelog

Our Beta is now available to everyone!

The Publishing Conflict Resolution Beta introduces Publishing Conflict resolution in app, appearance and functionality improvements to the Publishing page, Status page, and Domains section, an updated Source Editor, and text diffs for unsaved changes in our editing interfaces.

We'd like to invite everyone to test our new features before the full launch. Taking part in this Beta is a great chance to let us know what’s working, and what could be improved for you and your team.

For more information about the features included in this Beta, please read our blog post or check out the Beta Changelog.

Using CloudCannon Beta

To use the CloudCannon Beta, you must switch your account to the Beta environment.

To enter the CloudCannon Beta:

1. Log in to CloudCannon and open your Site Dashboard.
2. Click on your avatar in the bottom left of the app.
3. Select Enter CloudCannon Beta from the Account Menu.
4. Confirm by clicking the Enter Beta button on the Try our new Beta model.
5. CloudCannon will reload.

Alternatively, you can click the Enter Beta button in the App Sidebar.

CloudCannon will enable the Beta environment. To return to the Main CloudCannon environment, click Exit CloudCannon Beta in the Account Menu.

Beta Feedback

If you have any questions or feedback regarding this Beta release, you can discuss them on our new CloudCannon Community or get in contact with our friendly support team.

---

This release improved our file server performance and reliability, added the Use Relative URLs when redirecting flag, comments for DNS records, and NS DNS records for subdomains.

It also addressed issues affecting the Snippets tool in the Rich Text WYSIWYG toolbar, and accepting transfers.

Features & Improvements

• Improved file server performance and reliability for better hosting.
• Added the Use Relative URLs when redirecting flag under Org Settings and Site Settings to use relative redirects rather than absolute redirects.
• You can now add a comment to DNS records, allowing you to write a reminder description of the record's purpose.
• You can now add an NS record for your Custom Domain subdomains.

Fixes

• Fixed an issue where CloudCannon would incorrectly include or exclude the Snippets tool from the Rich Text WYSIWYG toolbar.
• Fixed an issue where, when accepting a transfer to your Organization, CloudCannon would incorrectly show an error when the transfer had succeeded.

More points for partners

April 14th, 2025 | Changelog

This release added extra points for members of the CloudCannon Partner Program, and improved the messaging around Transfers, including what information CloudCannon sends with the transfer request.

Features & Improvements

• If you are a member of the CloudCannon Partner Program, you can now earn extra points based on your pricing plan and the number of additional seats you pay for (including users and client sharing).
• Added better messaging for Transfers, such as indicating which additional resources CloudCannon will also include in the transfer (i.e., Sites, Domains, Inboxes, or DAMs) are connected to the resource you selected.
• Transfers now include the Site name, and any connected Domain, Inbox, or DAM names.

Fixes

• Updated dependencies to patch security vulnerabilities.

New Inbox options for Client Sharing

March 21st, 2025 | Changelog

This release added new Inbox options for allowing Client Sharing users to log in to CloudCannon from a notification email.

It also addressed several issues, including those affecting MFA permissions, Organization-level Flag permissions, and form reCAPTCHA.

Features & Improvements

• Added the Use Client Sharing to view attached files option for existing Inboxes and the File attachment settings option for existing Inboxes.
  • Previously, Client Sharing users could not view form submissions in CloudCannon by following the link from the form submission notification email, as CloudCannon would require them to log in with a CloudCannon account.
  • Now, when you create a new Inbox target, you can enable the Use Client Sharing to view attached files option. CloudCannon will ensure all form submission notification emails use a link to the Client Login Page.
  • Additionally, you can toggle this option for existing Inbox targets using the File attachment settings option in the Inbox Context menu.

Fixes

• Fixed an issue where users with the org:settings:details:write permission could edit the Multi-Factor Authentication settings for an Organization. You must be a member of the Owners Permission Group to edit these settings.
• Fixed an issue where only members of the Owners Permission Group could see the Organization-level Flags settings. Users with the org:settings:details:write permission should be able to edit these flags.
• Fixed an issue where, in some cases, reCAPTCHA validation would pass incorrectly. CloudCannon will now forward form submissions that fail reCAPTCHA validation to the Error section of your Inbox.

CloudCannon Beta: Publishing Conflict Resolution

March 11th, 2025 | Changelog

Our new beta is now available to CloudCannon Partners!

The March 2025 Publishing Conflict Resolution Beta introduces basic conflict resolution in app, appearance and functionality improvements to the Publishing page and Domains section, and an updated Source Editor.

We’d like to invite our Partners to test our new features before the full launch. Taking part in this Beta is a great chance to let us know what’s working, and what could be improved for you and your team.

For a full description of our Beta features, check out our Beta Changelog.

Using CloudCannon Beta

To use the CloudCannon Beta, you must switch your account to the Beta environment.

To enter the CloudCannon Beta:

1. Log in to CloudCannon and open your Site Dashboard.
2. Click on your avatar in the bottom left of the app.
3. Select Enter CloudCannon Beta from the Account Menu.
4. Confirm by clicking the Enter Beta button.
5. CloudCannon will reload.

Alternatively, you can click the Enter Beta button in your Site Navigation.

The Beta environment is now enabled for any Site you open in CloudCannon. To return to the Main CloudCannon environment, click Exit CloudCannon Beta in the Account Menu.

Beta Feedback

If you have any questions or feedback regarding this Beta release, you can discuss them on our new CloudCannon Community or get in contact with our friendly support team.

General fixes

February 26th, 2025 | Changelog

This release addressed several issues, including those affecting Redis, new branch names, default behavior for Site inboxes, and inbox target options.

Fixes

• Fixed an issue causing a Redis out-of-memory error. For more information, please read our issue postmortem.
• Fixed an issue where, when creating a new branch, CloudCannon added quotation marks to the suggested Branch name if you used them in the Site name.
• Fixed an issue where CloudCannon would automatically assign new inboxes as the default inbox for a Site, if it was the only inbox connected.
• Removed Automate and Integromat as Inbox target options for new form inboxes.

CloudCannon Site authentication option

February 20th, 2025 | Changelog

This release added a new Site authentication option, the Branch Defaults page for Projects, and improved sorting options in the DAM browser.

It also addressed several issues, including those affecting allow_custom_markup behavior and screenshots.

Features & Improvements

• Added the CloudCannon Site authentication option.
  • You can now add CloudCannon authentication to your Site, where visitors to your website can only view the content if they are logged in to CloudCannon and have the site: read permission for that Site.
• Added the Branch Defaults page under Project Settings.
  • You can now configure the default settings for new branches, such as what Publish Mode a new branch should use, whether CloudCannon should delete the Site after a successful merge, and if the branch Site has an authentication method.
• Better sorting options for the DAM browser.

Fixes

• Fixed an issue where allow_custom_markup: true destroyed the content of elements with class="cms-embed".
• Fixed an issue where, in some cases, screenshots were the wrong size.

Site search fixes

February 14th, 2025 | Changelog

This release addressed an issue affecting the Site search function.

Fixes

• Fixed an issue preventing you from searching for Sites in the Site browser on the Sites page, Project page, and Assets page under Org Settings.

Organization UUID visibility

February 13th, 2025 | Changelog

This release added an Organization UUID to the API Keys page, better messaging during Site Syncing, and changed when the first Site backup occurred.

It also addressed several issues, including those affecting the Live Site Preview button and the CloudCannon Configuration File.

Features & Improvements

• Added the Organization UUID and Copy button to the API Keys page under Org Settings.
  • The API feature is currently in private beta. For more information, please contact our friendly support team.
• Better messaging when you first Sync your Site files.
• CloudCannon no longer creates a Site backup when you first create your Site, as no changes have been made to your files during Syncing.

Fixes

• Fixed an issue where the Live Site Preview button did not appear after your first successful build.
• Fixed an issue where, in some cases, you Internet browser tab would become unresponsive after opening the CloudCannon Configuration File.

New URL input configuration options

February 5th, 2025 | Changelog

This release added new URL input configuration options, better error messaging, and optimized screenshot fetching.

It also addressed several issues, including those affecting the File browser, new branch names in GitHub, and ExpressVPN browser extension behavior.

Features & Improvements

• Added new URL input configuration options to configure dropdown menu:
  • hide_link_to_file
  • hide_link_to_page
  • hide_link_to_email_address
• Better error messaging when CloudCannon requires SSO to access an Organization.
• Optimized the number of times CloudCannon fetches screenshots.

Fixes

• Fixed an issue causing the File browser to appear blank when the CloudCannon configuration file was misconfigured.
• Fixed an issue where CloudCannon would convert a / character in a new branch name into the - character before pushing it to GitHub.
• Fixed an issue where, in some cases, the ExpressVPN browser extension would inject scripts into CloudCannon editing interfaces.
• Updated dependencies to patch security vulnerabilities.

GitHub account and email change workflow improvements

February 4th, 2025 | Changelog

This release improves how CloudCannon handles GitHub accounts and updates the email change workflow. It addresses several issues caused by signing up to CloudCannon with GitHub's no-reply or standard email addresses.

Improved GitHub account management

Previously, GitHub's no-reply email addresses would prevent you from resetting your CloudCannon password.

Additionally, CloudCannon would require you to enter a password to accomplish some actions in the app, even though signing up with a standard GitHub email address does not require you to set a password to log in. This prevented you from:

• Changing your account password.
• Changing your account email address.
• Deleting an Organization.
• Deleting your Account.

The only way to address these issues was to use the Forgotten Password recovery flow, which added unnecessary friction and potential security concerns.

This release adds the following improvements:

• You can no longer use GitHub's no-reply email addresses to sign up to CloudCannon.
• If you sign up for CloudCannon via GitHub, you can no longer sign up to CloudCannon with an email address that is unverified in GitHub.
• If you sign up for CloudCannon via GitHub and do not set a password, CloudCannon will flag the account accordingly.
• CloudCannon actions requiring a password will no longer prompt you if you have not set one for your account.

Improved email change workflow

When you update the email address associated with your account, CloudCannon now requires you to verify access to the new email address. This ensures that only the owner of an email address can use it on CloudCannon.