Store Locator Plus® for WordPress Forums Store Locator Plus Display Map and search form Problems

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #55296
    info205
    Participant

    We are running the latest versions of the Store Locator Plus and Store Locator Plus – Pro with the latest version of WordPress and are having lots of functionality issues.

    https://toegrips.com/retailers/

    Sometimes the map does not appear at all and the search does not bring back any results,

    Please help!

    • This topic was modified 6 years, 4 months ago by Cici.
    • This topic was modified 6 years, 4 months ago by Cici.
    • This topic was modified 6 years, 4 months ago by Cici.
    #55320
    Cici
    Keymaster

    Could you provide your Plugin Environment?  If you are referring to proPack, there is another forum post that explains that the ProPack Legacy add-on is not compatible since SLP version 4.8. See previous Post.

    #55369
    info205
    Participant

    We are not using the propack. We have the power plugin, which we used only to export/import the contacts. Please see attachment for Plugin Environment into. Thank you!

    • This reply was modified 6 years, 4 months ago by info205.
    Attachments:
    You must be logged in to view attached files.
    #55378
    Cici
    Keymaster

    Your initial post said PRO, not Power, thus the answer about legacy

    Is this your site url that has thSLP on ?

    https://toegrips.com/retailers/”

    I just typed in zip code 51250 within 500 miles for radius because I have no idea where your locations are and I see a return of more then a half dozen sites and showed the map with all the map markers…so could you tell us what isn’t working from your perspective?

    If you are seeing it sometimes and not others have you checked to make sure you are not over your query limit on those occasions?  If you are on a shared server, the number of queries allowed counts for all searches, geocoding etc.

     

    You do have these errors under your console:

    Uncaught SyntaxError: Invalid or unexpected token

    (index):1 Uncaught SyntaxError: Unexpected identifier

    at 764b8718a8c3fa3e9d8cb8869404ffc8-deanedwards.js:8

    toegrips.com/:152 0

    toegrips.com/:172 0

    ping:1 Can’t Load URL: The domain of this URL isn’t included in the app’s domains. To be able to load this URL, add all domains and subdomains of your app to the App Domains field in your app settings.

    VM233:1 WPP: OK. Execution time: 0.002031 seconds

    4util.js:37 [Violation] Added non-passive event listener to a scroll-blocking ‘touchstart’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952

    _.gC @ util.js:37

    MN @ controls.js:30

    YN @ controls.js:37

    _.ZN @ controls.js:40

    lO @ controls.js:51

    mO @ controls.js:50

    EP @ controls.js:97

    _.m.ea @ controls.js:145

     

    (anonymous) @ VM235:1

     

    Check

    • This reply was modified 6 years, 4 months ago by Cici.
    Attachments:
    You must be logged in to view attached files.
    #55446
    Cici
    Keymaster

    Anything that breaks javascripts will cause SLP to fail. Your cachescripts is showing as failing. Yo and stopping the load. The reason you see SLP map and search work sometimes and not others is because there is no order as to when plugins run , if they run first second or last….if you have a plugin that has  broken javascript and that fires off  the GET function  before SLP, then no map etc because your site broke before it could load SLP.

    You will  need to Debug. if you need the delveloper to log into your site and troubleshoot and/or fix that is under a paid support option . If it is a complex issue that requires more , please refer your request to Cybersprocket.  unfortunately, there is nothing we can do without  admin credentials.

    https://docs.storelocatorplus.com/blog/debugging-with-debug-log/

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