Support › Meta Box Geolocation › Geolocation failed to load - how to identify the issue?Resolved
- This topic has 13 replies, 3 voices, and was last updated 1 year, 9 months ago by
Gerard Halligan.
-
AuthorPosts
-
June 16, 2022 at 3:21 PM #36527
Prabakaran Shankar
ParticipantHello, my geolocation fields were filled in correctly until this morning. I checked the Google Maps Api, data was pulled until this morning, then no request was made. To identify the problem, I checked the production site in troubleshooting mode with the metabox plugin alone in the twenty twenty theme. Same problem. How to check further and identify the problem.
In Chrome > dev tools > there is script.<script type="html/template" class="data-geo" data-geo="{"api_key":"..hide...","types":"address"}"></script>No console errors.
June 16, 2022 at 10:30 PM #36536Long Nguyen
ModeratorHi,
Thanks for your feedback.
I'm also experiencing that issue on my demo site. I will inform the development team to check it and get back to you later.
June 17, 2022 at 12:22 AM #36542ParticipantThanks for your kind update
June 22, 2022 at 11:32 AM #36626ParticipantAny updates Mr. Long.
June 23, 2022 at 2:37 AM #36633Gerard Halligan
ParticipantHi, I'm also experiencing this issue. Is there any update?
Thanks,
GerJune 24, 2022 at 11:22 AM #36656ModeratorHi guys,
Can you please make sure that the extension MB Geolocation is enabled on Meta Box > Extensions page?
June 27, 2022 at 2:43 PM #36681ParticipantYes, I checked that the MB Geolocation extension is enabled on the Meta Box > Extensions page. But still the same problem. I even checked it again in the default WordPress theme without other plugins. Still the same problem.
June 27, 2022 at 8:24 PM #36683ParticipantIt's definitely an issue with the latest update AIO 1.162. I rolled back to 1.15.8 and it's working again.
June 30, 2022 at 12:27 PM #36731ModeratorHi guys,
Please share your site credentials via this contact form https://metabox.io/contact/
I will take a closer look.June 30, 2022 at 1:45 PM #36732ParticipantPlease check your inbox.
July 1, 2022 at 11:43 AM #36751ParticipantThank you very much for identifying the problem. Please close this ticket.
July 1, 2022 at 12:25 PM #36752ModeratorHi guys,
The issue happens due to the field map needs to be available to make other address fields work. I've escalated this issue to the development team to fix it in the next update.
July 1, 2022 at 12:44 PM #36754ParticipantHello,
Thank you very much for your immediate support.
Now it is working fine with the help additional map field.
Actually, I don't need to load the map in the frontend. Just showing data stored in the database as text.
But in the frontend it loads 4 (3+1) scripts,1. <script src="https://maps.google.com/maps/api/js?key&libraries=places&ver=5.6.4" id="google-maps-js"></script>
2. <script type="text/javascript" charset="UTF-8" src="https://maps.google.com/maps-api-v3/api/js/49/7/common.js"></script>
3. <script type="text/javascript" charset="UTF-8" src="https://maps.google.com/maps-api-v3/api/js/49/7/util.js"></script>
4. <script src="https://nviewscareer.com/wp-content/plugins/meta-box/js/map-frontend.js" id="rwmb-map-frontend-js" defer=""></script>which leads to a console warning.
warning #1: util.js:240 Google Maps JavaScript API warning: NoApiKeys https://developers.google.com/maps/documentation/javascript/error-messages#no-api-keys
pv.l @ util.js:240 (anonymous) @ js?key&libraries=places&ver=5.6.4:217 Promise.then (async), (anonymous) @ js?key&libraries=places&ver=5.6.4:217
warning #2: util.js:240 Google Maps JavaScript API warning: InvalidKey https://developers.google.com/maps/documentation/javascript/error-messages#invalid-keyJuly 1, 2022 at 1:26 PM #36760ParticipantThat's great, thanks 👍
-
AuthorPosts
- You must be logged in to reply to this topic.