With sensible ProxyPass rules, @@overview-controlpanel stops working

[Rudd-O]

I have a problem: mysite.com's @@overview-controlpanel returns 404.

This is what my proxy is doing:

BereqURL       /VirtualHostBase/https/mysite.com/Plone/en/VirtualHostRoot/@@overview-controlpanel

On the spanish site es.mysite.com, it's doing this:

BereqURL       /VirtualHostBase/https/es.mysite.com/Plone/en/VirtualHostRoot/@@overview-controlpanel

What am I doing wrong? It seems to me like the VHM URL appears correct. I'm telling Plone that the site root (it's the navigation root, after all, because en and es are LIFs) is en or es, but @@overview-controlpanel is still unavailable, and I can only ever manage the site if I go behind the proxy.

This seems like a bad bug to me.

[datakurre]

I assume the issue is that not all views registered for the portal root are also registered for the navigation root. I don't know if that's intentional for overview-controlpanel or not. "Fixing" would require registering both overview-controlpanel and probably all the other controlpanel views also for navigation root (some may already be, but some may not). And those are scattered around different packages.

I believe this has not been "fixed", because it's usual to have dedicated virtualhost for site admins.

[Rudd-O]

Well, it should be fixed.

Things that implement IPloneSiteRoot or other similar interfaces should probably automatically provide these views. Or any similar solution.

A number of other special views work fine.

It's tragic that people implementing Plone have to resort to workarounds such as deploying special management domains just so they can access key features.

On June 27, 2017 10:46:57 AM GMT+02:00, Asko Soukka notifications@github.com wrote:

I assume the issue is that not all views registered for the portal root are also registered for the navigation root. I don't know if that's intentional for overview-controlpanel or not. "Fixing" would require registering both overview-controlpanel and probably all the other controlpanel views also for navigation root (some may already be, but some may not). And those are scattered around different packages.

I believe this has not been "fixed", because it's usual to have dedicated virtualhost for site admins.

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/plone/Products.CMFPlone/issues/3748

--

Rudd-O

http://rudd-o.com/

[Rudd-O]

To be clear, you have a very common case where you have a "virtualhost for site admins" — every plone app multilingual site that maps /en /es /de (language URLs) to top-level domains has a "virtualhost" in this sense.

[jensens]

This issue should go to plone/Products.CMFPlone. If still an issue (and I think it is) please close here and create a new one

[Rudd-O]

Can't the issue be migrated somehow?