Skip to main content

Troubleshooting Guide: Map Listing Issues

This guide provides step-by-step instructions to troubleshoot issues with Map Listing not working. It covers API key verification, essential settings, plugin conflicts, and address validation to help identify and resolve the problem efficiently.

Updated over 2 weeks ago

1. Verify Google API Key Settings

Before troubleshooting further, ensure that the Google API key settings are correct:

  • Create an API key here: Google Maps Platform.

  • Enable the following APIs:

    • Geocoding API

    • JavaScript API

    • Places API

    API Key Restrictions Clarification

    You can restrict the Geocoding API key by IP as mentioned in the description here:

    Note that the top-level key (used in client-side requests made by the browser) cannot be restricted by IP, as the request originates from the client’s IP. If IP restrictions are applied, the API will not function correctly.

    To set up an IP address restriction for the Geocoding API key, you can use a tool like IP Address Guide to specify a range of addresses instead of a single IP. However, it’s up to you to determine whether you need to restrict access to a specific address or a range.

    The API key can be used for geocoding and will only work on your site. If you use an IP range, it may be accessible beyond your site, so if you require stricter control, you may need to configure a static IP.

    As for the API restrictions, there are two key settings in the interface:

    • Application restrictions: These define which IP addresses, websites, or applications can use the API key. You can set this to "None" or "IP Address."

    • API restrictions: These determine which specific APIs the key can access.

Overview of Required APIs

The following APIs are essential for Google Maps integration:

  1. Maps JavaScript API: Enables the rendering of maps on your website or application.

  2. Geocoding API: Converts addresses into geographic coordinates and vice versa, which is essential for place autocomplete and other location-based functionalities.

  3. Places API: Provides detailed information about places, including place autocomplete functionality. This API is particularly important for widgets like the Crocoblock Google Maps widget and Advanced Map widget.

Best Practices for API Key Configuration

  • Activate Your API Key: Ensure the API key used for your project is active and linked to the correct Google Cloud project.

  • Avoid Over-Restricting the API Key: During initial testing, avoid applying restrictions that might block required services. For example, ensure the key allows access to all enabled APIs.

  • Follow Google’s Documentation: Refer to the official Google Cloud Console documentation for detailed steps on creating and managing API keys.

2. Enable Preload Coordinates by Address

If a text meta field is used for addresses, enabling Preload coordinates by address is necessary.

Steps:

  1. Go to JetEngine settings.

  2. Enable Preload coordinates by address.

  3. Select the appropriate meta field.

  4. Re-save all posts to apply the changes.

3. Configure Map Listing Query

To ensure the map functions correctly:

  • Add a pin in Query Builder to set a default map center (this is required).

  • If not all results appear, enter -1 in the Posts per Page field.

4. Check for Borlabs Cookie Plugin Conflicts

The Borlabs Cookie plugin may interfere with the map’s functionality.

Steps:

  1. Check if the Borlabs Cookie plugin is installed and active.

  2. If installed, note that Borlabs has its own integration. For related issues, refer to their support team:

Additional Check: Address Validation in Google Maps

If the issue persists, search for the entered address directly in Google Maps:

  • If Google Maps cannot locate the address, the query in the Map Listing will also fail.

  • Ensure the address format is correct and recognizable by Google.

Following these steps should help diagnose and resolve most Map Listing issues efficiently.

Did this answer your question?