Changelog Page: 7

Nested keys within preview

March 20th, 2024 | Minor

This release added nested keys to the card preview key.

It also addressed several issues, including those affecting DAMs, copying links from Google Docs, Hugo hardWraps, and conflicting updates.

Features & Improvements:

• You can now use nested keys within preview.

Fixes:

• Fixed an issue where branched sites would not copy the state of the "upload locked" flag, allowing you to upload images to your git repository rather than your DAM.
• Fixed an issue where CloudCannon failed to respect the "extra prefix" option when searching and uploading to larger DAMs.
• Fixed an issue where you could not see non-image files in a Cloudinary DAM via the CloudCannon browser.
• Fixed an issue where copying a link from Google Docs would add a <u> tag.
• Fixed an issue where quotation marks would be replaced by ".
• Fixed an issue where Hugo hardWraps was false by default. The hardWraps key will now match your Hugo config file.
• Fixed an issue where bolding text in the Content Editor would cause unexpected behavior.
• Fixed an issue where the Verify Email form could sometimes be submitted twice in quick succession, causing an error.
• Fixed an issue where saving new files would, in some cases, prevent you from resolving conflicting updates.
• Fixed an issue where, in some cases, structures would been hidden in the Data Editor.
• Updated dependencies to patch security vulnerabilities.

New keys to allow and remove custom markup

March 14th, 2024 | Minor

This release added the allow_custom_markup key to enable editing of custom markup in rich text editors and the remove_custom_markup key to strip custom markup from rich text. It also added documentation links to checkboxes and switches, a Copy output button, custom URL support for your dashboard preview screenshot, and updated the View output button.

This release addressed several issues, including those affecting publishing to posts in Jekyll, image duplication in the Visual Editor, embeds, the conflicting updates warning, and new files.

Features & Improvements:

• Added more options for handling HTML or Markdown structure that cannot be recreated in the rich text editor.
  • The allow_custom_markup key allows you to edit custom markup in rich text editors and explicitly accept the risk of unintentionally deleting elements that cannot be recreated.
  • The remove_custom_markup key will strip custom markup from content edited in a rich text editor, allowing you to clean files of unnecessary HTML content.
  • The remove_custom_markup key is disabled if allow_custom_markup is enabled.
  • You can define these keys anywhere you would configure a rich text toolbar. By default, allow_custom_markup is false for inputs and true for editable regions, and remove_custom_markup is false for inputs and editable regions.
  • You can configure both keys using the configuration GUI.
  • When using allow_custom_markup outside of editable regions, content that uses JavaScript will not be editable for security reasons. These inputs will appear as uneditable snippets.
  • For more information, please read our documentation on best practices for HTML in rich text and editable regions.
• You can now add documentation links to checkboxes and switches.
• You can now copy your build log using the Copy output button in the build modal, on the Status page, and in the Builds history tab.
• You can now specify a custom URL for your dashboard preview screenshot using editor.default_path in your global configuration file.
• The View output button is now available while your build is optimizing assets.
• The embeds tool in the WYSIWYG toolbar now opens a code editor instead of a text area.
• Invalid editable regions will now preserve their original content and have better error messaging.

Fixes:

• Fixed an issue where cloning or renaming a file from within an editing interface would not immediately open the cloned or renamed file.
• Fixed an issue where, on a Jekyll site, publishing a file to posts would not prompt you to add a date to the filename.
• Fixed an issue where, in the Visual Editor, updating the details for an image would cause the image panel to close.
• Fixed an issue where the Context menu for array and object inputs would show "Add undefined" instead of "Add item" for structures with no label configured.
• Fixed a spacing issue affecting arrays in the Data Editor.
• Fixed an issue where image panels would open in the wrong place.
• Fixed an issue where screen readers would lose focus every time a new line appeared in the terminal.
• Fixed an issue where you could not scroll a data file on devices with a smaller screen.
• Fixed an issue where the Data Editor would return to the top of the file when you changed data level.
• Fixed an issue where, for image inputs with resize configured, CloudCannon would unnecessarily duplicate images that already matched the specified height and width.
• Fixed an issue where, on branches that had a file with the same name as the branch, git pulls would not work.
• Fixed an issue preventing you from pushing local changes to a new branch.
• Fixed an issue where opening a file in an editing interface would automatically add focus to the first input.
• Fixed an issue where opening a file in an editing interface would trigger a change to that file without you updating any content.
• Fixed an issue where discarding your unsaved changes would not dismiss the conflicting updates warning.
• Fixed an issue where switching between editing interfaces on new files would create a second new file.
• Fixed an issue that sometimes prevented editable regions from loading for new files in the Visual Editor.
• Fixed an issue where embeds would delete their content.
• Improved output clarity by removing data-cms-embed.
• Improved consistency of icon colors in the WYSIWYG toolbar.
• Updated the copy in the Switch to editing banner and the Legacy Editing locked banner.

More permissible editing for custom markup in editable regions

March 8th, 2024 | Minor

This release addresses an issue impacting sites that use "custom markup" in editable regions. Custom markup is any HTML or Markdown structure that cannot be recreated in the rich text editor (e.g., <div> tags or style attributes). This is normally any structure that cannot be produced by the WYSIWYG toolbar.

Yesterday's release (New CloudCannon editing interface!) contained the following update:

• HTML elements that cannot be recreated in the rich text editor (e.g., div tags) will now appear as uneditable Snippets. This prevents you from unintentionally deleting unsupported HTML elements from your file.

The rationale for this update was to protect your content from someone unintentionally deleting custom markup. As CloudCannon cannot render custom markup in the rich text editor, there is a risk that someone could accidentally backspace or delete it. This risk was present in previous versions of the editing interface, and yesterday's release intended to address this.

We understand that this change caused several concerns for some of our customers. We apologize for any interruptions to your work caused by this change and are committed to creating a better experience for customers who rely on custom markup.

We have created a more permissive experience for sites using custom markup. This release allows you to edit the content within your editable regions in line with the editing experience available before yesterday's release. Some markup remains uneditable, but now it looks more like your live site and does not appear as an uneditable Snippet.

We are also creating a feature for HTML inputs in the sidebar of the Visual and Content Editor and the Data Editor. Sites that rely on custom markup in these places will have access to an "unsafe editing mode", allowing you to explicitly accept the risk of unintentionally deleting elements that cannot be recreated.

If you want to reduce any risk to your site, we recommend reviewing the placement of your editable regions or creating custom Snippets so your team can add, remove, and edit custom markup without the risk of losing your content.

At CloudCannon, we are committed to providing the best support experience possible. Please contact our support team if you have any questions or concerns about this issue. We are happy to assist in any way we can.

---

This release also added support for WebP as a MIME-type format and a flag allowing Clients to use the Legacy Editor.

It also addressed several issues affecting image previews, Snippets, site backups, and the Legacy Editor.

Features & Improvements:

• Added a more permissible editing experience for custom markup in editable regions.
• CloudCannon now supports WebP as a MIME type format.
• Added a site flag to allow Clients to use the Legacy Editor.

Fixes:

• Fixed an issue where, when an image URL contained a fragment, the image preview would not load.
• Fixed an issue where tabbing to the drag indicator on a Snippet and pressing enter would replace the Snippet with a new line.
• Fixed an issue where the Snippet controls would not appear if the Snippet was the first element in a file.
• Fixed an issue where open editing sessions with no unsaved changes would prevent Legacy Editor users from making changes.
• Fixed an issue where site backups would always include the .git folder, even when explicitly excluded.
• Additional error handling was added to prevent an issue where the Update status indicator would continuously loop.
• Updated dependencies to patch security vulnerabilities.

New CloudCannon editing interface!

March 7th, 2024 | Major

The new CloudCannon editing interface is now the default for all your sites.

Editing in CloudCannon is now a collaborative experience where multiple users can create content together. We’ve improved how our editing interfaces look and function. We’ve also introduced avatars to various places within the app so you can see who is editing what in real time.

Thank you to everyone who assisted in our most successful Beta yet. Your feedback has been helpful, and all known issues have been addressed.

The Legacy editing interface is still available for a short amount of time. CloudCannon will provide support for the Legacy editing interface until March 29th, 2024. If you have any feedback about this change, please get in touch with our support team.

Features & Improvements:

Editing interface improvements

• We have updated the appearance and functionality of the Editing interface navigation. From left to right, the navigation items are: the Toggle navigation button, the title and filename of the open file, the Update status indicator, team member avatars, the Editing/Viewing dropdown, the Interface buttons, the Context menu button, the Information button, and the Save button.
  • The Toggle navigation button opens your Site navigation.
  • The title and filename tell you what file you have open. The tools from the old File menu are now in the Context menu on the top right of your Editing interface navigation.
  • You don’t have to worry about losing your unsaved changes. CloudCannon now periodically updates as you make changes, so you can refresh your internet browser, change the editing interface, and switch who is editing your file without losing any content. The Update status indicator will show when this file was last updated.
  • Each team member now has an avatar. These appear in the Editing interface navigation when someone opens that file. One avatar is highlighted as the file editor.
  • You can now participate in editing sessions with your team members. During an editing session, one person can edit while multiple people view their edits live. You can switch between modes with the Editing/Viewing dropdown. While in Viewing mode, you can interact with the file in read-only mode.
  • The Interface buttons allow you to easily switch between CloudCannon’s four editing interfaces: the Visual, Content, Data, and Source Editors. You will see between two and four options depending on how your site is configured.
  • The Context menu is in the top right of the Editing interface navigation, the same place as on a file card or folder. The Context menu includes the following file actions: Preview live site, Copy output URL, Open Source Folder, Open Collection, Publish to posts (Jekyll only), Move, Clone, Rename, Download, Discard unsaved changes, and Delete file actions.
  • The Information button opens our Editing help modal.
  • The Save button allows you to save your changes to all edited files. A red notification icon will indicate how many files have unsaved changes.
• All team members now share an editing environment. This prevents one team member from unknowingly destroying other people’s unsaved changes when editing the same file.
• You can now open newly created files in the Source Editor without the need to save your site.
• The Data panel for editing images and links in the Visual Editor is now consistent with the Data panel for editing snippets.
• When opening files in the Visual Editor, the sidebar now defaults to Open/Closed, depending on the last file you had open.
• If the contents of a file are the same in the Data Editor and the Content Editor (i.e., it is a data file), only the Data Editor Interface button will appear in the top right of the Editing interface navigation.
• You can now use the image cropper for newly uploaded images and existing images in your site files.
• You can now drag and drop an image into the rich text editor or an input field to upload the image.
• Editable regions now use a Snippet-style editing panel.
• HTML elements that cannot be recreated in the rich text editor (e.g., div tags) will now appear as uneditable Snippets. This prevents you from unintentionally deleting unsupported HTML elements from your file.

Rich text editor overhaul

• We have overhauled the appearance and functionality of the rich text editor.
• The WYSIWYG toolbar in the Content Editor and other rich text fields have updated icons. This will improve clarity and consistency with other icons in CloudCannon.
• We have improved the reliability of the Undo and Redo toolbar options and keyboard shortcuts.
• The Code tool has been split into code_inline and code_block toolbar options. Enabling code in your toolbar options under your global configuration file enables both toolbar options.
• You can now add inline Snippets.
• Images in the rich text editor now behave like Snippets.
• When you paste an image into the rich text editor, a loading icon will appear while the image uploads.
• Better controls for tables in the rich text editor.
• We have updated the pop-up window for links and Snippets.
• You can now add a title attribute to a link.

Avatars

• Avatars for you and your team members now appear in various places throughout the app. Avatars appear on file cards and folders, in the Site navigation, and at the top right of an editing interface.
• Avatars will appear when a team member is online and will move to indicate what sites or files they are interacting with in real time.
• Clicking on an avatar will open the Avatar card, showing that team member’s name, profile image, email address, and a list of files they have open. Files they are Viewing are marked with an eye icon. Files they are Editing are marked with a pencil icon. You can navigate to those files by clicking on the file name in the avatar card.
  • Client avatars have a list of open files but no name, profile image, or email address.
• Avatars will also appear in the Review changes modal and Activity tab. These avatars do not indicate whether a team member is online or which files they have open.
  • In the Review changes modal, the avatar indicates that a team member contributed to the unsaved changes for a given file.
  • In the Activity tab, avatars indicate who saved each set of changes and which team members contributed to those changes.

Workflow updates

• The process for uploading, moving, renaming, and deleting files is now consistent with git workflows. Selecting Upload, Move, Rename, or Delete no longer immediately performs that action. Instead, the file or folder will be marked, and that action will occur the next time you save your changes. Marked files will receive a New, Edited, or Deleted badge to indicate they have unsaved changes.
• You can now move, clone, rename, or delete a file or folder by selecting that option in the Context menu at the top right of the file/folder card or from the Context menu at the top right of any editing interface.
• Renamed files will appear in your browser twice. The file with the new name will have a New badge, and the file with the old name will have a Deleted badge.
• Deleting files or folders:
  • You can open files marked for deletion in read-only mode. Opening a deleted file will show the “This file has been deleted” banner across the bottom of the editing interface.
  • You can restore files or folders marked for deletion at any time before saving your changes. To restore a file or folder, select the Restore file/folder option in the Context menu at the top right of the file/folder card or from the Context menu at the top right of any editing interface. You can also click the Restore file button in the Deleted file banner at the bottom of any editing interface.
  • You can also restore files marked for deletion in the Review changes modal, by selecting all the files you want to restore and clicking the Discard selected button.
  • You must discard all unsaved changes before deleting a file.
• CloudCannon now shows a loading animation when performing long file operations, such as uploading or cloning a large file.

Review changes modal improvements

• You now have more control over the way you review your unsaved changes.
• Each file with unsaved changes appears in the Review changes modal as a file card. Each card shows the title, collection (if applicable), filename, the avatar of each team member who contributed to unsaved changes, and when the file was last updated. The file card will also show a New, Edited, or Deleted badge to summarize the unsaved changes to that file.
• Files with unsaved changes are grouped into three headings: My changes, Other changes, and Conflicting updates.
  • The My changes heading lists all the files where you contributed to unsaved changes. These files are selected by default when you open the Review changes modal.
  • The Other changes heading lists all the files where you have not contributed to unsaved changes.
  • In some cases, you may see a Conflicting updates heading. This heading lists files with updates from outside of CloudCannon that conflict with your unsaved changes. You must address these conflicting updates to save other changes. You can address these conflicting updates by saving the affected files to attempt a merge or by discarding unsaved changes for those files.
• You can select as many or as few files as you like. The Save selected and Discard selected buttons at the bottom of the modal allow you to save or discard your selected files as a group.

Conflicting updates

• CloudCannon now detects and blocks incoming changes that conflict with your unsaved changes. This will prevent your save from replacing any updates from an external source (i.e., race condition).
• You will be notified when your site has Conflicting updates via a warning message in your Site navigation and Review changes modal. You can address these Conflicting updates by saving the affected files to attempt a merge or by discarding unsaved changes for those files to remove the conflict.

Badge improvements

• Three badge types appear on file and folder cards, indicating unsaved changes. These badges are New, Edited, and Deleted. These badges are removed from cards once all changes have been saved.
  • The Edited badge indicates a file’s content has been updated or files within a folder have been added, edited, or marked for deletion. The Edited badge will also appear on cards on the Sites list page when there are unsaved changes for that site.
  • The New badge indicates a file or folder was recently created or that all files within a folder were recently created.
  • The Deleted badge indicates a file or folder has been marked for deletion or that all files within a folder have been marked for deletion.

Account menu and Context menu improvements

• The Account menu now has an option for Organizations. We have also renamed My Account to Account Settings and removed the header displaying your current organization.
• The Context menu in the top right of a file card and the Context menu in the top right of the editing interface are now more consistent.

Editing help modal

• An Editing help modal will now appear in CloudCannon’s editing interfaces. This modal contains helpful information about how to use the Editing interface navigation.
• You will see this modal when you open an editing interface for the first time or when a new feature is released for our editing interfaces.
• You can reopen the modal at any time using the ⓘ icon in the top right of any editing interface.

Accessibility improvements

• We have improved app navigation using keyboard inputs. You can now:
  • Navigate the Context menu using your keyboard's arrow, tab, and escape keys.
  • Use Tab to escape rich text.
  • Use the Tab and Shift+Tab keys to navigate any editing interface.
  • Use the Tab and Enter keys to navigate arrays and objects in read-only mode.

UI improvements

• Radio buttons now have a clearer color scheme to indicate selected, unselected, disabled selected, and disabled unselected states.
• We have improved the appearance of all modals in CloudCannon.
• The Status page now has separate tabs for the Build and Compress terminals, which open/close as the build progresses.
• The Publishing page now has clearer error messaging, and the error summary is full width.
• The page title is now the window title and will appear in your browser tab and history.
• In the Visual Editor, invalid editable regions are now highlighted.
• In the Content Editor, invalid snippets are now highlighted.
• Minor improvements for mobile/small screen devices.

Fixes:

Editing interface

• Fixed an issue where unsaved changes would be lost at commit time.
• Fixed an issue where typing in a text input in the sidebar of the Content or Visual Editor would cause image inputs to re-render.
• Fixed an issue where CloudCannon CSS interfered with site elements in the Visual Editor.
• Fixed an issue causing incorrect spacing in the sidebar of the Content or Visual Editor.
• Fixed an issue where the “Unable to load preview” message would persist after clearing an image input.
• Fixed an issue where image inputs would fail to render an image preview immediately after uploading a new image.
• Fixed an issue where selecting an existing image did not open the cropper for editable regions.
• Fixed an issue where Snippets did not work in the Visual Editor.
• Reduced unnecessary network traffic caused by re-requesting images.

Rich text editor

• Fixed an issue where undoing a Snippet in the rich text view incorrectly added HTML to the file.
• Fixed an issue where image Snippets would not display an image preview in some Hugo sites.
• Fixed an issue where, in some cases, the rich text input field would not display its content.

Badges

• Fixed an issue where the Edited badge would persist after all changes were saved.

Context menu

• Fixed an issue where, in some cases, the Context menu would open with incorrect size and placement.

Syncing

• Fixed an issue that prevented files from being uploaded when building a new site.
• The terminals on the Setup pages and the Status page are now consistent.

Accessibility

• Fixed an issue where using Tab to navigate allowed you to focus on elements behind an open modal.
• Fixed an issue where using the keyboard to open a tab on the Site Settings page would return your focus to the top of the page.
• Fixed an issue where, in some cases, navigating using the Tab key would skip particular inputs in the Data Editor.

Other fixes

• Fixed an issue where the save changes button would become stuck on "Committing..." when syncing unsaved changes failed.
• Fixed an issue where, in some cases, filenames were displayed without the file extension.
• Fixed an issue where, in some cases, a dropdown menu would persist after the parent pop-up window closed.
• Fixed an issue where, in some cases, the DAM browser would not display sub-folders.
• Fixed an issue where, in some cases, deleting or uploading a file would fail with no error messaging.
• Fixed an issue where renaming a new folder would not immediately update the folder name.
• Fixed an issue where you could reorder multi-select inputs while in read-only mode.
• Fixed an issue where empty_type was ignored for mutable object inputs.
• Fixed an issue where the options.empty_type key could not contain a null value.
• Fixed an issue where preview would override the value for picker_preview.
• Fixed an issue where picker_preview would not work if preview was not defined.
• Fixed an issue causing incorrect spacing when an editing interface and the Site navigation were open simultaneously.
• Fixed an issue where the [relative_path] placeholder was added to a filename multiple times.
• Fixed an issue where you could not navigate to a nested global configuration file due to an incorrect URL.
• Fixed an issue where files with the .lock extension could not be renamed.
• Fixed an issue preventing you from adding a site icon.
• Fixed an issue where you could not navigate to a nested global configuration file due to an incorrect URL.
• Fixed an issue where trailing <br> tags were incorrectly removed.
• Fixed an issue preventing Snippets from working in HTML files.

More build servers

February 29th, 2024 | Minor

This release added a modal regarding our upcoming editing interface update and ARIA attributes for button icons. It also improved the visibility of focused elements and increased the number of build servers to reduce build wait time.

This release addressed an issue affecting empty arrays.

Features & Improvements:

• Added a modal to CloudCannon alerting you to our upcoming editing interface update.
  • On March 7th, at 3 pm (NZT), CloudCannon will make our Editor Beta the default editing interface. For more information, read our Beta Documentation. If you have any questions or feedback regarding this update, get in touch with our development team.
• Added ARIA attributes to button icons.
• Improved the visibility of some focused elements.
• Increased the number of build servers to reduce build wait time.

Fixes:

• Fixed an issue where empty arrays would not display if they were the only child of an object.

General fixes

February 27th, 2024 | Minor

This release addressed issues affecting Client Sharing pull requests and merge requests, the GitHub Enterprise upgrade banner, and the [count] placeholder.

Fixes:

• Fixed an issue preventing Client Sharing pull requests and merge requests.
• Fixed an issue affecting the GitHub Enterprise upgrade banner.
• Fixed an issue preventing the [count] placeholder from working correctly in Create Paths.

General fixes

February 23rd, 2024 | Minor

This release addressed issues affecting incorrectly hidden inputs and the Upgrade modal.

Fixes:

• Fixed an issue where CloudCannon would incorrectly hide root inputs inside structures if a schema was attached to a file.
• Fixed an issue where the Upgrade modal did not close after selecting a new pricing plan.

Site Activity tab update

February 21st, 2024 | Minor

This release updated the appearance and functionality of the Site Activity tab. This tab now lists more types of site activity, including information about changes from external sources, branch settings, and sync or output errors. The tab will also refresh with each sync or Site Settings update.

This release also made minor copy changes in the app, allowed users to sync files while an editing session was open, and adding name and email configuration for Client Sharing.

This release addressed issues affecting Site Mounting, the Cloudflare icon, domain releases, DAMs, and the Sync files button.

Features & Improvements:

• Released an appearance update for the Site Activity tab. The Site Activity tab now shows:
  • Authors and commit messages for changes from an external source (i.e., git provider).
  • Changes to Branch and Publish Branch settings.
  • When a Sync or Output Error occurs.
  • More events regarding updates to Site Settings.
• The Site Activity tab will now refresh with each sync or Site Settings update.
• Minor copy improvements in the app.
• Users can now sync files while an editing session is open.
• Users can now configure a name and email for Client Sharing. These are used to identify the author of commits to your git repository.
• Users can now use the keyboard to show or hide their password, improving accessibility.

Fixes:

• Fixed an issue preventing Standard Plan users from adding multiple Site Mountings.
• Fixed an issue where the Cloudflare icon was not visible on a white background.
• Fixed an issue where CloudCannon would not redirect users away from the Domain page after they released a domain.
• Fixed an issue preventing users from setting a DAM as the main source.
• Fixed an issue causing the Sync files button on the Site dashboard to fail in the event of an error.
• Fixed an issue preventing the Schema option hide_extra_inputs from working.
• Fixed an issue allowing URL encoding to bypass Auth Routes.
• Fixed an an issue preventing /.well-known/ URLs being served.

General fixes

February 16th, 2024 | Minor

This release addressed issues affecting preview screenshots and patched security vulnerabilities.

Fixes:

• CloudCannon has updated how we store preview screenshots for your sites.
  • Users may notice that preview screenshots for cards in the app are temporarily unavailable. Screenshots will appear again after the site is rebuilt.
• Fixed an issue where preview screenshots would fail for pages with no trailing slash or an extensionless URL.
• Updated dependencies to patch security vulnerabilities.

Accessibility updates

February 15th, 2024 | Minor

This release improved accessibility in the CloudCannon app by updating the shade of red used in the terminal and adding keyboard accessibility for various buttons. The CloudCannon UI now updates for all users when a user edits the organization branding, site details, or flags.

It also addressed incorrect copy in the upstream changes tooltip, extra prefixes preventing filename clash detection when uploading to a DAM, issues with structure configuration, and patched security vulnerabilities.

Features & Improvements:

• Updated the shade of red used in the CloudCannon terminal to pass Web Content Accessibility Guidelines (WCAG) criteria at AAA level.
• Improved keyboard accessibility for various buttons in the app.
• App notifications and changes to site setup status are now announced to screen readers as they happen.
• CloudCannon now updates the site UI for all users when a user changes the organization branding, site details, or site flags (i.e., Editing locked or Beta Editing sessions flag).

Fixes:

• Fixed the tooltip copy regarding upstream changes on the Publish button in your Site navigation.
• CloudCannon now respects extra prefixes when checking for clashing filenames while uploading to a DAM.
• Fixed an issue where, when adding an item to an array or object input, CloudCannon would select the first matching structure rather than the best match.
• When configuring structures, the preview.text and preview.icon keys now fall back to label and icon.
• Updated dependencies to patch security vulnerabilities.