Hi LauGau.
Script blocking should work just fine. I will tell you what the problem might be, but there is one thing you should know before that.
Blocking script by the main domain (like “hubspot.com) is not a good idea. Full Picture will block all the script from hubspot – even the ones you don’t want to block. Try to provide exactly the URL you want to block, e.g. https://www.googletagmanager.com/gtm.js or, if it doesn’t work, block by the script’s content. I found the second method to work especially well. Simply tell FP to block script by the unique ID that you use in, e.g. Google Analytics or other platforms.
And now, let me give you the possible reasons why blocking can fail:
- The script is added dynamically by a different script after the page loads. In such case you should block that original script.
- There is some condition that forces the script to be loaded. For example, if you choose to block the script only in Germany while you are in Singapore, then you will see the script as usual.
I hope it helps 🙂 If you have any more questions, just ask. I may not be available later today (and tomorrow) but I will reply on monday.
Thread Starter
LauGau
(@laugau)
Thanks for your swift reply especially during the weekend 🙂
I imagine that blocking the whole domain is a bit “too much” but I am desperate to have the plugin working…
I added all the urls in the “Sources” devtools but it’s not working either… Also, I didn’t use any conditions that may force the scripts to load.
How can I backtrack what’s going on ?
If you are doing everything correctly, then the problem may be with conditions that need to be met to load these blocked scripts.
Please tell me:
- Do you use WP Full Picure’s cookie notice?
- If you do, did you mark what types of cookies the blocked scripts require? Next to the text “What does this script use visitor’s data for?” in the settings of blocked scripts.
- Is the notice set to block tracking scripts until you agree to cookies in the notice?
Thread Starter
LauGau
(@laugau)
- Yes I use the cookie notice module
- All scripts are set with either “analytics” or “Marketing” but most have both “Analytics” and ” Marketing” checked (a bit randomly for testing).
- The Cookie notice it is set to : “Start tracking when visitors agree to cookies”
Note that I installed the plugin on a live website and the problem is the same…
-
This reply was modified 2 years, 11 months ago by
LauGau.
Hmmm… I wish I could see your site but since it is local, I can’t do it…. Please contact me directly using the contact form on WP Full Picture. I will try to help you.
Thread Starter
LauGau
(@laugau)
Thanks for your support! I just sent you a message from your form.
Hi LauGau. The latest update of WP FP lets you manage loading links and images so it should help you conditionally load all tracking tools that you need (except those added to HTML by Cloudflare). Please let me know if you need anything else.
Have a great day!
Thread Starter
LauGau
(@laugau)
I just come back to let you know that Chris is really committed to make WP Full Picture the best plugin to tackle the headaches caused by the RGPD implementation. He took time to explain how this plugin work. Everything is solved now. Not that it’s not a magic wand neither : it cannot block scripts loaded directly from the edge like Cloudflare… but it’s perfectly understandable. Thank you again!
Wow! Thank you very much 🙂 It’s great to hear that you like it! It increases my motivation to work on the plugin event more. If that’s ok with you, can I ask you to write a short review in the plugin’s reviews section? At the moment there are only 6 reviews there so another one would make a difference 🙂
I am going to mark this issue as resolved, however if you have any other issues, just open a new topic and I will help.
Have a great day LauGau!
