Home › Forums › Calendar Products › Events Calendar PRO › No Events in Map View unless ‘Near’ field is completed.
- This topic has 9 replies, 4 voices, and was last updated 10 years, 1 month ago by
Leah.
-
AuthorPosts
-
January 17, 2016 at 8:43 am #1057505
Matthew
ParticipantHi,
I’m having a problem with my map view. When you click map view without completing the ‘Near’ field no events load. When you complete the near field they load just fine. I’ve recorded a quick video of the problem and my my efforts to address it here:
https://drive.google.com/file/d/0Bwi8XsZZg622TThjS2RXZW51R1U/view
Is there anything else I can try?
Thanks,
MatJanuary 18, 2016 at 3:35 pm #1058134Barry
MemberHi Mat,
Thanks for the screencast – that was helpful.
What really stood out was that, on initial load, the spinner icon never seemed to disappear (from map view). While I cannot replicate the same problem, that could be a useful lead.
If you’re familiar with your browser’s dev tools, could I ask you to visit map view and open them up – then check in the console. Do you see any Javascript errors and can you copy them here if so?
Failing that, would it be possible to get my hands on some (HTTP) credentials so I can view the problem first hand?
Thanks!
January 19, 2016 at 1:12 am #1058337Matthew
ParticipantHi Barry,
I do seem to be getting an error, I’m not sure exactly what it means. I’ll past a screenshot link and then copy exactly what it says below:
Screenshot:
https://nimbus.everhelper.me/client/notes/share/373771/1mz1l4rUpzQqbVQhgtkNcDSO59MmoOPQ/Error Message:
You have included the Google Maps API multiple times on this page. This may cause unexpected errors.tg @ js?sensor=false&ver=4.4.1:84
(index):244 Mixed Content: The page at ‘https://physiocourse.com/events/map/’ was loaded over HTTPS, but requested an insecure stylesheet ‘http://fonts.googleapis.com/css?family=Open+Sans%3A300%2C%3A300italic%2C%3A…ic%2C%3A600%2C%3A600italic%2C%3A700%2C%3A700italic%2C%3A800%2C%3A800italic’. This request has been blocked; the content must be served over HTTPS.
maps.google.com/maps-api-v3/api/js/23/5/util.js:23 Google Maps API warning: InvalidKey, SensorNotRequired: https://developers.google.com/maps/documentation/javascript/error-messages
https://physiocourse.com/wp-admin/admin-ajax.php Failed to load resource: the server responded with a status of 500 (Internal Server Error)January 19, 2016 at 7:31 am #1058674Barry
MemberThanks Mat,
So we’ve got a few things there. One, we can safely ignore (the SensorNotRequired issue).
The other – reporting the Google Maps API being used multiple times on one page is concerning and probably stems from your theme or another plugin also trying to use Google Maps. However, based on your screencast, it seems like the map itself is still functional and renders properly. So we can set this aside for the time being.
That leaves us with:
https://physiocourse.com/wp-admin/admin-ajax.php Failed to load resource: the server responded with a status of 500 (Internal Server Error)
What I’d like to find out is the precise nature of the 500 error. Do you have access to the error logs (or can you work with your host to obtain access)?
If you trigger this same problem and inspect the logs, do you find there is a more detailed error message available?
January 28, 2016 at 5:28 am #1063569Matthew
ParticipantHi Barry,
I called WP Engine and found out how to access the error logs. He said the problem appears to be with the plugin rather than something to do with hosting.
Here is a screenshot of the error logs:
https://nimbus.everhelper.me/client/notes/share/381983/gwel9CqN8c6rCFJkUaVkt0FTMzbx1cJG/If you need the full thing it is a really big text file but here it is:
https://drive.google.com/file/d/0Bwi8XsZZg622UlRCa3FBMVRoLW8/view?usp=sharingHe said basically the problem is that the ‘query’ is too long (he didn’t know what kind of query he said to ask you).
Any thoughts?
Thanks,
MatJanuary 28, 2016 at 8:35 am #1063860Barry
MemberThanks Mat,
There is definitely a scalability issue here and partly due to the large number of venues in your database, but partly because of they way we construct those queries, WP Engine is – not unreasonably – stopping them from running.
We’re going to have to revisit this and see if there is an alternative way of achieving the same result but without the extremely long list of venue IDs; in the short term perhaps you could ask WP Engine to remove the logic which kills very long queries like this one, if only as a temporary measure?
January 30, 2016 at 7:15 am #1065025Matthew
ParticipantHi Barry,
I called WP Engine but they said that they are not able to disable the kill script at the minute because I am not the only install on there and it would mess things up for the others. They said that they will kill anything longer than 6 seconds.
If you guys could look into changing this as soon as possible that would be great because I am going to have to turn map view off until it works 🙁 Could you notify me when it is fixed?
Thanks,
MatJanuary 31, 2016 at 7:42 am #1065327Barry
MemberHi Mat,
Sorry to hear that – but yes we’ll aim to post an update in here once the fix is available (you can also subscribe to our blog’s RSS feed as we cover release highlights there, too).
Thanks again for your support and patience.
February 21, 2016 at 8:35 am #1079331Support Droid
KeymasterThis topic has not been active for quite some time and will now be closed.
If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.March 14, 2016 at 2:08 pm #1088769Leah
MemberHello,
Thank you for reporting this issue. We weren’t able to get a fix for it into our upcoming release (4.1). However, please know that the problem is still on our radar and is ticketed within our system to be addressed in a future maintenance release. We’ll do our best to keep you posted when we are able to get a solution in place. Thank you for your patience while we improve and expand our plugins.
Best,
Leah -
AuthorPosts
- The topic ‘No Events in Map View unless ‘Near’ field is completed.’ is closed to new replies.
