Plugin Author
bozdoz
(@bozdoz)
Can’t reproduce this error. Maybe the consumer key you provided wasn’t correct?
check out my results: https://imgur.com/a/qLfcGs8
feel free to test with my api key; it’s just a demo, so I can revoke it.
Plugin Author
bozdoz
(@bozdoz)
Also, I am on WordPress 5.6
Thread Starter
kvako
(@kvako)
Hello bozdoz,
Thank you for the quick reply. Unfortunately, also with your Mapquest API key, it does not seem to work on my WP 5.6 (Theme wprentals). Please check my settings and shortcode generator using your API :
Leaflet 2.22.1 issue on WP 5.6?
Best regards,
Kvako
Plugin Author
bozdoz
(@bozdoz)
If you could, go to the shortcode helper page and open the developer tools console (in the browser). You very likely have a lot of javascript issues that are being printed there. Let me know what errors you get
Thread Starter
kvako
(@kvako)
Hello,
I get a few warnings and 1 error concerning an uncaught TypeError t is null in polyline.js.
Please see the text below:
Deprecated include of L.Mixin.Events: this property will be removed in future releases, please inherit from L.Evented instead. S.extend/<@https://unpkg.com/leaflet@1.7.1/dist/leaflet.js:5:3170
S.extend@https://unpkg.com/leaflet@1.7.1/dist/leaflet.js:5:3188
@https://www.mapquestapi.com/sdk/leaflet/v2.2/mq-map.js?key=KNu78zs1AncFt9ohmneASgH9BOdmn4EX&ver=2.0:44:15103
Class.js:121:11
Uncaught TypeError: t is null
_projectLatlngs Polyline.js:223
_projectLatlngs Polyline.js:236
_projectLatlngs Polyline.js:236
_project Polyline.js:204
_reset Path.js:139
onAdd Path.js:85
_layerAdd Layer.js:114
whenReady Map.js:1465
addLayer Layer.js:176
addLayer LayerGroup.js:47
addLayer FeatureGroup.js:35
addTo Layer.js:52
<anonymous> admin.php:1498
init construct-leaflet-map.min.js:1
Polyline.js:223:13
_projectLatlngs Polyline.js:223
_projectLatlngs Polyline.js:236
_projectLatlngs Polyline.js:236
_project Polyline.js:204
_reset Path.js:139
onAdd Path.js:85
_layerAdd Layer.js:114
whenReady Map.js:1465
addLayer Layer.js:176
addLayer LayerGroup.js:47
addLayer FeatureGroup.js:35
addTo Layer.js:52
<anoniem> admin.php:1498
init construct-leaflet-map.min.js:1
Does this give a clue to you concerning the issue?
Thanks,
Kvako
Plugin Author
bozdoz
(@bozdoz)
well it looks like some of the coordinates are missing, but no idea why. Maybe there’s some issue with decimal zooms. If you want to try creating a new post and testing there, you could try to recreate the issue:
[leaflet-map lat=52 lng=5 zoom=8.2 zoomcontrol !show_scale]
[leaflet-circle lat=52 lng=5 radius=17500]
[leaflet-scale position=topright]
That is from the shortcode page and has a decimal zoom. If you wanted to test without the decimal zoom, try this:
[leaflet-map lat=52 lng=5 zoom=8 zoomcontrol !show_scale]
[leaflet-circle lat=52 lng=5 radius=17500]
[leaflet-scale position=topright]
Thread Starter
kvako
(@kvako)
Hi,
I have put your both code sets in a seperate text field and both options on the frontend seem to work fine. They are correctly displayed. The shortcode generator at the back end however keeps having the same problems, whatever I try.
The default latitude and longitude is saving values with a comma instead of a decimal point. So when I type for instance 45.67, it will be returned to 45,67. Could this be an issue?
Best regards,
Kvako
Thread Starter
kvako
(@kvako)
Hello bozdoz,
I have to make a small correction to my observation. The maps are not displayed completely correctly on the frontend. The zoomcontrol buttons are not showing up at all. Also the scale is not showing. Whatever setting I try.
The map, zoom level and circle appearance are OK.
Best regards,
kvako
Plugin Author
bozdoz
(@bozdoz)
This is completely bizarre then. I really don’t know where to go with this. Some things you could try:
1. reset the plugin settings, and clear your geocoder cache (from settings page)
2. change themes
3. try just [leaflet-map][leaflet-scale] for the scale
Also check the developer console to see if there are any *new* javascript errors. The old one still doesn’t make much sense (though if your lat/lng is turning into commas, then yeah, that’s a huge problem).
Plugin Author
bozdoz
(@bozdoz)
The default latitude and longitude is saving values with a comma instead of a decimal point. So when I type for instance 45.67, it will be returned to 45,67. Could this be an issue?
Where are you seeing this happen?
Thread Starter
kvako
(@kvako)
Hello Bozdoz,
After some testing, I have the impression that there might be some incompatability issues with my theme? I have no other explanation at this moment. My theme uses WpBakery or Elementor to build up pages and I guess this is causing an issue? My homepage for example is using WPbakery to build up the elements on the page. First I include a row and then I place a text block in it using the wpbakery widgets. In this text block, I incorporate the leaflet codes that you supplied. Everything is displaying well except the zoom buttons and scale which are essential to me. There are no errors on the debugger screen, only some warnings not related to the problem.
If I incorporate your leaflet codes on a post that has been configured with the classic wordpress theme, then everything is displayed well including scale and zoom.
Other test that I did was to reinstall the leaflet maps plugin but this did not bring a solution.
Concerning the point and comma issue. This is appearing for the values “default latitude” and “default longitude” on the settings page in my backend. When I use the dutch language at the backend (my native language), then my saved values for “default latitude” and “default longitude” are always appearing with a comma. Even when I introduce a point as decimal separator. However, I have tested my backend as well by returning to the english language. In that case, values are correctly appearing with a decimal point. But unfortunately, the codehelper page keeps having the same issues.
I am a bit stuck on this. The problem seems to be slightly complicated. I might contact wprentals (my theme) for this or I could leave out the map on my homepage. Not sure yet how I will manage.
Thanks anyway for your support.
Plugin Author
bozdoz
(@bozdoz)
Just tried changing languages, and found the comma thing you mentioned. That is not a problem; it’s just how the browser renders the number in the inputs (the maps are not actually effected by it).
I tried installing Elementor and no issues.
I cannot install WPBakery because it’s not free. So it’s possible that it’s specific to that plugin, or it might be something else in that theme.
Hope that helps.
