Plone 6.2 Is Here
Plone 6.2 focuses on further improving everyday editing and site administration, includes improvements for multi-site deployment, and continues the quiet modernization of the underlying foundation.

This page describes Plone 6.2 at a functional level for editors, site administrators, integrators, and decision makers. If you want to dive straight into the technical details: the changelogs, upgrade guide, and release-candidate announcement are linked in the Resources section at the bottom of this page.

Plone 6.2 focuses on further improving everyday editing and site administration, includes improvements for multi-site deployment, and continues the quiet modernization of the underlying foundation.

Plone 6.2 is the work of the whole Plone community: developers contributing across many sprints and Tune-Up Days; sponsors who make those sprints possible; translators; documentation writers; testers; and everyone on community.plone.org and Discord who reported issues and tried release candidates. Thank you all!

Plone has always been about empowering editors, and with Plone 6.2, we continue to deepen that commitment. By listening closely to our users and our editors, we’re making everyday work simpler and smoother — step by step, with every release. — Timo Stollenwerk

What's new?

Restore unsaved content

Losing work because of browser, operating system, or application crashes is incredibly frustrating for editors. It does not matter whether you lose five minutes or two hours of work.

Plone 6.2 addresses this problem with support for restoring unsaved content. As you type, your work-in-progress is stored in your browser’s local storage, separate from the published content on the server. Close the tab, lose power, or suffer a browser crash — when you return to that page, Plone offers to restore your changes.

Drop files straight into a folder

The folder contents listing is now itself a drop target. Drag files from your desktop anywhere onto the listing, and Plone opens a staging dialog with the dropped files ready to be reviewed, renamed, or removed before upload. The toolbar upload button still works for the cases where it makes sense — uploading into a folder you’re not currently viewing, for instance.

A control panel for blocks

Blocks in Plone offer great flexibility and sophisticated page layouts. However, editors and site administrators sometimes wonder where certain blocks are used or how many times a certain block is used on their website. This can be useful to decide if an organization wants to further enhance much used blocks. It can also be useful when deciding on migrations when blocks evolve over time.

With Plone 6.2, site administrators can use the new blocks control panel to get a list of all the blocks that are used on the website. They can see the exact numbers a block is used on the website and retrieve a full list of pages where a block is used.

Run Plone under any URL path

Plone can easily run hundreds of websites at scale. Large organizations, like the European Environment Agency or the German Aerospace Center, publish websites under their top-level domain and serve them via subpaths — example.com/intranet, example.com/kb, example.com/marine. Plone 6.2 supports this out of the box.

A live demo is available at demo.plone.org/next.

Plone 6.2 marks an important step in modernizing the frontend experience. By improving consistency, accessibility, and tooling, we are making the UI more intuitive for editors, while giving developers a stronger and more future-proof foundation. — Víctor Fernández de Alba

A consistent way to add an image

Until now, we had multiple different ways and widgets in Plone to upload, delete or replace an image. Plone 6.2 unifies all of that to a single image widget. Wherever in Plone you need an image, you get the same four options: upload from your computer, drag and drop a file in, pick something already on your site via the object browser, or link to an image elsewhere on the web. This provides a consistent user experience for editors and a consistent way for developers to customize and extend the image upload widget.

Under the hood

We stay up to date with the latest developments in the underlying Python packaging ecosystem we rely on. This becomes simpler and more reliable by switching to implicit namespaces (PEP 420). With Plone 6.2 we switch all our Python packages to use implicit namespaces, so you do not have to worry about it.

With native namespaces, the backend is up to date with the Python packaging ecosystem, making it easier to maintain a Plone site. — Maurits van Rees

Also in Plone 6.2

  • TinyMCE 8 in Classic UI, with optional license-key support for paid plugins.

  • Python 3.14 support; Python 3.10 is still the minimum supported version.

  • Updated to Zope 6 and many other refreshed dependencies.

  • New REST API services: @export, @import, @blocktypes, plus improvements to several existing services.

  • Better support for Plone distributions that define their own base profile, including distribution-aware upgrade handling.

  • Cross-language search in the Blocks chooser, single-selection mode for the SelectAutoComplete widget, and new Size / Width / BlockAlignment widgets.

  • Migration of unit tests from Jest to Vitest; default language now loaded from the backend API; Node 20 support dropped; pnpm 10 with catalog support adopted.

  • Add-ons that emit raw <a> or <img> tags should migrate to Volto’s UniversalLink and Image components — see the upgrade guide.

  • Whether you're building an add-on, starting a new project, or even creating your own Plone Distribution, Cookieplone simplifies the process by using templates maintained by the Plone Community.

  • RepoPlone is a tool designed to manage mono repos containing a repository.toml configuration file at the repository root. It provides various commands to streamline repository management, versioning, and release processes

Get Plone 6.2

Installation instructions, technical release notes, the upgrade guide, and the full backend and frontend changelogs are all linked in the Resources section below.

Thank you to everyone who made Plone 6.2 happen.

Resources

Article published: 20260521