we’ve encountered a strange loop problem with the cmplz-consent-area shortcode. It loads the site perfectly fine when accepting the cookies, and when blocking them afterwards as well. BUT if we accept the cookies a second time an infinite loop is created jumping from the regular URL to the /?cmplz_consent=1-URL.
We’re using WP Fastest Cache on that site and have already set the “cache_redirect=true” attribute in the shortcode. Is there anything else we can try?
Thanks in advance, Lisa
The page I need help with: [log in to see the link]
I have WP Fastest Cache fully enabled without issues.
I would expect its not WPFC at all, disabling WPFC and trying the consent block again should confirm it still doesn’t work. So WPFC is then excluded from the issue.
If it works, we can have a look at the exclusion in WPFC.
unfortunately not. I compared the websites with the same problem and these always have the cmplz-consent-area shortcode on the page and WPFC active. I thought WPFC is the problem but the infinite redirect has not been solved when I disable the caching for the page. It only works if I remove the shortcode completely from the page. I have sent you our website by e-mail because I don’t want to share the URL. Do you have an idea which plugin could cause problems with Complianz?
My colleague did respond to your e-mail about this, in which he shared a link to a test site using the Consent Area shortcode with WPFC (everything enabled/no exclusions); but we weren’t able to replicate the issue here yet.
We therefore asked how we might be able to apply the [falke_facebookteaser] shortcode ourselves, to get the issue to occur on our end as well.
I did notice the following, though. It appears that when I block “falkeScript.js” in my own browser using the Network Request Blocking option in Chrome DevTools:
And then try to replicate the behavior again with the steps you provided (accept cookies for a second time, which previously caused the issue to appear rather consistently): it does not seem to happen any longer.
If it’s indeed related to your custom code, that would explain why it wasn’t resolved by changing WPFC settings; and why we could not replicate the issue on our end.
Hi @jarnovos, I didn’t receive an email from your colleague. The infinite refresh occurs without the [falke_facebookteaser] shortcode and blocking our falkeScript.js too. I have now adjusted the code so that our javascript on the page is not loaded at all. The problem still occurs.
Really strange, I’ve been attempting to replicate the behavior with the same shortcode parameters that you’re using, but it never happens for me.
As you’re now no longer caching the page in question, perhaps you could test the behavior without the cache_redirect=true parameter, and check if clientside=true works better for your use case?
As for the cause, unfortunately I don’t really have further leads at the moment. I can only recommend further narrowing down the potential causes, for instance by disabling integrations under Complianz -> Integrations & disabling plugins one-by-one, until the issue no longer appears. At which point you’ll know that one of the items that you disabled was likely related to the behavior.
One last thing that I noticed is that many scripts on your site get the parameter ?falkeTS appended them, and the latter appears to be a timestamp. It would appear that this is part of caching or an optimization that’s still enabled on the page.
As the described reload behavior with the shortcode, will in almost every case be related to some form of caching, this is also something that I would recommend ruling out as being potentially related.
Hope this helps with your troubleshooting efforts!
Kind regards, Jarno
This reply was modified 2 years, 10 months ago by Jarno Vos.
Viewing 14 replies - 1 through 14 (of 14 total)
The topic ‘cmplz-consent-area shortcode infinite loop’ is closed to new replies.
