Tell us what you are trying to do?
I´m trying to properly integrate Toolset Maps and Forms with the Borlabs Cookie GDPR consent tool. At the moment it is not possible to block Toolset Maps using the automatic blocking function inside of Borlabs Cookie. But that´s o.k. The real problem is that I can´t find a proper way of blocking Google Maps scripts from Toolset Maps with the "script blocker" of Borlabs Cookie. I tried the exact same solution as in the mentioned ticket below - apart from using Borlabs Cookie instead of GDPR Cookie Consent Pro.
Blocking "wpv_addon_maps.js" alone is not working for me. For several hours I tried to block "wpv_addon_maps.js" and other js scripts from Toolset maps in addition to this file. Finally I found a solution which worked for this part. So far so good.
Unfortunately I also have a Toolset form on my website with an address field which is used to save the address/lat/lng of entries. I have the same problem with this field as it is also using google to get the coordinates of the address. Therefore it is necessary to block this field or form until the visitor has consented to the GDPR. I tried to integrate this form with Borlabs Cookie but I haven´t found a proper solution until now. As far as I have to block the maps scripts here as well it collides with the script blocking for Toolset Maps.
At the moment it is quite hard to implement a working solution which is respecting the GDPR. It would be super helpful if you could find a way to properly integrate with Borlabs Cookie or different solutions and to document that. Maybe it is possible to load the scripts in a different way so that it is easier to block them.
How can I achieve respecting the GDPR using Toolset Maps and Forms together with Borlabs Cookie? Your help is highly appreciated.
Is there any documentation that you are following?
I already tried to follow Bedas and Andreas advice in this ticket: https://toolset.com/forums/topic/toolset-maps-and-gdpr-cookie-consent-plugin-seems-to-conflict/
What is the link to your site?
I can create a staging site if this is helpful.
Thanks a lot in advance
Daniel
Hello,
The custom codes of the thread you mentioned above is for GDPR plugins: "GDPR Cookie Consent PRO" and " GDPR Cookie Consent PRO".
https://toolset.com/forums/topic/toolset-maps-and-gdpr-cookie-consent-plugin-seems-to-conflict/#post-1326825
We don't have any existed plan to integrate Borlabs Cookie plugin, you can submit a feature request for it:
https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/
Our developers will evaluate it.
I have searched it in google, and found below document of Borlabs Cookie plugin, it seems this plugin can use shortcode [borlabs-cookie ...] ... [/borlabs-cookie] to show/block other contents.
See their document:
hidden link
I suggest you try to follow their document to show/block the Toolset forms and maps shortcodes
https://toolset.com/documentation/programmer-reference/forms/cred-shortcodes/#cred_form
https://toolset.com/documentation/programmer-reference/maps/maps-shortcodes/#wpv-map-render
Since I don't have a copy of Borlabs Cookie plugin in my localhost, I can not confirm it myself.
Hi Luo,
thanks a lot for taking the time. Unfortunately I haven´t seen your reply until now. Sorry for answering late.
I know that the mentioned ticket is for another GDPR plugin but in a way they all work in a similar way and this was the only ticket which led in the right direction. Furthermore it shows all problems which probably all users building websites with toolset maps and customers in the european union will have. In germany Borlabs Cookie is one of the most popular GDPR plugins. But I guess the problem is not so much with Borlabs or any other special GDPR plugin. Maybe it would be sufficient to find other ways inside of Toolset to block/fire external scripts (especially Google Maps scripts). If there was more control then it would probably be possible to make Toolset GDPR compliant using any GDPR consent plugin.
Borlabs Cookie seems to work a lot like the GDPR Cookie Consent Pro as it has the same options and also a way of blocking external scripts. Also it has a way of blocking content using shortcodes. At the moment I´m using a combination of shortcodes and script blocking. If I´m only using shortcodes the map isn´t rendered correctly. This is probably related to the way and order in which "wpv_addon_maps.js" is loaded. Therefore I tried "approach 1" (https://toolset.com/forums/topic/toolset-maps-and-gdpr-cookie-consent-plugin-seems-to-conflict/#post-1326825) of the ticket which led to some success. But as far as I have to additionally integrate it with a form that is providing the address field it is even more complicated and doesn´t work as expected.
If you like I can provide you with a current version of Borlabs Cookie. It has a developer mode in which it can be used without activation. Alternatively I can create a staging development of my website.
I really appreciate your time and help. Thanks a lot in advance.
Daniel
It is confused.
1) Since you are using Borlabs Cookie plugin, it will use different cookie name and cookie value to store user's option
2) And the Borlabs Cookie plugin provides a built-in shortcode [borlabs-cookie] to check user's cookie, see the document I mentioned above:
hidden link
Why do you still need create other custom shortcode?
Hi Luo,
sorry for my late response. I have to check my preferences as far as I don´t get noticed if there is a new answer to this ticket. But anyway.
You are right. In fact it is confusing. The problem is that using the built-in google maps shortcode alone doesn´t work. The map won´t be rendered correctly. This is because of the way /order in which the google maps scripts (especially wpv_addon_maps.js) are loaded by toolset maps. Therefore it´s necessary to create a shortcode that uses a special cookie with a coresponding cookie category, a script blocker and reloading the page. If any one of these three ingredients is missing it doesn´t work. The situation is exactly like Beda describes it here: https://toolset.com/forums/topic/toolset-maps-and-gdpr-cookie-consent-plugin-seems-to-conflict/#post-1326825. Also the next comment of the author is important as it points out that reloading is necessary.
Thanks again
Daniel
Again, you can not use the same custom codes of "GDPR Cookie Consent PRO" plugin for your plugin "Borlabs Cookie", they are different plugins, it will not work, you will need to create other custom codes for your plugin "Borlabs Cookie".
Since it is a custom codes problem, and I don't have a copy of "Borlabs Cookie" plugin in my localhost, if you need more assistance for it, please provide a test site with the same problem, also point out the problem page URLs, and where I can edit your custom PHP codes, I need a live website to test and debug it.
