Hanno

Hi @trejder,
seems as if this plugin is dead. No reply, no updates.
I switched to “Disable XML-RPC” by Philip Erb, this is extremely simple and does a good job. That plugin just adds a filter, so there are no issues with compatibility with current WP versions at all …
CU Hanno

Issue solved!
I am using the ACF plugin which you have listed in your Integrations – Plugins tab, activated by default. With this activation revoked (plugin does not have to be deactivated), wpgmaps Pro runs ok.
Thanks for your time, highly appreciated!
Cu Hanno

• This reply was modified 4 years, 5 months ago by Hanno.

I have sent screenshots of the wpgmaps and Complianz settings to your mailbox. I also included a map export (json).
Regarding the js url, I don’t know where it should be blocked. I have registered for this API, and Google console shows quite a few API calls, without any errors.

Hi Rogier,

FYI, usually I use WP Fastest Cache, but I had already switched it off before.
Unfortunately, it makes no difference if the Cache is active, or switched off with the plugin still active, or the plugin deactivated. Just to be sure, I also purged the browser cache again before every try.
Right now, the plugin is deactivated.
The Complianz, and wpgmaps, settings are as required. I thought of sending you screenshots to give you an opportunity to compare. This will take a few hours as I am currently out of office. If you think this wasn’t necessary please let me know.
Tx – Hanno

Hi Rogier,
Steven from WP Google Maps just told me that he has sent a copy to your email address. Please check your inbox.
– Hanno

Hi Rogier,
you’re definitely right. I’ll send a copy of your email to wpgmaps support, they will contact you ASAP, I’m sure.
Tx Hanno

I understand. No problem, we will have another try then.
After blocking wp-google-maps-pro.min.js, wp-google-maps-pro/js/core.js no more console error, but a warning instead:
Something went wrong TypeError: WPGMZA.RestAPI is undefined
No fake map, no real map, just blank screen

Hi Rogier,
this makes it even worse – no more fake map for users without cookie agreement, two more UncaughtReference Errors: WPGMZA is not defined

Sure, but then I would have to create the entire CSS myself, wouldn’t I?

I did so already. Still I think, although providing this icon is a good thing in general, any option to switch it off would be a great thing.
Tx Hanno

Thank you for your reply.
I changed one page to using the WP Google Maps plugin instead of the Divi module.
It works as it should, although I am not very keen on implementing one plugin after another, if there is a built-in solution one could use. Every plugin brings its own security risks.
BTW, please have a look at this info which shows below the Google Maps window:
Um Google Maps-Cookies zu aktivieren, bitte auf ?Ich stimme zu? klicken
The question marks should be German opening resp. closing quotation marks. Don’t know where the problem is, the .mo file has the correct characters.
CU

I could also provide you with a complete sourcecode of one of the webpages affected, if that would be of any help for you.
If so, please advise how to proceed.

• This reply was modified 4 years, 6 months ago by Hanno.

Well, that example does not help. I use Divi page builder, and the philosophy of implementing Google Maps seems to be quite different from that of Elementor, which you use. Especially, there is no iframe object which, as I see it, is the main hook for your blocking mechanism. Instead, the Divi module uses a script link to googleapis.com/maps, which I can’t find at all in your demo site.

Here comes the link:

<a href="javascript:;" data-enc-email="unaab[at]obygr.qr?fhowrpg=Jrofvgr%20|%20Oyügratnyrevr" class="bo_mail" data-wpel-link="ignore">"></a>

The ‘class’ entry is voluntarily defined by the WordPress admin (not always present!), ‘data-enc-email’ contains the encrypted email address, subject asf.
Hope that helps.

• This reply was modified 4 years, 6 months ago by Hanno.

Hi Rogier,
unfortunately the site is still under construction and not yet online. As there are certain restrictions on Google Maps API, we will probably have to wait until the site is accessible from outside.
I will get back to you later.