Customer location as Geolocate with page caching issue

  • Resolved akashthakor

    (@akashthakor)


    3 years, 5 months ago

    Hi there,

    I’ve a website with multi-currency integration on woocommerce. In backend woocommerce > general > Default customer location need to be set as Geolocate (with page caching support) so that users get the precise currency with caching in website. If I change this option to only geolocate then multi-currency is not working properly with caching. But If I set default customer location to Geolocate (with page caching support), my website loads twice for the first time. As in if someone open any page from browser it loads twice on first time and if we reload it then it works fine.

    I’ve already deactivated all other plugins and tested it, but issue still persists. I got to know by testing that the string (?v=xxxxx) which is added by Geolocate (with page caching support) is the reason for multiple loading. Is there any way to resolve it?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Grigorij S. a11n

    (@grigaswp)

    Hi there,

    Thank you for reaching out!

    I’m sorry to hear about pages loading twice when the default customer location is set to Geolocate (with page caching support).

    Can you please specify which multi-currency plugin you’re using and if you’ve tried disabling it?

    On my test site, I was not able to replicate this behaviour so it sounds like it is isolated to your WordPress/WooCommerce install.

    Next, I’d suggest disabling all plugins except for WooCommerce, switching to a default Storefront theme and checking if the site still loads twice.

    If it doesn’t with the multi-currency plugin disabled but it loads twice with that plugin enabled – you may want to report this behaviour to the support team of that plugin.

    If the site doesn’t load twice with a default Storefront theme but it loads twice with your theme – you may want to report this behaviour to the support team of your theme.

    https://docs.woocommerce.com/document/how-to-test-for-conflicts/

    Let us know how that goes!

    Thread Starter akashthakor

    (@akashthakor)

    Hi there,

    Thank you for the reply!

    We are using a module from Booster for Woocommerce plugin. In local I have tested the issue without the plugin(Booster) and also tried to test it in default theme but I am facing the same issue there! There’s only one plugin is activated(Woocommerce) with default theme, still I am facing the same issue.

    Was there ever an resolve here? I am facing the same issue and will be publishing soon. Suggestions beyond what is discussed here?

    best regards, “K”

    Looks like this may have been addressed already in another thread, so for those of you searching:

    `The browser’s navigator function that GEO my WP depends on when getting the current location is trigger via the client-side. Which means only after the page was loaded.

    So the page must first load, then the navigator is triggered via JavaScript and saves the user’s location in cookies. The page will then reload and use those cookies to display locations nearby the user’s location.

    It should be possible to disable the page reload using a filter, but that means that the map will show locations based on the user’s location only after the user reloads the page.`

    Mirko P.

    (@rainfallnixfig)

    Hi @ksteele36,

    Thanks for sharing that part that could also be useful for others. If you have any other issues please open your own topic as it’ll be easier to follow for us.

    Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Customer location as Geolocate with page caching issue’ is closed to new replies.