Wrong id of location field.

[tickHub]

In geolocation.js you refer to the location field as locationField: $("#form-field-location")

But i think it should be locationField: $("#form-field-coordinates")

[rutger1140]

Thanks for reporting. I will investigate this.

[tickHub]

Ah! The field name is dynamic (specified in the blueprint file), so it can be everything of course.
You can fix it for now with locationField: $("[type=geolocation]"), as long if you facilitate only one instance per page.

[rutger1140]

@tickHub I was unaware that the field type in the blueprint is set as the <input type='geolocation'> in the panel directly. I thought it was only needed to activate the custom field.

It looks like this:

<input class="input input-is-readonly" type="geolocation" name="location" autocomplete="on" placeholder="Coordinates" readonly="" id="form-field-location" tabindex="-1" data-field="location">

When changing the field name to 'location2' it looks like this:

<input class="input input-is-readonly" type="geolocation" name="location2" autocomplete="on" placeholder="Coordinates" readonly="" id="form-field-location2" tabindex="-1" data-field="location">

Selecting an input on an 'invalid' type attribute doesn't feel like the way to go. I would rather stick with the id of the field and instruct people to use location as the field name in their blueprint. I will update the readme.

But please feel free to issue a PR if you have a solid solution for this. Maybe loop through all the input fields with data-field="location" to allow multiple instances?