Viewing 3 replies - 1 through 3 (of 3 total)
  • RossMitchell

    (@rossmitchell)

    One of the changes in the 4.0.1 upgrade is that shortcodes are now more strictly scanned, some plugins and themes have come to grief on this, some have released updates. I understand that the problems are about how fields are quoted (The example was single quotes), and with square brackets. It seems that some shortcodes which were not quite correct, were being forgiven for their syntax errors, after the update an error occurs.
    I do not know if errors are being logged, or if turning on debugging helps.

    Who is the plugin author ? What are they saying ?

    Thread Starter digbymaass

    (@digbymaass)

    Plugin homepage:
    https://www.atlsoft.de/wordpress-map-plugin/#tabs1-engl
    So far there is no response from the developer.
    But it doesn’t seem like the shortcode is not working, since removing the code in the gpx file as described makes the plugin work again. A typical shortcode on our site would look like this:
    [map style="width: 350px; height:175px; border: 1px solid black;" gpx="/wp-content/uploads/2014/10/some-file-or-other.gpx"]

    The site with maps showing after editing the gpx files
    https://carnethy.com/

    Thread Starter digbymaass

    (@digbymaass)

    The error codes don’t tell me much as I don’t understand error codes; I left the non functioning maps on localhost –
    ReferenceError: Can’t find variable: L
    https://localhost/:251
    SyntaxError: Unexpected token ‘,’
    https://localhost/:279
    InvalidValueError: setIcon: in property fillOpacity: not a number
    2%7Bmain,panoramio,places%7D.js:27

    Doesn’t sound like anything to do with the plugin

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Could 4.01 update have broken Google-Maps-GPX-Viewer plugin?’ is closed to new replies.