github sveltia/sveltia-cms v0.267.0

59 minutes ago
  • Assets can now be moved between repository folders and cloud storage services in the Asset Library. Select one or more assets and choose Move from the Edit Options menu or the details view, or drag them onto a folder or service in the sidebar. The entries using the assets are updated with the new paths or URLs in one commit, and the originals are only deleted once everything is in place, so a failure never leaves an entry pointing at a missing file. (#1166)
  • Renaming a file or folder on a cloud storage service now updates the entries that link to it, as with repository assets, instead of leaving them with broken links.
  • With Open Authoring, maintainers now see the pull requests contributors have opened from their forks on their own Editorial Workflow board, marked From a fork. They can open the entry to review it and, when the contributor allows edits from maintainers, save changes to the contributor’s branch. The pull request is then merged on GitHub, GitLab, Gitea or Forgejo with the new Review on… button. See Reviewing in Sveltia CMS for details. Make sure the sanitize_preview option is left at its default of true. (#1164)
  • Added a default option to the providers in media_libraries, so the Select File and Select Image dialogs open on an external storage provider instead of the first repository folder. This helps prevent files from ending up in your repository by mistake. The option can also be set per field.
  • Added an optional underline button to the RichText field, which saves underlined text as a <u> element. It’s only available with the html format, as Markdown has no syntax for underlines. (#1159)
  • Added an optional task-list button to the RichText field for GitHub Flavored Markdown task lists, with checkboxes that can be toggled with a click. (#1160)
  • Bug fixes and improvements.

Full Changelog: v0.266.0...v0.267.0

Don't miss a new sveltia-cms release

NewReleases is sending notifications on new releases.