Hi @bitcoincasino666,
I think the error may indeed be related to an optimization in WP Rocket, as the error does not appear when visiting your website with ?nowprocket added to the end of your URL.
You can find which setting causes it by disabling optimizations in WP Rocket one-by-one, clearing cache and checking the front-end after each change, to see if the error disappears upon doing so.
If the issue disappears upon disabling a feature, you’ll know exactly which feature causes the issue. You can then exclude Complianz from that feature by adding complianz to the list of exclusions.
Kind regards,
Jarno
Hi Jarno,
I have done this please can you confirm that the error is removed and that the plugin is now correctly installed and everything working as it should.
Many thanks
-
This reply was modified 4 years ago by
James Huff.
-
This reply was modified 4 years ago by James Huff. Reason: redundant link removed
@bitcoincasino666 For the third time, please stop repeatedly including your links outside of the proper field in the original post.
If you have more to add with a different link, that’s fine, but yet again your reply included the same link as you originally listed in the proper field.
That’s spammer behavior, which of course is not allowed here: https://wordpress.org/support/guidelines/#do-not-spam
If this happens again, your account will be banned.
If you have any questions, you can reach the Moderators in the #forums channel on our Slack instance: https://make.wordpress.org/chat/
I am sorry for the mistake I made of posting the URL, it is not my intention to spam, I thought I was helping out Jarno as I did not see that I had posted it.
Plugin Author
Aert
(@aahulsebos)
Hi @bitcoincasino666,
I’m not currently seeing an error. WP Rocket and Complianz should work well together, however deferring all scripts might cause issues on some configurations. I would start by disabling delay/defer scripts in WP Rocket and see if this works,
regards Aert
I currently do not see any errors (safari, firefox, chrome), so the issue seems to be solved. If you do have any errors, please disable optimizations in WP Rocket one-by-one as described by Jarno previously until the issue is resolved.
