Plone 5.2rc1 soft-released

Confirmed. Versions and files are 5.1.5 (which is why restapi works in py2 but not in py3)

The versions file is flaky

http://dist.plone.org/release/5.2rc1-pending/versions.cfg

It extends

http://dist.plone.org/versions/zope-2-13-27-versions.cfg

rather than a decent Zope 4 versions.cfg.

Obviously an improper symlink. @esteele

Ugh. Fixed.

3 Likes

Looks good now! Tests of starzel-buildout with that are green and I also updated a project sucessfully.

Same here. plone.restapi buildout works now.

:metal:

Ok. I've removed the pending tag and will pass it along to the installers team.

2 Likes

a friendly reminder that 5.2 must not be released as final until this security issue has been addressed:

If we are about to list blockers, I have mine as well:

/cc @jensens

I am sorry, I don't get it. This was your last reply on the issue on github:

I think that may solve the issue as the URL would now only have one valid answer and no cache poisoning could happen.

What do you expect from us here?
`

If there are issues that should be fixed before a final replease and are not in https://github.com/plone/Products.CMFPlone/milestone/10 (because they are in a different repository): Please add theme here: https://github.com/orgs/plone/projects/5

I also consider this as a blocker

Is there "manage_interfaces" in zmi view in 5.2 ?
Doesn't seem to see it, or any other alternative ?

There are still various tiny public facing issues in the UI open which should be fixed for 5.2

and there are only some of the most obvious UI issues...a bunch of more subtle UI error exist.

Again, we've lost an eye on details, quality and user experience.

1 Like

After adding a new Member Date field, click on settings give below error.

Steps to reproduce:

  1. Create a new Plone instance
  2. Under Site Setup -> Users and Groups -> Member Fields
  3. Add a new date or datetime field.
  4. Click settings of the new field will give below error.

Using Python3.7

2019-03-31 21:04:57,614 ERROR [Zope.SiteErrorLog:17][waitress] 1554037497.61398820.848641227510042 http://localhost:8080/Plone2/member-fields/join/@@edit
Traceback (innermost last):
Module ZPublisher.WSGIPublisher, line 142, in transaction_pubevents
Module ZPublisher.WSGIPublisher, line 295, in publish_module
Module ZPublisher.WSGIPublisher, line 229, in publish
Module ZPublisher.mapply, line 85, in mapply
Module Products.PDBDebugMode.wsgi_runcall, line 60, in pdb_runcall
Module plone.z3cform.layout, line 63, in call
Module plone.z3cform.layout, line 47, in update
Module plone.z3cform.fieldsets.extensible, line 65, in update
Module plone.z3cform.patch, line 30, in GroupForm_update
Module z3c.form.group, line 132, in update
Module z3c.form.form, line 136, in updateWidgets
Module z3c.form.field, line 257, in update
Module zope.component._api, line 97, in getMultiAdapter
zope.interface.interfaces.ComponentLookupError: ((<zope.schema._bootstrapfields.Field object at 0x10e2394e0>, <WSGIRequest, URL=http://localhost:8080/Plone2/member-fields/join/@@edit>), , '')
[12] > /Users/michael/plone5/destiny/eggs/zope.component-4.5-py3.7.egg/zope/component/_api.py(97)getMultiAdapter()

Similar issue. I am using 5.2.2 pending because I got spun around using the 5.2.1 version with it calling mailinglogger==3.8.8 etc. anyone else still having this problem?

I do not see any difference between 5.2.1 and 5.2.2-pending:

[ale@emily ~]$ diff <(ploneversions 5.2.2-pending) <(ploneversions 5.2.1)
164c164
< ## https://dist.plone.org/release/5.2.2-pending/versions.cfg
---
> ## https://dist.plone.org/release/5.2.1/versions.cfg