collective / collective/lineage.controlpanels

No sub site control panels with Plone >= 5.2

Open
#2 3 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

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`)?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the control-panel behavior for a sub site in Plone 5.2, then inspect the URL expression `string:${object/aq_parent/absolute_url}/@@site-controlpanel` and the `not:object/aq_parent/@@lineageutils/isChildSite` condition mentioned in the report. Done means sub sites show control panels whose URLs target the sub site, while main-site and sub-site records remain separate.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.