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

TypeError upon logging in to a user without an ExpressSearchConfig app resource #5470

Open
grantfitzsimmons opened this issue Dec 12, 2024 · 0 comments
Labels
1 - Bug Incorrect behavior of the product geospecify regression This is behavior that once worked that has broken. Must be resolved before the next release.
Milestone

Comments

@grantfitzsimmons
Copy link
Member

Describe the bug
Users who do not have an ExpressSearchConfig app resource will experience an error toast immediately upon logging into production as of c75cf54.

TypeError at /context/available_related_searches.json cannot unpack non-iterable NoneType object Request Method: GET Request URL: http://localhost/context/available_related_searches.json 

To Reproduce
Steps to reproduce the behavior:

  1. Go to App Resources
  2. Filter all resources until you only see "Express Search Config"s
  3. Delete any ExpressSearchConfig app resource associated with your current user
  4. Log out or clear your cache
  5. See the error toast

Expected behavior

It should use the default express search config resource.

Crash Report

Specify 7 Crash Report - 2024-12-12T21_53_32.665Z.txt

Encountered on the geo_swiss instance as well as on a local copy of eurl
macOS, Vivaldi

This does not happen on v7.9.6.2

@grantfitzsimmons grantfitzsimmons added 1 - Bug Incorrect behavior of the product geospecify regression This is behavior that once worked that has broken. Must be resolved before the next release. labels Dec 12, 2024
@grantfitzsimmons grantfitzsimmons added this to the 7.9.x milestone Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Bug Incorrect behavior of the product geospecify regression This is behavior that once worked that has broken. Must be resolved before the next release.
Projects
None yet
Development

No branches or pull requests

1 participant