search

plone / Products.CMFPlone

The core of the Plone content management system
https://plone.org
GNU General Public License v2.0
240 stars 183 forks source link

Registry records' values reset after upgrade to Plone 6? #3914

Open gforcada opened 4 months ago

gforcada commented 4 months ago

Hi,

in our policy product we are overriding plone.roles_allowed_to_add_keywords registry record.

But after the upgrade (this weekend) our editors complain that they can not add new keywords.

Indeed, if I look at that registry record, it has no values at all ❗ 😱

If I export the registry from production I see that the difference is that now the interface for that record moved from Products.CMFPlone.xxx.ISiteSchema to plone.base.interfaces.controlpanel.ISiteSchema.

Does that mean (I will check myself) that all interfaces that have registry records that got moved around from CMFPlone to plone.base or other packages, have lost their configuration? 😰

stevepiercy commented 4 months ago

From what version to what version?

If it helps, you can check all the release notes: https://plone.org/download/releases. (I just noticed, we don't have Plone release notes on Documentation 😱 .)

At least the upgrade guides are well-documented: https://6.docs.plone.org/upgrade/index.html

mauritsvanrees commented 4 months ago

Related is this fix, also handling registry records https://github.com/plone/plone.app.upgrade/pull/318

yurj commented 4 months ago

The question is why the key is the interface? I know you can query the registry by interface but this means that only one path is allowed or that aliases are not possible.