On November 7th, CloudCannon will remove support for the Legacy version of our app. Thank you so much to everyone who provided feedback. We have addressed all issues brought to our attention.
This release added the Authn Context field after SAML configuration and updated the default SAML signing algorithm and SSL minimum TLS version.
Features & Improvements
You can now edit the Authn Context field without removing your SAML configuration.
The default signing algorithm for SAML is now SHA256. Existing SAML configuration using SHA1 is not affected by this change.
The default Minimum TLS version for SSL is now 1.2. Existing SSL configuration using TLS 1.0 is not affected by this change.
This release added several improvements to the onboarding and initial Site creation process, the appearance of the Sites and Projects pages, Jekyll codeblock behavior, and error messages after logging in fails.
It also addressed several issues, including those affecting new Collection items, app behavior when using two tabs, SSO, images in your DAM, Site icons, and uneditable snippets.
Features & Improvements
Hid non-essential UI elements during initial Site setup.
Updated the onboarding survey for new users setting up their first Site.
Updated the appearance of the Sites list page when you have no Sites.
Updated the appearance of the Projects list page when you have no Projects.
For Jekyll Sites, CloudCannon no longer adds {%raw%} and {%highlight%} tags to your codeblocks automatically if you include templating in your Markdown. Please use the Raw or Highlight snippets.
Clearer error messages when logging in fails.
Fixes
Fixed an issue where, in some cases, CloudCannon did not apply your Collection configuration to new Collection items unless you refreshed the app.
Fixed an issue causing unexpected behavior when deleting or saving files on the same Site in two different tabs on the same Internet browser.
Fixed an issue where the Setup SSO prompt would persist after you had finished setting up SSO.
Fixed an issue where CloudCannon did not apply mime_type and expandable to images in your DAM.
Fixed an issue causing Site icons to break when you used relative URLs with a DAM.
Fixed an issue where, in some cases, CloudCannon would add extra non-breaking spaces around uneditable snippets protecting custom markup.
Updated dependencies to patch security vulnerabilities.
This release added support for Cloudflare Turnstile CAPTCHA, missing keys to the CloudCannon configuration file in the Data Editor, and improved accessibility and error messaging.
It also addressed several issues, including those affecting draft files on Jekyll Sites, Cards in the Structures and Snippets modals, cloning file behavior, disabling file actions, and the Asset browser.
For Sites using Live Data and Configuration Editing, you can now see new Schemas in your Collection browser+Add button dropdown before saving the Schema
Added the file_config, _snippets_imports, and commit_templates keys to the CloudCannon configuration file when you open it in the Data Editor.
Improved accessibility on the Add a new Site page by adding keyboard controls when you choose whether to use a template or your own files, and when uploading files for a new Site from your computer.
Better error messaging when setting up an existing CloudCannon account with SAML.
Better error messaging when you reference a Schema that does not exist.
Better error handling when you make a duplicate Pull Request.
Fixes
Fixed an issue where publishing a draft file on a Jekyll Site would not prompt you to rename the file with a date.
Fixed an issue where Cards in the Structures and Snippets modals did not use Gallery view by default, despite having images configured.
Fixed an issue where, in some cases, after you cloned a file CloudCannon would incorrectly open a separate file.
Fixed an issue where, in some cases, cloning a file a file would cause multiple file Cards for that file to appear in the Collection browser.
Fixed an issue where a blank file would persist in your Collection browser when you created a new file with an incorrect Schema name.
Fixed an issue where disabling file actions in a Collection would not disable the Delete option.
Fixed an issue where CloudCannon did not use the name of a Collection as the tab title in your Internet browser.
Fixed an issue where opening a link for the Organizations List before logging in to CloudCannon would result in a 404 error after logging in.
Fixed an issue where, in some cases, the Asset browser would attempt to use a broken external URL as the folder path.
Fixed an issue where clicking the Cancel button did not close the upload modal.
Fixed an issue where, if you had permission to Read the Source Syncing page under Site Settings and the Subscription page under Org Settings, CloudCannon would allow you to click buttons and produce a permission error, rather than displaying a Read-only page.
Fixed an issue where CloudCannon would reorder the values for Select and Multiselect inputs rather than respecting the order in your input configuration.
This release improved the appearance of the Snippet and Structure picker modals, updated Data Panel behavior in the Content Editor, and moved the Enter Legacy button.
It also addressed several issues, including those affecting filenames in the Review changes modal, Code Blocks in Rich Text inputs, automatic detection for templating files, and Site loading.
Features & Improvements
Cards in the Snippet picker modal and Structure picker modal now only display a gallery image if the Snippet or Structure has a gallery image or icon configured.
In the Content Editor, the Data Panel now opens immediately after adding a link, snippet, or image.
Moved the Enter CloudCannon Legacy button from the App Sidebar to the Account Menu.
Fixes
Fixed an issue where opening the Review changes modal would clear the filename of recently added, cloned, or renamed files.
Fixed an issue where, in the Google Chrome browser, you could not use Code Blocks inside a Rich Text input.
Fixed an issue where you could not use the Esc keyboard key to close the several modals.
Fixed an issue where CloudCannon could not automatically detect the URL or find metadata for templating files (e.g., liquid, astro).
Fixed several issues preventing Sites from loading.
This release added new options to the billing graphs for users on legacy plans.
It also addressed several issues affecting uploads_filename configuration, Collection items for Link to a page, and Client Sharing file globs.
Features & Improvements
Added "This Billing Period" and "Last Billing Period" options to the billing graphs on the Organization Dashboard for users of legacy plans.
Fixes
Fixed an issue preventing you from defining the input path uploads_filename outside of your configuration file at other levels of the configuration cascade.
Fixed an issue where some Collection files did not appear when using Link to a page in CloudCannon.
Fixed an issue preventing you from configuring file globs for Client Sharing users.
This release added better error messaging and the Metadata URL field to the Single Sign-On page.
It also addressed several issues affecting icons in Select inputs, picker preview configuration, and updated dependencies.
Features & Improvements
Better error messaging when creating a Pull Request that already exists.
Added the Metadata URL field to the Single Sign-On page under Org Settings.
Fixes
Fixed an issue where you couldn't select an option in a Select input by clicking on the icon.
Fixed an issue where, when viewing the CloudCannon configuration file in the Data Editor, the Icon dropdown under Collection Display did not display icons correctly.
Fixed an issue preventing you from configuring text and image simultaneously in picker preview.
Updated dependencies to patch security vulnerabilities.
This release added a new default Permission Group, commit message configuration to the CloudCannon configuration file in the Data Editor, and improved error handling and accessibility.
It also addressed several issues, including those affecting building, the CloudCannon configuration file, Client Sharing, Rich Text inputs, unsaved Collection files.
Features & Improvements
Added a new default Permission Group called "Billing". This Permission Group allows members to edit Billing settings for a Site. You can be a member of this group as well as the Editor, Technical Editor, or Developer group.
Added commit message configuration when you open the CloudCannon configuration file in the Data Editor.
Improved error handling for misconfigured data_config entries.
Improved accessibility for the build suggestions section on the Status page after a failed build.
Fixes
Fixed an issue preventing you from building your Site if you set SYNC_PATHS to a large directory.
Fixed an issue where, if you enabled the Require rebuild on branch setting, CloudCannon would incorrectly trigger a build before switching branches.
Fixed an issue where changes made to the CloudCannon configuration file did not persist between CloudCannon and CloudCannon Legacy.
Fixed an issue where Client Sharing users could not use the Visual Editor.
Fixed an issue where, in some cases, Markdown and HTML inputs would become misconfigured.
Fixed an issue where you could not use File inputs in a new, unsaved Collection file.
Fixed an issue preventing you from uploading a file to your DAM with a + character in the filename.
Live data and configuration editing and the Unified Configuration file format are now available for everyone on CloudCannon! Thank you to everyone who assisted in our September 2024 Live Configuration Beta. Your feedback is always valuable to our team.
All new Organizations will now use the Unified Configuration file format by default. Existing Organizations can opt into live data and configuration editing or Unified Configuration on the Org-level or Site-level by following the Unified Configuration Migration Guide.
The Legacy version of CloudCannon (which does not support live data and configuration editing or Unified Configuration) is still available for a short time. CloudCannon will support the Legacy app until October 31st, 2024. If you have any feedback about this change, please get in touch with our support team or contact us through your dedicated Slack channel.
This release added a warning if CloudCannon detects that you need to enable Git LFS, new features for Select and Multiselect inputs, UI elements for returning to CloudCannon Legacy, UI improvements to the Status and Flags pages, and better messaging in-app.
This release also addressed several issues affecting Object inputs and the CloudCannon configuration file.
Features & Improvements
CloudCannon will now warn you if you have a /.gitattributes file but have not enabled Git LFS on the Source Syncing page in your Site Settings. This warning will appear in the new Needs Attention section on the Status page.
Groups within Structures are now configured using the values.groups key to avoid a common source of misconfiguration.
You can now configure whether an Object input is tabbed using options.subtype: tabbed value.
Added a Clear button, a loading spinner, and icons to Select and Multiselect inputs.
You can now populate Select and Multiselect inputs with a filtered subset of values from Collections, data files, or data sets. Most JSONPath expressions are supported here. For example, the following Multiselect input will only provide values from the Posts collection where the author key is equal to james.
james-author-profile.yml
copied
_inputs:james_posts:type: multiselect
label: James
options:values:"collections.posts[?(@.author == 'james')].title"
CloudCannon now uses the Collection preview options for Select and Multiselect inputs populated by a Collection.
You can now configure the full set of preview options for Select and Multiselect inputs, including icon, metadata, gallery, subtext, image, and tags. Additionally, the new keys view, picker_view, and picker_preview are now available.
Partner Organizations can select whether new Client Organizations use the Legacy app by default during Organization creation.
Client Sharing users can control if they are in the Legacy environment using the Enter Legacy button in the App Navigation sidebar.
This button enables a Site-wide flag that affects all Client Sharing users.
Client Sharing users cannot open Sites using the Unified Configuration file format while in the Legacy app.
The Summary tab on the Status page now has a Needs attention notice if CloudCannon detects an issue with your Site configuration, a Suggestions section, and a link to Support. The most recent Sync and Build are on the right of the page.
The Flags page now has sections for General, Upgrade to Unified Configuration, Input naming conventions, and Legacy options.
Flags available under the General section include the Disable setup prompts flag.
Flags available under the Upgrade to Unified Configuration section include the Enable live configuration and data reloading and Use Unified Configuration flags. This section will not appear if your Site is already using the Unified Configuration file format.
Flags available under the Input naming conventions section include the Infer Select values from input key and Infer Structure from input key flags.
Flags available under the Legacy options section include the Image size attributes default behavior and Legacy collections value key flags.
Better messaging when discarding unsaved changes.
Better messaging in the Data Editor when you set your source in the CloudCannon configuration file.
Live data and configuration editing
You can now see your updates affect CloudCannon live whenever you edit your data and configuration files without waiting for a build.
When you create a new file in a Collection, Select inputs populated by that Collection will display the new file before you save it.
When you update your Input, Structure, or Schema configuration, you can see those changes the next time you open a file in an editing interface.
CloudCannon applies a Schema to a file when first opened during an editing session. You will not see live changes from an updated Schema if a file is already open with unsaved changes.
Live data and configuration editing is available by default on all Sites with the Unified Configuration file format.
You can enable live data and configuration editing on your existing Sites using the Enable live configuration and data reloading flag on the Flags page. For more information, please read steps one and two of our Unified Configuration Migration Guide.
The Unified Configuration file format
The Unified Configuration file format for your CloudCannon configuration file simplifies Site setup.
When you create a Site using the Unified Configuration file format, CloudCannon requires less information from you. It also uses the same configuration options regardless of SSG.
CloudCannon can now detect your Collections immediately after syncing your files, regardless of SSG.
You can now manage your content in CloudCannon before your first build.
Loading your Sites in CloudCannon is now faster.
CloudCannon now provides suggestions for your build configuration settings based on your files and SSG, including your command line options and environment variables.
Added the CloudCannon Configuration Path field to the Editing page under Site Settings for specifying the location of your configuration file. You can no longer configure this path in your environment variables.
This setting is important for Sites using Headless Mode or which do not build using CloudCannon.
You can now enable Headless Mode if you want to create a headless Site on CloudCannon. Headless mode disables building and hosting for your Site and streamlines your Site Settings by removing settings you don't need.
Headless Mode is useful if you want to create externally hosted static websites with visual editing, server-side rendering (SSR) or other server-side functions, or externally hosted APIs while still using CloudCannon as your primary CMS.
The Site Details page now includes fields for your Site Name, Mode, and Static Site Generator. Mode determines whether your Site is Hosted or Headless, toggling Site hosting and builds. Adding a Site icon is now part of the onboarding flow.
The Build Configuration page now includes a checkbox for Building Locked and sections for Command line options, Build system options, and Library versions. The SSG dropdown has moved to the Site Details page.
Fields available under Command line options are Install Command, Build Command, Output Path, and Environment Variables.
Fields available under Build system options are Preserved Paths, Preserve Output, Include Git Folder, and Manually Configure URLs.
Fields available under Library versions are Hugo version, Ruby version, Node version, and Deno version.
Many configuration options have been removed from this page as you no longer need to specify them in CloudCannon for Sites using the Unified Configuration file format.
All new Organizations now use the Unified Configuration file format by default.
New flags have been added to Sites to control some input naming conventions. Existing Sites will be unaffected.
The Infer Select values from input key flag controls whether inputs will select from collections automatically. For example, whether an input named author will automatically become a select box referencing a collection named authors. New Sites using Unified Configuration will not have this flag enabled, but it can be enabled in the Site settings.
The Infer Structure from input key flag controls whether inputs will reference a configured structure automatically. For example, whether an input named content_blocks will automatically become an array of the structure named content_blocks. All sites will continue to have this flag enabled by default, but this can be disabled in the Site settings.
Fixes
Fixed an issue where CloudCannon incorrectly showed an error for undefined mutable Object inputs.
Fixed a spacing issue for Object inputs with a context box.
Fixed an issue where CloudCannon did not display the correct icons in the CloudCannon configuration file.
Fixed an issue causing inputs with an undefined input.type in your CloudCannon configuration file to break when you open it in the Data Editor.
Fixed an issue preventing input selectors prefixed with $. from applying inside a structured array.
Fixed an issue where, in some cases, CloudCannon did not register an unsaved change when you deleted the content of a Rich Text input.
Fixed an issue where, in some cases, you could not save changes to your Site while another person had a new file open in an editing interface.