- This topic has 0 replies, 1 voice, and was last updated 2 hours, 22 minutes 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,
HaNeulChi
