Renaming/moving (and likely copying) a portal leads to inconsistent catalog

[d-maurer]

Plone 5.2.x

Details: "zopefoundation/Products.CMFCore#118"

Workaround: enter the portal's "site context" (--> zope.component.hooks.setSite) before the operation (will not work for copying).

[mauritsvanrees]

I fear many other things would need fixing as well, next to the catalog. At least intids and relation catalog are likely a problem. Linkintegrity checks may fail. I admit that I am guessing. But I would not trust a renamed or copied site. Problem may only surface later.
Really I think this should not be supported. I would not mind if this raised an explicit error, or at least show a warning.

Some links:

• Rename and Import of plonesite fails when site contains at least on file or image (dexterity) #839
• https://community.plone.org/t/related-objects-not-shown-after-renaming-plone-site-id/15027

[d-maurer]

Maurits van Rees wrote at 2022-8-24 06:58 -0700:

I fear many other things would need fixing as well, next to the catalog. At least intids and relation catalog are likely a problem.

I do not speak about copying -- just moving/renaming: intids should therefore not be a problem. The catalogs currently use absolute paths (both as "uid"s as well as in the `path` index). Would they switch to portal relative paths, moving/renaming would get significantly simpler.

Linkintegrity checks may fail. I admit that I am guessing.

It, too, may be better use portal relative paths.