Front-end event editing breaks my map shortcode

[elmalak]

Hi Casey,
Thank you for getting back to me with this solution, however, when I Tried it I am still getting the same result, the shortcode is broken as it used to.
When I type in this shortcode:
[map style=”width: auto; height:400px; margin:20px 0px 20px 0px; border: 1px solid black;” gpx=”http://www.trailsleuth.com/wp-content/uploads/user_uploads/ventoux/NEW%20VICO.gpx”%5D
And I Try to edit it, I get this broken code

<p>
<div class="gm_gpx_body" id="holder_map_0" style=""width:;">
<div class="google_map_holder" id="map_0" style="width:;"></div></div>
<script type="text/javascript">

var fszIndex = 1;
var distanceUnit = "";
var gmapv3_disableDefaultUI = false;
var gmapv3_zoomControl = false;

var scrollToEle = "html";
var mapSizeButton = true;
var mapobj = {
name: "OSM",
wms: "osm",
minzoom: 18,
maxzoom: 0,
url: "http://tile.openstreetmap.org/",
copy:"Open Street Map",
visible:true
};
mapTypesArr.push(mapobj);
var mapobj = {
name: "OSM Cycle",
wms: "osm",
minzoom: 18,
maxzoom: 0,
url: "http://b.tile.opencyclemap.org/cycle/",
copy:"Cycle OSM",
visible:true
};
mapTypesArr.push(mapobj);
var mapobj = {
name: "Relief",
wms: "",
minzoom: 18,
maxzoom: 0,
url: "",
copy:"maps-for-free",
visible:true
};
mapTypesArr.push(mapobj);
var mapobj = {
name: "Demis",
wms: "wms",
minzoom: 13,
maxzoom: 1,
url: "http://www2.demis.nl/wms/wms.ashx?Service=WMS&WMS=BlueMarble&Version=1.1.0&Request=GetMap&Layers=Earth Image,Borders,Coastlines&Format=image/jpeg",
copy:"WMS demo by Demis",
visible:true
};
mapTypesArr.push(mapobj);
var mapobj = {
name: "ROADMAP",
wms: "",
minzoom: 13,
maxzoom: 10,
url: "",
copy:"",
visible:true
};
mapTypesArr.push(mapobj);
var mapobj = {
name: "SATELLITE",
wms: "",
minzoom: 13,
maxzoom: 10,
url: "",
copy:"",
visible:true
};
mapTypesArr.push(mapobj);
var mapobj = {
name: "HYBRID",
wms: "",
minzoom: 13,
maxzoom: 10,
url: "",
copy:"",
visible:true
};
mapTypesArr.push(mapobj);
var mapobj = {
name: "TERRAIN",
wms: "",
minzoom: 13,
maxzoom: 10,
url: "",
copy:"",
visible:true
};
mapTypesArr.push(mapobj);
var msg_00 = "click to full size";
var msg_01 = "IE 8 or higher is needed / switch of compatibility mode";
var msg_03 = "Distance";
var msg_04 = "Height";
var msg_05 = "Download";
var pluri = "http://www.trailsleuth.com/wp-content/plugins/google-maps-gpx-viewer/";
var ieX = false;
if (window.navigator.appName == "Microsoft Internet Explorer") {
var err = ieX = true;
if (document.documentMode > 7) err = false;
if(err){
//alert(msg_01);
}
}

var map_0;
google.setOnLoadCallback(function() {
map_0 = init_map("TERRAIN", "map_0", 1);
load_map(map_0, "", "", "");

map_0["elevation"] = true;
map_0["download"] = true;
map_0.g_seCookie = false; // no cookie
map_0.g_showCnt++;
showGPX(map_0, ""http://www.trailsleuth.com/wp-content/uploads/user_uploads/ventoux/NEW%20VICO.gpx"");

map_0.gmap_poi_db = false;

post_init(map_0);

});

</script>
</p>

Regards,

[Casey]

Elmalak,
Our developer was able to test this fix successfully using shortcodes for other plugins. We’re actually looking at removing this by default in future versions of the plugin, so thanks for bringing this issue to our attention.

Unfortunately, if this fix isn’t working for you, then it must be something specific to your system or the plugin that you’re using that would account for the different results. We unfortunately can’t provide any further troubleshooting, as this looks to be a unique situation with how your specific plugin is implemented.

I hope you understand, and definitely feel free to reach out to us if you have other issues.

Thanks!

-Casey-

[elmalak]

Well,
I see what you mean and I understand your point.
Just to add this code works when I add a new event as it prevents the shortcode from breaking but when I got back to edit that event using the Front-end editor of the community events, it breaks into the code I’ve shared above.
Not sure if that makes a difference to the code needed for the fix or not, but I just thought I would make it clearer.
Regards,
Elmalak

[Casey]

Elmalak,
Thanks for the clarification!

[Leah]

Hi there,

Thanks for reporting this issue. We were not able to get a fix into our forthcoming 3.4 release. However, this issue is still definitely a priority for us and we plan to work on it for an upcoming release. We will update this thread at that time. Thank you for your patience.

Best,
Leah

[Barry]

Hi! We’ve now completed some work that ought to address this issue in our very next upcoming release. Thanks for your patience and if you do hit any further problems with this once you’ve updated please don’t hesitate to let us know in a new thread – thanks!

[Author]

Posts