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

Problem when adding new meeting #9388

Closed
esdrasitq opened this issue Jun 3, 2022 · 2 comments · Fixed by #11507
Closed

Problem when adding new meeting #9388

esdrasitq opened this issue Jun 3, 2022 · 2 comments · Fixed by #11507

Comments

@esdrasitq
Copy link

Describe the bug
Hello Decidim community.
When adding a meeting, Entering adress displays 'invalid adress' and the development-app says : "There was a problem creating this meeting"

To Reproduce
Steps to reproduce the behavior:

  1. Add meeting component to a process
  2. Create a new meeting
  3. When you add the address, the development-app displays the error
  4. See error in shot screen

Expected behavior
There was a problem creating this meeting.

Screenshots
image

Stacktrace
N/A

Extra data (please complete the following information):

  • Device: [Desktop]
  • Device OS: [Windows 10]
  • Browser: [Chrome, Firefox]
  • Decidim Version: [0.25.2]
  • Decidim installation: [Alpine Linux Docker]

Additional context
N/A

@ahukkanen
Copy link
Contributor

This happens in case the maps backend does not find the given address or when the autocomplete is incorrectly configured.

So we need a bit more information for this:

  1. Do you have map services configured for the instance where you tested this?
  2. If you have map services configured, can you share all the configurations you have, such as which service you are using for geocoding and which service are you using for the front-end autocompletion? Of course, do not post any sensitive information, such as your API keys.

I tested this locally with HERE Maps as well as without any map service and it worked fine for me.

When HERE Maps was enabled I tested both cases:

  • Selecting one result from the autocomplete address list
  • Not selecting anything from the autocomplete address list (when geocoding happens at the backend)

Both cases worked fine on develop.

It could be also that this issue has been already fixed and I suspect PR #8430 (which became part of 0.26.0) if this is the case. Could you re-test this using 0.26.0 or the latest version at develop?

@esdrasitq
Copy link
Author

esdrasitq commented Oct 14, 2022

Thx @ahukkanen

In the picture below, you'll see the lines changed in config/initializers/decidim.rb
image

The picture below is the screen shot of my geocoder.rb
geocoder

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

Successfully merging a pull request may close this issue.

2 participants