- This topic has 5 replies, 2 voices, and was last updated 5 days, 16 hours ago by
.
Compatibility Issue: Complianz Policy Page Auto-Generation Conflict (Jevelin/WPBakery/Contact Form 7)
Dear Jevelin Support Team,
I hope this message finds you well.
I am writing to report a compatibility issue encountered on my site, which runs the Jevelin theme, WPBakery Page Builder, and the Complianz GDPR/Cookie Consent plugin.
The Original Conflict (Complianz Auto-Generation Failure)
The core issue occurred during the Complianz setup wizard when the plugin attempted to automatically generate the necessary Cookie Policy and Privacy Policy pages.Instead of generating the correct policy content, the pages were corrupted.
The shortcode output was incorrectly pulling and displaying content from a Contact Form 7 form present on the site, including form fields, email addresses, and mailto: links.
Resolution Provided by Complianz Support
The support team at Complianz confirmed the conflict and provided a two-part workaround to bypass the issue.Manual Page Creation (Fixing Content):
Stop using the Complianz automatic page generation feature.
Manually create the policy pages (e.g., “Cookie Policy EU” and “Privacy Policy UE”).
Manually insert the relevant Complianz shortcodes into those pages (e.g., [cmplz-document type=”cookie-statement”] and [cmplz-document type=”privacy-statement”]).
JavaScript Snippet (Fixing Links):
They also advised adding the following JavaScript snippet to force the links in the cookie banner to the correct, manually created page URLs:
JavaScript
document.addEventListener(“DOMContentLoaded”, function() {
// Define custom URLs
const customUrls = {
cookieStatement: “https://uglyfish.it/cookie-policy-eu/”,
privacyStatement: “https://uglyfish.it/privacy-policy-ue/”
};// Replaces the URL for cmplz links
document.querySelectorAll(“a.cmplz-link.cookie-statement”).forEach(function(link) {
link.setAttribute(“href”, customUrls.cookieStatement);
});// Replaces the URL for privacy-statement links
document.querySelectorAll(“a.cmplz-link.privacy-statement”).forEach(function(link) {
link.setAttribute(“href”, customUrls.privacyStatement);
});
});I wanted to share this detailed discovery with your team. Since this major conflict was resolved by manually bypassing the Complianz automatic page generation feature, and the secondary link issue required a JavaScript workaround, it suggests there might be a point of interference within the Jevelin/WPBakery environment.
Thank you for your attention to this issue.
Best regards,
HaNeulChiHello,
Thank you for sharing the detailed information. We haven’t encountered this issue before, and we don’t use Complianz in our testing setups, so we haven’t been able to reproduce it on our side yet. Since the incorrect content appears during Complianz’s automatic page generation, before Jevelin or WPBakery modifies anything, it seems to come from how the plugin processes content rather than from the theme or builder.
If you can provide the exact steps you followed in the Complianz setup wizard to trigger the issue, we can try to replicate it in a clean test environment. This will help us see if there’s anything on the theme side contributing to the conflict.
Best regards,
Shufflehound team
Hello Shufflehound Team,
Please accept my apologies for the delayed reply. I’m not sure why my previous message didn’t send or wasn’t received; I thought I had responded earlier.
Thank you for your quick response and your willingness to investigate.
I understand your reasoning that the issue seems to originate from Complianz’s automatic page generation process, before the theme or WPBakery get involved.
To answer your request: there were no special steps taken, other than the standard Complianz setup wizard (guided procedure).
The error occurred exactly when the Complianz setup wizard, upon reaching the final phase, attempted to automatically create the “Cookie Policy” and “Privacy Policy” pages, asking the user to confirm the data and pages to be generated.
In summary, the steps were simply:
- Install and activate Complianz.
- Start the setup wizard (guided procedure).
- Follow all steps until the plugin asks to automatically create the policy pages.
- Upon completion, the automatically generated pages were corrupted.
I hope this confirmation helps you to reproduce the issue in a clean test environment.
I look forward to your update.
Best regards,
HaNeulChi
Hello,
Thanks for the extra details.
We tried to reproduce this on our end and we can see something similar happening during the Complianz wizard, but we still cannot find the exact cause. We did some checks and basic debugging, but didn’t find what could cause this.
For now, we recommend continuing with the workaround you received from the Complianz team. The manual policy pages with the Complianz shortcodes, plus the link override if needed, looks like the most reliable way to avoid the corrupted auto generated content.
Best regards,
Shufflehound team
Hello Shufflehound Team,
Thank you for the update and for taking the time to test this on your end.
It is reassuring to know that you were able to reproduce a similar behavior in your environment. Even though the root cause isn’t fully clear yet, knowing it wasn’t an isolated incident on my side is helpful.
As suggested, I will stick with the manual workaround provided by Complianz, as it is working stable for now. I hope this report remains useful for your development team to potentially address this conflict in a future theme update, to help other users avoid this friction.
You can consider this ticket resolved for now. Thanks again for your support.
Best regards, HaNeulChi
