• The plugin uses their own Google Maps API key on the admin which is hardcoded in the code. This was conflicting with the key we use for Advanced Custom Fields. The funky “Chat with us!” support link goes to a page with an expired SSL certificate. Not cool.

Viewing 1 replies (of 1 total)
  • Plugin Author DylanAuty

    (@dylanauty)

    Hi @martinsotirov,

    Dylan here from the development team. Thank you for taking the time to bring this to our attention.

    My sincerest apologies for the trouble experienced with our chat system, I have reported this to the relevant team members to be resolved as promptly as possible.

    With regards to your issue with the Google Maps API which we include with the plugin by default, this is correct, by default we load a basic API key which we manage as this allows for basic first-time interactions with the map editor and interface.

    With that said, this key should be updated with your own key under Maps -> Settings -> Advanced -> By adding it to the relevant API key field. Once added, our bundled key is disabled entirely.

    We would really like to discuss any conflict you are seeing with ACF prior to updating the field if you are open to it. Could I ask you to reach out to me on our websites contact page? This will allow us to discuss this with you in a bit more detail.

Viewing 1 replies (of 1 total)
  • The topic ‘Sloppy code, bad support’ is closed to new replies.