Configuration

For the default callback route, configure geolocation providers the same way as base_geolocalize :

• Open Settings and configure the geolocation provider you want to use.
• If you use Google, set the GeoCoding API key.
• If you use the public OpenStreetMap service, keep request volume low to avoid rate limits.

No extra configuration is required to open the demo page.

Usage

Manual UI test

Open /website_map_picker/demo on the website.

• Click on the map.
• The widget calls the configured callback route.
• The returned payload is shown under the map.

Reuse the helper in another page

Call the QWeb helper template:

<t t-call="website_map_picker.map_picker_helper">
    <t t-set="picker_title" t-value="'Pick an address'" />
    <t t-set="picker_description" t-value="'Click on the map to select a location.'" />
    <t t-set="clickable" t-value="True" />
    <t t-set="show_panel" t-value="True" />
    <t t-set="default_address" t-value="''" />
    <t t-set="callback_route" t-value="'/website_map_picker/location/info'" />
    <t t-set="result_target" t-value="'#my_result_box'" />
</t>

Set clickable to False when the map should stay read-only. In that mode the cursor stays neutral and click events do not trigger the callback route.

Set show_panel to True when you want the built-in side panel with the status, coordinates, address, and raw payload. The helper hides that panel by default.

Show the logged-in user or another partner/user on the map

The helper model can prepare map defaults from a partner or user record.

Logged-in user:

<t t-set="map_defaults" t-value="request.env['website.map.picker.helper'].sudo().get_current_user_map_defaults()" />
<t t-call="website_map_picker.map_picker_helper">
    <t t-set="picker_title" t-value="'Your current address'" />
    <t t-set="picker_description" t-value="'The map starts from the logged-in user address.'" />
    <t t-set="clickable" t-value="True" />
    <t t-set="default_address" t-value="map_defaults.get('address', '')" />
    <t t-set="default_latitude" t-value="map_defaults.get('latitude', 20)" />
    <t t-set="default_longitude" t-value="map_defaults.get('longitude', 0)" />
    <t t-set="default_zoom" t-value="map_defaults.get('zoom', 2)" />
    <t t-set="result_target" t-value="''" />
</t>

Any partner or user:

<t t-set="map_defaults" t-value="request.env['website.map.picker.helper'].sudo().get_record_map_defaults(partner_record)" />

Pass a res.partner or res.users record as partner_record. If the record has no saved coordinates, the helper will try to geocode its address.

The widget also emits a browser event named website-map-picker:location-picked on the helper root element. Another frontend module can listen to that event and populate form fields without changing this addon.