Open mauritsvanrees opened 7 years ago
So maybe someone made a change to the plone.app.querystring profile but neglected to add an upgrade step to make the same change for existing sites?
This part of registry.xml
in current master is the exact same as in plone.app.upgrade for version 4.2 rc1. It has not changed since then. Weird. It is already broken when upgrading from Plone 3.1 to 4.3.
How do I apply the profile plone.app.querystring:default
? in portal_setup
. I've got the same problem when I try to delete a folder in a Plone 5 instance. The Delete button itself makes the error. I am not able to click on it while in folder_contents
.
I don't think the Delete button has anything to do with plone.app.querystring
, so this may be a different error. I could be wrong.
But to apply it:
/manage_main
).portal_setup
.profile-plone.app.querystring:default
in the profile id dropdown.
Today I tested an upgrade from Plone 3.1 to 4.3 and then on to 5.0.6. When I edit a page and want to search for an image, I get a traceback:
Looking in the configuration registry, I see lots of things starting with
plone.app.querystring.operation
, but nothing starting withplone.app.querystring.operation.list
.Going to
portal_setup
and applying theplone.app.querystring:default
profile, fixes it. But it should work out of the box after an upgrade. I don't know where this exactly goes wrong. There were no unapplied upgrade steps.