WPIntell

Source evidence

Confused

WP Maps – Google Maps,OpenStreetMap,Mapbox,Store Locator,Listing,Directory & Filters · review · 2025-05-02T10:45:00+00:00

complaintsentiment
mediumseverity
0.87relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 34 rows with source links

14.7% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

review
caryalpacas23 unresolved
I would have gladly given a ‘FIVE’ Star rating for the many months I have successfully been using WP Maps but for some strange reason, all gone haywire. ‘Not showing correctly on Website and informed ‘Billing Not Activated’ then ‘API Not Activated’, all of which I have activated but map still not showing. Went back to basic with location and although map shows correctly in Google Maps when I try to test in sandbox ‘Ooops something went wrong’? Hi, Thank you for using WP Maps over the past few months — we’re sorry to hear you’re now facing issues. Based on what you’ve described, here are a few things to double-check: Billing & API Setup: Even if you’ve already activated billing and APIs, it’s worth confirming in your Google Cloud Console: Billing is active and linked to the correct project. Required APIs are enabled (Maps JavaScript API, Geocoding API, Directions API, Places API, etc.). API Key Restrictions: Sometimes, restrictions (like HTTP referrers or IP addresses) placed on the API key can prevent the map from loading. Please check the API key settings for any such restrictions. Console Errors: When you see “Oops! Something went wrong,” it usually indicates a specific error. Open your browser’s Developer Console (Inspect → Console tab) and look for any detailed error messages — they can help identify the root cause (e.g., ApiKeyInvalid, RefererNotAllowedMapError, etc.). Please cross check you have follow all the steps of this tutorial: https://www.wpmapspro.com/docs/get-a-google-maps-api-key/ If you can share a screenshot of the error from your console or your API settings (with sensitive details hidden), we’d be happy to take a closer look and assist you further. Looking forward to resolving this for you. Best Regards Weplugins Team This reply was modified 1 year, 2 months ago by Steven Stern (sterndata) . This reply was modified 1 year, 2 months ago by Steven Stern (sterndata) . Reason: format

Comments

1 shown
Ashok Singh 2025-05-02T12:41:00+00:00

Hi, Thank you for using WP Maps over the past few months — we’re sorry to hear you’re now facing issues. Based on what you’ve described, here are a few things to double-check: Billing & API Setup: Even if you’ve already activated billing and APIs, it’s worth confirming in your Google Cloud Console: Billing is active and linked to the correct project. Required APIs are enabled (Maps JavaScript API, Geocoding API, Directions API, Places API, etc.). API Key Restrictions: Sometimes, restrictions (like HTTP referrers or IP addresses) placed on the API key can prevent the map from loading. Please check the API key settings for any such restrictions. Console Errors: When you see “Oops! Something went wrong,” it usually indicates a specific error. Open your browser’s Developer Console (Inspect → Console tab) and look for any detailed error messages — they can help identify the root cause (e.g., ApiKeyInvalid, RefererNotAllowedMapError, etc.). Please cross check you have follow all the steps of this tutorial: https://www.wpmapspro.com/docs/get-a-google-maps-api-key/ If you can share a screenshot of the error from your console or your API settings (with sensitive details hidden), we’d be happy to take a closer look and assist you further. Looking forward to resolving this for you. Best Regards Weplugins Team This reply was modified 1 year, 2 months ago by Steven Stern (sterndata) . This reply was modified 1 year, 2 months ago by Steven Stern (sterndata) . Reason: format