matchlessweb
Forum Replies Created
-
Forum: Plugins
In reply to: [Pie Calendar - Events Calendar Made Simple] Post Titles Not Updatable?Okay, I’m dumb. This was no bug at all, totally user error. Long story short, I wasn’t looking in the right place for the title change because I have a lot of posts that are sharing an identical name (it’s a volleyball tournament) and I just simply wasn’t looking in the right place for the title to change on the particular event day that I was expecting. User error, no bug.
I’d also love to be able to set page-specific display rules. +1
Forum: Plugins
In reply to: [WP Search with Algolia] Algolia Scripts BlockingThe same result happens if the scripts are delayed with Flying Scripts.
I imagine the plugin may require those scripts to load in their original position or deferred/async for the appropriate connection to Algolia’s API to be established?
Ahh that makes sense! Ok cool. I’m fully intending on buying the premium version of this plugin to be able to have this plugin configured for all regions in the world. I just want to be sure I can get the performance benefits of using Flying Scripts if I use the premium version of this plugin.
If I had this configured for GDPR, would it make those tracking scripts get blocked until someone clicks the “accept” button? I’m wanting to be extra sure this Flying Scripts configuration won’t break such a feature in Complianz.
I’d hate for my attempts at speed optimization to harm make my efforts towards compliance with these cookie-related privacy laws. I’m thinking I could safely purchase the premium version and experiment with this further.
I think I may just be confused about which events or custom events should fire from GTM before or after consent has been granted.
Hey Leon, I have done as you recommended.
I originally had things set up that way, but I was getting a “duplicate analytics” notice (maybe related to something I was doing wrong as discussed in this post: https://complianz.io/duplicate-implementation-of-analytics/) in the Complianz plugin dashboard in WP Admin, so I toggled it off and was just inserting my Analytics using GTM.
This is the current GTM preview link
It seems I’ve still got scripts firing before consent has been granted via clicking the “accept” button on the cookie banner. Any ideas what I might be doing wrong?
Do you think using Flying Scripts to delay the Complianz JS files until 5 seconds after the page has loaded is causing issues with Complianz plugin functionality?
Hi Aert,
Here’s a preview link of my Tag Manager setup: Preview here
One thing I experimented with since my original message is not allowing Complianz to handle my “statistics” as it’s labeled. I was getting a message saying I had duplicate analytics running on my site, so I’ve turned that off and now I’m just using GTM to inset my analytics code. Here’s a screenshot of the current tags (I know that screenshot alone doesn’t tell you everything about the tags): https://cln.sh/LXG4Ff
Presently, it seems only one facebook related cookie is being blocked before consent is granted by clicking the accept button on my cookie banner. I’m sure you can help me determine what I’ve configured wrongly here.
And FYI, I do still have all 3 scripts assoicated with Complianz being delayed by Flying Scripts as of this message.
Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] WP Rocket IntegrationPerfect explanation – thanks so much!
First test of delaying all 3 scripts resulted in the console error seen here: https://cln.sh/HcybCJ
Removing cookieconfig.min.js from Flying Scripts while leaving cookieconsent.min.js and postscribe.min.js gets rid of the console error, but I can see my GTM scripts are still firing before the accept button is clicked on the cookie bar. So maybe some other combination of delaying vs. not delaying these 3 scripts might be needed?
Or maybe my triggers for FB Pixel and Active Campaign are setup incorrectly? I’ve tried to setup the events triggers as described in this tutorial: https://complianz.io/definitive-guide-to-tag-manager-and-complianz/
But maybe I’ve done something wrong there since the scripts are still firing before the accept button has been clicked. Here’s a screenshot of my triggers for FB Pixel and ActiveCampaign Site tracking: https://cln.sh/ZPAKEw Let me know if that looks wrong (I’m sure it is).
I’m assuming the Google Analytics should also be blocked before consent is given, but I haven’t got a GTM trigger in place for that at the moment. So please let me know if that’s needed. I think I got confused by my duplicate analytics issue from my other thread related to this issue. So I removed the analytics trigger for now. I feel like I read somewhere in the documentation that some scripts are blocked by default by Complianz, so I’m unsure if I need a GTM analytics script to be inserted or not being that I already configured Complianz to use my GTM container to insert the scripts.
If you have recommended settings for the analytics trigger, I’m all ears 🙂
Also worth mentioning, the only thing entered in my Script Center settings is “activecampaign-subscription-forms” which I gathered was supposed to be there because I’m inserting my tracking script with GTM. Screenshot here: https://cln.sh/YbKoFD
This is the documentation on ActiveCampaign setup I followed:https://complianz.io/configuring-activecampaign/
Side Note regarding GTM categories: Though I’ve tried setting up custom event triggers in GTM, I don’t see these options appearing in my Complianz plugin settings:
I assume when setup correctly I should have the toggles appear in my cookie banner as seen in thie screenshot: https://cln.sh/wxIPTx from this article: https://complianz.io/definitive-guide-to-tag-manager-and-complianz/
Word vomit I know. Thanks for being patient with me as I try to wrap my head around making this work.
Ok, I’m going to give this a shot right now. I hope it works! I’m using the Perfmatters plugin to quickly identify scripts associated with the Complianz plugin: screenshot of the 3 JS files: https://cln.sh/mez1Qb
Scripts are:
cookieconfig.min.js
cookieconsent.min.js
postscribe.min.jsDo you think it’s safe to delay all three files using Flying Scripts? Or would any of them still need to load in their normal position while only delaying one or two with Flying Scripts?
Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Google Tag Manager – gtm.js 404Hey Aert, thanks so much. I was able to determine I had made a mistake in the Wizard.
I had indicated I’m using GTM to insert my Google Analytics tracking code but when it asked me to enter my Container ID I wrongly entered my UA- identifier (standard google analytics identifer) in that space.
That mistake appended my UA- ID to the end of the gtm.js file, which of course doesn’t exist and therefore was causing the 404.
I’ve now replaced the UA- identifier with the GTM container identifier and the 404 is no longer appearing.
Screenshot is of the step in the wizard where I had gone wrong. Now the correct GTM Identifier code has been entered there: https://cln.sh/4lw56t
And this screenshot shows my humble suggestion that might help others like me who tried to go through the Wizard too quickly on initial setup: https://cln.sh/xha5Ie
I failed to simply read the text that says “Google Tag Manager Code”. And I didn’t open the tooltip to see the words “Container ID”. If other people have made this mistake like me, I wonder if it would be helpful to include the verbiage “Container ID” or “GTM Container ID” in place of “Google Tag Manager Code” OR maybe put a placeholder in the form field that at least includes “GTM-” so users (like me who aren’t reading closely enough) don’t try to wrongly input their UA- code from their Analytics account like I did.
Loving this plugin! And I’m going to get it configured perfectly with you and your team’s help. So thanks for helping me out here. I really appreciate you.
Thanks for your response Rogier!
My only concern with removing the consent-requiring scripts from Flying Scripts is I’m afraid of my load times will taking a hit. And that’s the main reason I’ve got them delayed in the first place. Maybe that won’t happen if I remove them from Flying Scripts though.
I hope I’m not being dense here. Please correct me if I’m not understanding correctly.
For Complianz to work correctly, do its scripts have to load before any consent-requiring scripts?
I imagine loading consent-requiring scripts via my Flying Scripts setup could potentially make the cookies fire without user consent? Or is that incorrect? Maybe Complianz has to have that user interaction of clicking “accept” before letting any consent-requiring JS load – regardless of whether or not my Flying Scripts setup is trying to have those scripts execute after timeout of 5 seconds.
If I remove the consent-requiring scripts from Flying Scripts, are you saying they’ll be delayed until user interaction of clicking “accept” on the cookie notice bar occurs? effectively, I guess that would give me the same effect Flying Scripts is currently providing for those consent-requiring scripts?
In a perfect world (at least in my mind if I’m understanding how Complianz works) Complianz scripts could be delayed until the page has finished loading. And after that point, any consent requiring scripts would only be executed if a user accepts cookies via the cookie bar. So that would be a user interaction based delay instead of my Flying Scripts delay of 5 seconds after timeout.
Is that what you’re saying? I feel like I may have just said what you were getting at but in my own way, LOL. Please inform me otherwise if I’m missing it. Again, I’m just trying to have the best load times possible while still properly abiding by these cookie consent laws.
Hey Richard, thanks for the reply. I just found the issue and it had nothing to do with WP Search with Algolia.
In my attempts to optimize my site for fast page loads, I forgot that I had attempted to delay the execution of all Javascript associated with WP Search with Algolia by using the “Flying Scripts” plugin (https://ww.wp.xz.cn/plugins/flying-scripts/). It seems delaying the execution of this plugin’s JS breaks the autocomplete functionality of WP Search with Algolia, which totally makes sense. I reversed my Flying Scripts configuration for this plugin, and normal functionality has returned so all is well now.
I had originally attempted delaying the JS execution in hopes pages using the search widget wouldn’t be slowed down by having to parse that JS on page load.