- This topic has 5 replies, 2 voices, and was last updated 11 years, 10 months ago by .
Viewing 6 posts - 1 through 6 (of 6 total)
Viewing 6 posts - 1 through 6 (of 6 total)
- The forum ‘Generic’ is closed to new topics and replies.
Events Made Easy › Forums › Generic › locations_map shortcode no longer showing the map
Tagged: [locations_map]
I have an events calendar that previously used the locations_map shortcode to display the locations map with success. I am running v.1.0.5 of the plugin and WP 3.5. The shortcode Im using is:
[locations_map eventful=true width=580 height=480]
…and my calendar is at: http://www.cheesesociety.org/events-education/event-calendar/
I also tried eventful=1. There are no JS errors being generated, so I’m not sure what’s up here. Looks like my client has generated some wonky event location names – could that be causing the problem?
Well, I don’t see anything wrong, except you have some weird javascript in your header section that messes with the location map:
$('.eme-location-map').wrap('<div id="singleEventMapWrapper" />');
maybe that’s causing this? Or some CSS issues?
Franky, that line of jQ just wraps the maps on the individual event pages (eg – http://www.cheesesociety.org/events/?event_id=146) where oddly, the maps work. There’s nothing wrong with the shortcode as shown above?
I just looked at the net activity for this page, and the google maps resources are being called, so the process is at least starting. What does the parameter sensor=false in the maps JS coming from google mean? Could that be it?
UPDATE: Franky, my code editor seems to dislike some styntax around line 845 of eme_locations.php. See anything odd?
Thanks!
That line is commented out, should not be a problem:
//$result .= "<script src='".EME_PLUGIN_URL."eme_global_map.js' type='text/javascript'></script>";
But I just looked at your page again, and the map on your calendar page is now showing just fine? What did you change?
Aha! I had my client clean up some location names that included a bunch of event description info, creating very long location names and many duplicates. Looks like that fixed it! Not sure what that means, but something to put low on the troubleshooting checklist perhaps. Thanks for being so responsive, Franky! Resolved.
Well, if you happen to find one of those names that causes this, let me know!