Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KeyError for list operation after upgrade #69

Open
mauritsvanrees opened this issue Nov 4, 2016 · 4 comments
Open

KeyError for list operation after upgrade #69

mauritsvanrees opened this issue Nov 4, 2016 · 4 comments

Comments

@mauritsvanrees
Copy link
Member

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:

Traceback (innermost last):
  Module ZPublisher.Publish, line 138, in publish
  Module ZPublisher.mapply, line 77, in mapply
  Module ZPublisher.Publish, line 48, in call_object
  Module plone.app.content.browser.vocabulary, line 101, in __call__
  Module plone.app.content.browser.vocabulary, line 323, in get_vocabulary
  Module plone.app.vocabularies.catalog, line 594, in __call__
  Module plone.app.vocabularies.utils, line 7, in parseQueryString
  Module plone.app.querystring.queryparser, line 29, in parseFormquery
  Module plone.registry.registry, line 38, in __getitem__
KeyError: u'plone.app.querystring.operation.list.contains.operation'

Looking in the configuration registry, I see lots of things starting with plone.app.querystring.operation, but nothing starting with plone.app.querystring.operation.list.

Going to portal_setup and applying the plone.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.

@davisagli
Copy link
Member

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?

@mauritsvanrees
Copy link
Member Author

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.

@NicolasGoeddel
Copy link

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.

@mauritsvanrees
Copy link
Member Author

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:

  • Go to the Zope Management Interface (/manage_main).
  • Go to portal_setup.
  • Go to the Import tab.
  • Select either 'Querystring parser/builder' in the profile title dropdown, or profile-plone.app.querystring:default in the profile id dropdown.
  • Click 'Import all steps'. (The default setting for dependency profiles should be fine.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants