jackaspades

Thanks for your 2 messages.

I did also notice the system is trying to load Control.FullScreen library from the wp-gpx-maps plugin directory. This directory is not present. The attempted load is coming from another plugin for which I am the author and occurs in connection with the loading of maps for the database page – so it is fully my problem.

However I made some other progress with your plugin. I removed all sgpx tags in the articles and the alti profiles now work correctly with the various defaults.

Also I implemented a test page with multiple hoverable tracks. I observed that the hover system works correctly but clicking on a track polyline makes it disappear. The track control on the uppper left is still functional but you can’t get make the tracks visible without a page refresh. According to me this is an undesirable behaviour. Also, I noticed that the name=”…” option in the elevation-track tag is not used in the track control. The control is sourcing the track name directly from the gpx. Also possibly undesirable ?

Regarding polyline weights – in my opinion {weight:2} is not useful but {weight:6} might be.

Thanks and best regards

Hi No caching plugins are installed. Below are the setting in the widget panel.

Title : Notre programme (Voir en pleine page)
Lien du titre du widget : /association/programme-de-lassociation
Catégorie(s) à afficher : a subset of the categories (all but one are included)
Navigation above calendar : Nav
Navigation below calendar : jump
Limiter par auteur : nothing selected
Limiter par h?te : nothing selected
Location (Type) : all
Location (Value) : field is empty
Plage temporelle du mini-calendrier : Mois
Months to show in view : 1
Thanks

I just want make some minor changes to the layout and content, not the behaviour Thanks

Yes makes good sense. Thanks for the fast response. And by the way, this is the only GDPR plugin that looks (to me at least) to be doing everything right. I tried several. Some conflict with other plugins (ACF in particular) and others just don’t work. So thanks again !

Hi Just looking at this a second time, I notice that the reject button removes the script from the page source code. So this probably means that the residual cookies can no longer be used by the analytics package. Do you confirm ? Thanks

Bit late to answer this maybe. I had the same problem. Fixed it by hacking the script named WP-GPX-Maps.js. You can find the script in the plugin directory under /js. You will lose the control button allowing you to switch the map to a full screen but the rest of the functionality started to work again in my case.

The developper has removed support for Google Maps and replaced with support for OSM. As a result, the Google Streetview option (along with the various Google maps layers) are no longer available. Other functions seem to have been removed also. In addition, the plugin script WP-GPX_Maps.js throws an error on the fullscreen control. I am not sure why (perhaps a library is not loaded). However, if you are willing to hack the script you can make it work again by removing or commenting out 2 lines from the script and re-uploading the modified script to your site. The 2 lines to remove or comment-out are
– var fsControl = new L.Control.FullScreen();
– this.map.addControl(fsControl);
They are located around lines 690 to 695 in the script. You will no longer have a full screen option but the OSM maps should work . Good luck.

I tested the new GPX feature. It works perfectly. Thanks for your rapid response.