Markers not showing up in map with Breeze caching enabled

This topic contains 13 replies, has 3 voices, and was last updated by  David Hahn 4 years, 5 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
  • Author
    Posts
  • #517782

    David Hahn
    Full Member
    Post count: 18

    We’re using GeoDirectory 2.0.0.69 on a site hosted at Cloudways. When activating the Breeze plugin, the markers don’t show on the map to users that are not logged into the site. Instead, they see a “No Records Found” message. (Actually, sometimes they will see the markers, like maybe the first time they load the page, but subsequent reloads show no records found.)

    I’ve read through some of the other threads with people having similar problems (like #516409) but most of the replies are private so I’m not sure what the final resolution was, if any.

    I have tried clearing the Varnish cache as suggested, and also tried with Varnish disabled at the server level, but that didn’t solve the problem.

    I have found that GeoDirectory works as expected with the Gzip and Browser Cache options in Breeze enabled, but as soon as the main Cache System is enabled, that’s when the problem occurs. Disabling the Cache System restores the correct marker behavior.

    Any insight on how to make GeoDirectory and Breeze play nice together?

    #517817

    Alex Rollin
    Moderator
    Post count: 27815

    Hello,

    Please share site credentials so we can check into the issue.

    You say enable the main cache system and no more map markers, right?
    Anything else to replicate the issue?

    #517834

    David Hahn
    Full Member
    Post count: 18
    This reply has been marked as private.
    #517843

    Alex Rollin
    Moderator
    Post count: 27815

    Thanks, the developers will take a look.

    #517896

    Kiran
    Moderator
    Post count: 7069

    Hi David,

    I checked and found there is an error on page “You have included the Google Maps JavaScript API multiple times on this page. This may cause unexpected errors.” when markers are not loaded on page.

    Do you have any plugin expect GeoDirectory that uses Google map?
    I can’t check plugin manager in backend due to lake of full admin access. Provide us full admin access and FTP credentials to look into more.

    Regards,
    Kiran

    #517935

    David Hahn
    Full Member
    Post count: 18

    Hi Kiran,

    Yes, it looks like they have a plugin named “MapPress Maps for WordPress”, I have no idea where that is used on the site (they have an obscene number of plugins.) I have went ahead and deactivated it and cleared out the cache, and I also gave you super admin at the multisite level, so you should be able to look at anything. (Again, this is a dev clone of their live site, so don’t worry about breaking anything.)

    But in my brief testing here, it looks like deactivating that MapPress plugin fixed the problem, with caching on I can reload the GeoDirectory page over and over and the markers appear as they are supposed to. I’ll contact the client to ask them where they are using that MapPress plugin.

    #518087

    Kiran
    Moderator
    Post count: 7069

    Thanks for letting us know.

    Kiran

    #518158

    David Hahn
    Full Member
    Post count: 18

    Hi Kiran,

    Upon further testing today, MapPress doesn’t seem to be the problem. With the MapPress plugin disabled, I cleared the caches, loaded up the GD page, and after doing a page reload the markers are gone again and the “no records found” message is displayed. Not sure why it was surviving multiple page reloads yesterday when I tested, but it seems once you clear the cache, it works once then “no records found” for all subsequent reloads.

    So I still have MapPress disabled anyway, but you can go back in and do some further investigation. (I also did further testing in Chrome and Firefox, and found the same behavior in all browsers.)

    #518173

    David Hahn
    Full Member
    Post count: 18

    Also curious: did you find a solution for the person having a similar problem in post #516409?

    #518250

    Kiran
    Moderator
    Post count: 7069

    Hi,

    I have page refresh few times after clearing browser & site cache, but could not replicated issue again.

    I seen following some JavaScript errors in console.
    – You have included the Google Maps JavaScript API multiple times on this page. This may cause unexpected errors.
    – TypeError: $ is not a function
    – TypeError: “$select2.data(…).$container is undefined”

    Please try again and if still see problem, then provide us FTP credentials to look into more.

    Regards,
    Kiran

    #518272

    David Hahn
    Full Member
    Post count: 18
    This reply has been marked as private.
    #518363

    Alex Rollin
    Moderator
    Post count: 27815

    The developers will take another look as soon as possible.

    #518593

    Kiran
    Moderator
    Post count: 7069

    Hi David,

    I have done some debugging and found Breeze caching changes the content-type of the map markers ajax response. With Breeze caching it changes the content-type of the map markers ajax response from “application/json; charset=UTF-8” to “text/html; charset=utf-8”. This creates trouble in rendering markers data on map.

    The content type for json response should be “application/json; charset=UTF-8”.

    I have found some stuff and added “/geodir/v2/markers/” in Settings > Breeze > ADVANCED OPTIONS > Never Cache these URLs. I tried several times and now i can’t replicate issue anymore.

    Please try now from your side. If you see issue again then contact Breeze team that why it changing the content-type of the response.

    Regards,
    Kiran

    #518622

    David Hahn
    Full Member
    Post count: 18

    Hi Kiran,

    So far in testing, it looks like never caching /geodir/v2/markers/ addresses the problem. I’ll let you know if anything comes up again.

    Thanks.

Viewing 14 posts - 1 through 14 (of 14 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket