You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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? 😰
The text was updated successfully, but these errors were encountered:
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 😱 .)
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.
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
toplone.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? 😰The text was updated successfully, but these errors were encountered: