No sub site control panels with Plone >= 5.2

[thomasmassmann]

Starting with Plone 5.2.0 all control panels are shown for sub sites, and the URLs point to the main site control panels.

Manually opening a URL of a control panel within a sub site works, and so does storing individual records for the main and sub sites.

Is it possible that the URL expression (e.g. string:${object/aq_parent/absolute_url}/@@site-controlpanel) is the problem with the aq_parent (same with the condition like not:object/aq_parent/@@lineageutils/isChildSite)?

[thomasmassmann]

So the difference seems to be the object and request in Plone 5.2.

In Plone 5.1, we get the following:

object: <PloneControlPanel at /Plone/portal_controlpanel used for /Plone/subsite-1>
request: <HTTPRequest, URL=http://localhost:8080/Plone/subsite-1/@@overview-controlpanel>

The object here has this used for, which resolves the correct parent.

In Plone 5.2 we have:

object: <PloneControlPanel at /Plone/portal_controlpanel>
request: <WSGIRequest, URL=http://localhost:8080/Plone/subsite-1/@@overview-controlpanel>

[thomasmassmann]

For Plone >= 5.2 the only solution I found to get the navigation root is by using something like string:${plone_portal_state/navigation_root_url}/@@site-controlpanel for the “Action”. Unfortunately, the PloneControlpanel does not support the extended expression context provided by the PloneBaseTool, so plone_portal_state is not available.

A ticket for Plone has been created at plone/Products.CMFPlone#3288.

A patch is available with https://github.com/cusyio/cusy.patches.cmfplone/

@jensens does this sound reasonable or do you have another solution to get the navigation root in Plone 5.2?

[jensens]

I agree! Same for Plone 6 I suppose.