Locations plugin: Address input fields are wiped after hitting "find address"

Support Discourse Locations
1

Environment

Discourse Version: 3.2.2

Plugin Commit: Merge pull request #113 from paviliondev/fix_inside_map_drag_on_desktop · paviliondev/discourse-locations@3c350d0 · GitHub

Steps to Reproduce

  1. Create new topic, hit “add location” button
  2. enter address fields and hit “Find address”
  3. all field values are wiped (when address not found)

Example

https://cablogstaging.discoursehosting.net/c/csc-verzeichnis/144

This is very annoying as the address was not found, I have to enter all details from scratch

Logs

Message (66787983 copies reported)

[db6158] Job exception: undefined method `wrapped’ for #<SystemStackError: stack level too deep>

Backtrace

/var/www/discourse/app/jobs/regular/user_email.rb:17:in block in <class:UserEmail>' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/job_retry.rb:198:in delay_for’
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/job_retry.rb:174:in process_retry' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/job_retry.rb:129:in rescue in local’
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/job_retry.rb:112:in local' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:135:in block (5 levels) in dispatch’
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq.rb:44:in block in <module:Sidekiq>' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:131:in block (4 levels) in dispatch’
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:263:in stats' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:126:in block (3 levels) in dispatch’

1 Like
3

Given this is a free plugin, I can’t promise a response time, but thanks for the report, I can see the frustration.

In fact, I’d go as far as to say this is a UI enhancement request albeit a very reasonable one.

We have discussed internally moving this to a paid support model, but those discussions have not concluded.

I don’t believe your attached logs are related, but thank you for sharing those in case. If there are errors on the browser console, please share those.

1 Like