• Resolved Steve Fulton

    (@cableguysteve)


    Hi there

    If you visit the page you will see that the Geo Location which was working is now not. Please see the error messages from Chrome Inspect.

    JQMIGRATE: Migrate is installed, version 3.4.1
    cemetery-lookup/:1396 Uncaught SyntaxError: Unexpected token ']'Understand this errorAI
    cemetery-lookup/?wpda_search_column_idcemetery=1107:1937 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
    at updateAdsCount (cemetery-lookup/?wpda_search_column_idcemetery=1107:1937:20)
    at cemetery-lookup/?wpda_search_column_idcemetery=1107:1762:5
    at cemetery-lookup/?wpda_search_column_idcemetery=1107:1950:6Understand this errorAI
    js?key=AIzaSyD6sS09BqpE44xyQ3M29mR2lIbc2VbuOdY&libraries=places&callback=wpdaproGeolocationInit:1093 Google Maps JavaScript API has been loaded directly without loading=async. This can result in suboptimal performance. For best-practice loading patterns please see https://goo.gle/js-api-loading
    ifa @ js?key=AIzaSyD6sS09BqpE44xyQ3M29mR2lIbc2VbuOdY&libraries=places&callback=wpdaproGeolocationInit:1093Understand this warningAI
    js?key=AIzaSyD6sS09BqpE44xyQ3M29mR2lIbc2VbuOdY&libraries=places&callback=wpdaproGeolocationInit:1000 Uncaught (in promise) InvalidValueError: wpdaproGeolocationInit is not a function
    at _.Nj (js?key=AIzaSyD6sS09BqpE44xyQ3M29mR2lIbc2VbuOdY&libraries=places&callback=wpdaproGeolocationInit:1000:373)
    at hfa (js?key=AIzaSyD6sS09BqpE44xyQ3M29mR2lIbc2VbuOdY&libraries=places&callback=wpdaproGeolocationInit:1098:180)
    at js?key=AIzaSyD6sS09BqpE44xyQ3M29mR2lIbc2VbuOdY&libraries=places&callback=wpdaproGeolocationInit:1097:228Understand this errorAI
    advanced.min.js?ver=1.55.0:1 Object
    wpda_geolocation.js?ver=5.5.16:88 Uncaught ReferenceError: markers is not defined
    at deleteAllMarkers (wpda_geolocation.js?ver=5.5.16:88:18)
    at e..drawCallback (wpda_datatables.js?ver=5.5.16:77:42)
    at jquery.dataTables.min.js?ver=5.5.16:4:47231
    at Function.map (jquery.min.js?ver=3.7.1:2:3971)
    at R (jquery.dataTables.min.js?ver=5.5.16:4:47178)
    at y (jquery.dataTables.min.js?ver=5.5.16:4:23396)
    at It (jquery.dataTables.min.js?ver=5.5.16:4:28084)
    at jquery.dataTables.min.js?ver=5.5.16:4:26646
    at Object.e as success
    at c (jquery.min.js?ver=3.7.1:2:25304)Understand this errorAI
    196Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies.Understand this warningAI

    I did resolve a few issues before sending this to you. As i stated it was working at one time. The API Key has been checked and is vaild.

    Any assistance would be helpful.

    Thanks

    Steve Fulton, UE

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Passionate Programmer Peter

    (@peterschulznl)

    Hi Steve,

    Sorry you’re having this issue. This looks like some malformed source code.

    Please open the source of your page and search for:
    wpda_url_params] = urlparam[1];

    This should be:
    wpda_url_params[urlparam[0]] = urlparam[1];

    For comparison you can check this demo page:
    https://wpdataaccess.com/publication-using-geolocation/

    Sor some reason [urlparam[0] is missing. I can think of two reasons:
    1. The file was not correctly transferred or edited
    2. Some filter is changing the code

    Can you please check if the code is correctly saved in file WPDAPRO_Geo_Location_Init.php? This is would eliminated the first option.

    Does it work if you run this code on the back-end? This would suggest some filter is changing the code on the front-end.

    Please let us know if this help.

    Best wishes,
    Peter

    Thread Starter Steve Fulton

    (@cableguysteve)

    Morning Peter:

    1. Can you please check if the code is correctly saved in file WPDAPRO_Geo_Location_Init.php?
      • The Code is saved correctly in the file.
    2. Now to fiqure out what filter is changing this code

    Thanks and I will update when i can.

    Thanks

    Steve

    Thread Starter Steve Fulton

    (@cableguysteve)

    Morning

    I wanted to followup and let you know i found the issue. The Elementor plugin was causing the issue. I first developed the page using the plugin, took it back to the WordPress Editor and it worked perfectly.

    Please close ticket, don’t need Elementor on this page.

    Thanks

    Steve Fulton, UE

    Plugin Author Passionate Programmer Peter

    (@peterschulznl)

    Thank you your update Steve

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.