Plone 6.0.0b2 released

1

The second beta is here! Some links:

Release notes for Plone 6.0.0b2

Released: Saturday September 10, 2022.

Highlights

Most important change is that this release officially drops Python 3.7 support.
Currently everything still work in 3.7, all tests pass, but beta 2 is the last release where this is the case.
See discussion in this issue and especially this community poll.

Python 3.8, 3.9 and 3.10 are supported. Python 3.11 support will likely be added after the final release. Most work for this is being done in the Zope packages. Note that Plone add-ons may choose to support less Python versions, especially dropping 3.8. You are encouraged to use Python 3.10, which is also the fastest supported Python.

Other major changes since 6.0.0b2:

  • plone.session:

    • Creating per-user keyrings in order to have session invalidation on log-out (server-side logout).
    • Cookie attribute SameSite is set to "Lax".

  • plone.restapi:

    • Add @portrait endpoint.
    • Add support for importing profiles in @addons endpoint.
    • Add support to search for fullname, email, id on the @users endpoint with "?search=".

  • plone.volto:

    • Added preview image link behavior.
    • Use slate as default text block in default contents for default-homepage and
      multilingual profile.

  • plone.app.z3cform:

    • Add default_time attribute/argument to Date- and DatetimeWidget to allow the converter to set a custom time when nothing was given.
    • Customizable DateWidget formatter length.

  • plone.i18n:

    • Add some more native names to language-country combinations
    • Fix the missing native names for language-country variants.

  • plone.app.robotframework: Add keyword 'Wait For Elements'. Here the requested element is allowed to match multiple times.

Volto frontend

The default frontend for Plone 6 is Volto. Latest release is 16.0.0-alpha.30.
See the changelog.

Python compatibility

This release supports Python 3.8, 3.9, and 3.10.
As said, technically 3.7 still works, but it is not supported anymore.

Installation

For installation instructions, see the documentation.
This documentation is under development, but this should get you up and running. No worries.

7 Likes
2

It has come to my attention that if you use buildout, you need at least zc.buildout 3.0.0rc1, otherwise you will see this error:

NameError: name 'python310' is not defined

This is caused by the [versions:python310] section with version pins specifically for Python 3.10.
It does not matter which Python version you use to run the buildout: you will always get the error when your zc.buildout version is too old.

Note that the requirements use version 3.0.0rc3, so you are fine when you use that.

1 Like
3

Thanks for Work!
I have upgrade our Intranet to P6b2 based on Classic UI, it's running very smooth.

What i have found:

  • /portal_catalog/manage_catalogReport raise an error, I stumbled across this by chance. normally i didn't click on the query report tab in the catalog tool.
Traceback (innermost last):
  Module ZPublisher.WSGIPublisher, line 167, in transaction_pubevents
  Module ZPublisher.WSGIPublisher, line 376, in publish_module
  Module ZPublisher.WSGIPublisher, line 271, in publish
  Module ZPublisher.mapply, line 85, in mapply
  Module ZPublisher.WSGIPublisher, line 68, in call_object
  Module Shared.DC.Scripts.Bindings, line 333, in __call__
  Module Shared.DC.Scripts.Bindings, line 370, in _bindAndExec
  Module App.special_dtml, line 213, in _exec
  Module DocumentTemplate._DocumentTemplate, line 144, in render_blocks
  Module DocumentTemplate._DocumentTemplate, line 227, in render_blocks_
  Module DocumentTemplate._DocumentTemplate, line 245, in render_blocks_
  Module DocumentTemplate.DT_In, line 762, in renderwob
  Module DocumentTemplate._DocumentTemplate, line 144, in render_blocks
  Module DocumentTemplate._DocumentTemplate, line 245, in render_blocks_
  Module DocumentTemplate.DT_In, line 698, in renderwob
  Module DocumentTemplate.DT_In, line 853, in sort_sequence
TypeError: '<' not supported between instances of 'dict' and 'dict'

  • the javascript webresource of collective.collectionfilter updated only after a second restart of clients, the first restart after the buildout is not enough, for whatever reason

  • in the folder_contents view the properties button of effective and expiration date, did't respect timezones

Thank's to all Plonistas for this crazy work

4

@1letter Thanks for using it and reporting back.
Can you report these issues on GitHub please, if you have not done so already? For most issues anyone finds, the CMFPlone tracker is a good one.
For the catalog issue... ah, I see it already was reported earlier this year in ZCatalog.