Plone 6.0.0rc2 released

Release notes for Plone 6.0.0rc2

Released: Monday December 5, 2022.

The second, and probably last, release candidate of Plone 6 is ready!

For technical wizards who want to jump straight in, here are two important links:


Major changes since 6.0.0rc1:

  • None really. Lots of packages have gotten a final release, losing their alpha, beta or release candidate markers.

We are in a bugfix-only mode. An upgrade from rc1 to rc2 should be painless and is recommended for everyone.

Volto frontend

The default frontend for Plone 6 is Volto. Latest release is 16.3.0. See the changelog.
Note that this is a JavaScript frontend that you need to run in a separate process with NodeJS.
The ClassicUI is still available when you only run the Python process.

Python compatibility

This release supports Python 3.8, 3.9, 3.10, and 3.11.


For installation instructions, see the documentation.
This documentation is under development, but this should get you up and running. No worries.
We expect to switch to show the Plone 6 documentation sometime this week.

Final release date: December 12, 2022

Unless blocking issues are found that require more work, we expect to release Plone 6.0.0 final one week from now:
December 12, 2022.

If you find any issues, blocking or not, please report them in the main issue tracker.


Anyone had same byline issue?

Just show who edit it, but no date or time, as shown below?

by admin —

I see the rest of the byline just fine:

Screenshot 2022-12-09 at 09.57.19

If the item is modified, it will show the date.

And when I tried to add a new item, it displayed the date when I saved... but the date was gone when published.

Can you do a test? or it's the problem of my python 3.11?

The html source is (visit to 8088 without varnish or nginx)

    <a class="badge rounded-pill bg-light text-dark fw-normal fs-6" href="">admin</a>


here is a screen capture hope you can see it.

I see the same on
After creation the modification date is visible:

<span class="documentModified">
    <span>last modified</span>
    <span>Dec 10, 2022</span>

After publishing it is gone. When retracting it is stays gone. Weird.

I can confirm the issue.

Although the REST-API both for the document and for the workflow show the date:

curl \
    -s -X GET ${AT_ID}/@workflow \
    -H "Accept: application/json" \
    --user ${USER}

# returns
  "@id": "",
  "history": [
      "action": null,
      "actor": "admin",
      "comments": "",
      "review_state": "private",
      "time": "2022-12-10T11:24:00+00:00",
      "title": "Private"
      "action": "publish",
      "actor": "admin",
      "comments": "",
      "review_state": "published",
      "time": "2022-12-10T11:24:19+00:00",
      "title": "Published"
  "state": {
    "id": "published",
    "title": "Published"
  "transitions": [
      "@id": "",
      "title": "Send back"
      "@id": "",
      "title": "Retract"
curl \
    -s -X GET ${AT_ID} \
    -H "Accept: application/json" \
    --user ${USER} \
   | jq -r '."modified"'

# -> 2022-12-10T11:24:19+00:00

According to the byline code this works as follows:

  • Show the publication date only if "Show the publication date" setting is enabled.

Regardless that setting the modification date is shown either:

  • When there is no publication date yet (ex: the item is private)
  • The modification date is later than the publication date

Weird? Could be. Perhaps we can improve that in some other way. But I see it working.

Regarding the REST API, the REST API doesn't handle those settings like "Show the publication date", "Hide the author", etc. The REST API just exposes all the information.

The setting is called display_publication_date_in_byline so I would assume that the date is only shown when I published the document and I activated this setting ...

1 Like

The logic for the byline viewlet has changed between 5.2 and 6.0, and the current code is not completely logical, to me anyway. I have created an issue: Inconsistency in document byline · Issue #330 · plone/ · GitHub
But no blocker, let's see if we can fix this in 6.0.1. For now you can experiment with different combinations of the two settings I mention there, and see which combination works best for you.