I think this may be a caching problem. Looks like the javascript files are not being loaded in time, so the JS on page is throwing up undefined reference errors. If you’re using a caching plugin can you try excluding the OS maps JS files from being delay-loaded?
I’ve disabled the caching plugin but still nothing visible.
It is probably unrelated but I’ve just noticed that a problem I had with a conflicting plugin that I reported (https://wordpress.org/support/topic/possible-conflict-with-wp-gpx-maps-plugin/) was not resolved by disabling, and indeed, removing the conflicting plugin. I had to also remove the shortcode from the post.
My symptoms were slightly different – I didn’t get a blank map, but I lost the trail. I noticed you have a couple of widgets in your example (e.g. TablePress and YouTube). TablePress should be fine (fantastic plugin for a running website) but it may be worth temporarily removing other blocks to eliminate them from your enquiries regardless of whether you’ve disabled the plugin.
I’m still seeing something which looks like a deferred load in the page source:
<script type=’text/javascript’ src=’https://burnhamjoggers.co.uk/wp-content/plugins/os-datahub-maps/js/leaflet.js’ defer onload=” id=’osmap-leaflet-js’></script>
@dougienisbet I’ve also seen that problem with the GPX maps plugin. The issue there is that the GPX maps plugin always loads its JS scripts regardless of whether it is displaying a map on the page, and it uses an earlier version of Leaflet maps which conflicts with the one used by my plugin. The OS maps plugin only loads the Leaflet script on pages where the shortcode is actually used, to avoid this sort of conflict. If you try to use both plugins on the same page then it will always be problematic.
@andrewkazalia I may have a workaround for this. If you can contact me via the email on the plugin website then I can send you a test version to try.
The temporary fix is now included in the official 1.3 release.
