DylanAuty

Hi @nlogica,

Thank you for getting in touch, we do appreciate your time! ??

Yes, it is possible to disable both of these, along with a few other controls, directly within our settings area. Please head over to Maps > Settings > General Settings > And you should see options such as:

• Disable StreetView
• Disable Map Type Controls
• Disable Full Screen Control
• Disable Zoom Controls
• Disable Tilt Controls

These options can be switched on, in order to disable those controls within the map itself.

I hope that helps?

Hi @haleybrandshack,

Thank you for getting in touch, we do appreciate your time. I am sorry you are having trouble switching back to the Google Maps engine. Just to confirm, what happens when you navigate to Maps > Settings > And change “Maps Engine” to “Google Maps”?

Does the page revert the changes after reloading, or are the changes saving, but the map engine is not updating on the frontend?

This will help me determine which part of the system is not accepting the change, and we can debug this a bit further.

Thanks for confirming @djkavaa – We do have some improvements planned for our website, so keep an eye out for those! ??

Hi @djkavaa,

Dylan here from the development team, we’ve been speaking directly via email as well.

Thank you for bringing this to our attention. We’ve located a bug in our auto-loader which seems to be effecting a subset of users, where a specific PHP module is not behaving as expected when enabled. We have fallbacks for this in place, but it seems in some cases they do not activate in time to prevent a failure.

This doesn’t appear to be a widespread issue at the moment, but it is one that we will be dealing with as soon as possible, in a more permanent way. I did reply to your email as well, stating that I have implemented a workaround on your site for the moment.

The full patch for this will also be included in our next basic update, to ensure this does not resurface again in the future.

Hi @fidanb,

Thank you for getting in touch, we do appreciate your time. I’m sorry you’re having trouble with your locations.

Can I ask you to share a link to your site with us, so that I can run a few tests from my side to determine how the marker data is being managed at the moment?

Hi @snehminz,

Thank you for getting in touch, we do appreciate your time. Unfortunately, we don’t have settings built into the plugin to achieve this specifically, however, it may be possible to achieve some of this with minor custom scripts to hide the store locator search once a search is performed, and open the first marker matched to the query.

Could you share a link to your map so that I can take a look at your configuration to determine if this is something we can help with?

Hi @virtualnomad,

Thank you for getting in touch, we do appreciate your time. Unfortunately, as your issue related to our Pro add-on, I will need to ask you to get in touch via our website instead.

As per the www.ads-software.com guidelines, these forums are reserved for support directly related to our basic plugin and we are not allowed to discuss or support our Pro version here. With that said, we’d be more than happy to assist you directly instead.

Please note: We will be marking this thread as resolved, as per the guidelines mentioned above.

Thanks for getting back to me @stevenblake – I do appreciate it, and I’m eager to get this resolved for you.

I just ran a test on that page in Chrome, Edge and Firefox, and the map does seem to be working for me in all three of those cases. Can I ask you to confirm if you see the same issues when viewing that page incognito/private window?

It’s possible that some of the resources we load are being cached by browser caching, which may make it appear as if the map is not functional for all users, when it may be for a select set of users who have visited the site before. This is tends on sites which use caching solutions (it looks like you do use WP Rocket), in which case the caches may need to be fully cleared between updates.

We do try and trigger cache clearing automatically, but this is not always respected by caching solutions. If you find you are still seeing the issue on your end, clearing your cache may allow us to see the issue on our side, as it is currently working as expected.

Hi @stevenblake,

Dylan here from the development team. I received your ticket this morning and replied there as well.

We’re very sorry you’ve experienced issues after updating, we’d be interested to learn more about what IONOS had to say in terms of compatibility as we don’t have any known incompatibilities with server environments. That is to say, in most cases if your environment supports WordPress core, it should also fully support our plugin code base.

If you don’t mind sharing more information in your reply to my email, I’d be happy to work with you closely in solving this in our next update. Based on the information you’ve shared, we suspect there may be some configuration on your server, such as a PHP package/version which we might need to adjust for slightly.

Hi there,

Thank you for getting in touch, we do appreciate your time.

Unfortunately, this is not possible with our basic plugin, however, we do have an add-on available which may be a good match for this. Please take a look at our website for more information, and if needed, please do reach out to us via our contact page so that we can discuss this further.

We are not allowed to discuss any paid add-ons in detail via these support threads as they are reserved for our basic plugin and supporting it instead. As a result, this thread will be closed and marked as resolved, but we look forward to hearing from you directly.

Hi @lolcabanon,

Fantastic, I’m glad to hear this has been resolved, thank you for letting me know.

With regards to the Pro update, unfortunately, as per the www.ads-software.com guidelines, we are not allowed to discuss or provide any support for Premium add-ons via these threads, meaning the best way forward would be for you to contact us on our website.

That will allow us to assist you directly and explain some of the details. I do apologize for the run around in that regard.

Hope to hear from you soon!

Thank you for letting us know @debsher – Glad to hear things are back to normal! ??

Hi all,

We have just updated the plugin to resolve this issue in instances where the add-ons are not fully up to date. Please update to version 9.0.43 to resolve the issue.

Once updated the plugin will check to ensure that the add-ons are up to date, and if they are not, we will not apply the Divi check at all, meaning the error will no longer occur. With that said, I would like to ask that you both also reach out to us on our website so that we can help get your add-ons up to date.

@lreyes13 @debsher

Hi all,

We have just updated the plugin to resolve this issue in instances where the add-ons are not fully up to date. Please update to version 9.0.43 to resolve the issue.

Additionally, if you haven’t already, please reach out to us on our website so that we can get your add-ons up to date as well.

Please do let me know if you are still experiencing issues after updating. ??

@mach4design @lolcabanon

Hi @debsher & @lreyes13,

Thank you both for bringing this to our attention. We have identified the cause of this issue and the team and I are working on a priority update to resolve this within the next few hours.

I have posted a bit more detail about this here: https://www.ads-software.com/support/topic/divi-error-as-of-10-15-2024/

I will let you both know via this thread once the issue has been resolved. Thank you for your patience.