Conversation
supportKunalb, We seem to be having an issue with the Google Maps API in EventPress. It was working great and I am not sure if it quit working when we upgraded EventPress or what. I disabled all the plugins just to see (except buddypress, buddypress custom posts and eventpress) and still have the same issue. Here is a page where it is not working: http://109.104.78.35/events/bridget-riley-paintings-and-related-work-4/ If you run the firebug console, you will notice that the google maps api request returns 404 due to a bad request. Any ideas what needs to happen / where to look to fix this? http://wordpress.org/extend/plugins/eventpress/
Just comparing the javascript to the Google Maps API example, it seems to me that the latlong variable may not be getting processed properly?
Strange — can you take a look at what is being stored in the _ep_latlong metadata for the post?
Your assumption is correct… the _ep_latlong value is empty. Problem is that when I create a new event, this value is never being created / stored.
Is the venue location on the map changing when you modify the page in the admin? As in, if you change the venue to, say, Mumbai — is the marker moving? If yes, then _ep_latlong is getting interfered with while saving; if not, then something’s preventing the code to get the latitude/longitude corresponding to the venue provided.
Here is what is going on… If I create an event from the front end of the site, everything works great. If I create an event from the back end, the map does not display at all in the edit post screen. After some thorough testing, I discovered that a combination of two plugins together were causing a conflict that prevented the proper loading of the JavaScript for the Google Map on the back end. If I disabled one, or the other, of the plugins it would work… but if both were enabled it would not. So everything is back to working again… no problem with your plugin. I do have one thing that is bugging me though. On the back-end, if you use the date picker and want to delete a date that has been entered, you have to select the date and use the backspace button (NOT delete). Simple enough if you know that. On the front end, if you so much as click in a field, the date picker inserts a default date. Any dates inserted on the front end CANNOT be cleared (unless there is something I don’t know).
Actually the front end is behaving as the guy who wrote the plugin intended it to. In the back end, the previous version of Jquery UI is being used with a partially hacked version of the calendar picker. On the frontend, the right version of JqueryUI is being used with a pristine calendar picker. I’ve been looking for time to either build that a bit better or roll my own date+time picker because the current one gives no feedback on selecting a date.
Just comparing the javascript to the Google Maps API example, it seems to me that the latlong variable may not be getting processed properly?
Strange — can you take a look at what is being stored in the _ep_latlong metadata for the post?
Your assumption is correct… the _ep_latlong value is empty. Problem is that when I create a new event, this value is never being created / stored.
Is the venue location on the map changing when you modify the page in the admin? As in, if you change the venue to, say, Mumbai — is the marker moving? If yes, then _ep_latlong is getting interfered with while saving; if not, then something’s preventing the code to get the latitude/longitude corresponding to the venue provided.
Here is what is going on… If I create an event from the front end of the site, everything works great. If I create an event from the back end, the map does not display at all in the edit post screen. After some thorough testing, I discovered that a combination of two plugins together were causing a conflict that prevented the proper loading of the JavaScript for the Google Map on the back end. If I disabled one, or the other, of the plugins it would work… but if both were enabled it would not. So everything is back to working again… no problem with your plugin. I do have one thing that is bugging me though. On the back-end, if you use the date picker and want to delete a date that has been entered, you have to select the date and use the backspace button (NOT delete). Simple enough if you know that. On the front end, if you so much as click in a field, the date picker inserts a default date. Any dates inserted on the front end CANNOT be cleared (unless there is something I don’t know).
Actually the front end is behaving as the guy who wrote the plugin intended it to. In the back end, the previous version of Jquery UI is being used with a partially hacked version of the calendar picker. On the frontend, the right version of JqueryUI is being used with a pristine calendar picker. I’ve been looking for time to either build that a bit better or roll my own date+time picker because the current one gives no feedback on selecting a date.