Cache and Plugin Conflicts

This guide helps you troubleshoot caching issues and conflicts with other WordPress plugins and themes.

Caching Plugin Conflicts

Symptom

Landing pages not updating, displaying incorrectly, or analytics not working due to caching.

Common Caching Plugins

WP Super Cache

Problem: Landing page changes don’t appear, cached version shown.

Solution 1 – Clear Cache:

1. Go to Settings → WP Super Cache
2. Click Delete Cache button
3. Visit landing page to verify changes

Solution 2 – Exclude Landing Pages:

4. Go to Settings → WP Super Cache → Advanced
5. Find Rejected URIs section
6. Add landing page URLs (one per line):

`
/landing-page/
/lp/
/offer/
`

7. Or exclude all ShahiLandin pages:

`
/shahi-landing/
`

Solution 3 – Disable for Dynamic Content:

8. Advanced tab → Don’t cache pages for known users (check)
9. Advanced tab → Don’t cache pages with GET parameters (check if using experiments)

W3 Total Cache


Problem: Landing pages cached with wrong content, A/B tests not working.

Solution 1 – Clear All Caches:

10. Go to Performance → Dashboard
11. Click Empty All Caches
12. Test landing page

Solution 2 – Exclude Pages:

13. Go to Performance → Page Cache → Advanced
14. Find Never cache the following pages
15. Add landing page patterns:

`
landing-page/*
lp/*
shahi-landing/*
`

Solution 3 – Exclude Query Strings:

16. Page Cache → Advanced → Accepted query strings
17. Add experiment parameters:

`
variant
experiment
shahilandin_variant
`

Solution 4 – Disable for Logged-in Users:

18. Page Cache → General → Uncheck Cache requests for logged-in users

WP Rocket


Problem: Aggressive optimization breaks landing page features.

Solution 1 – Clear Cache:

19. Click WP Rocket in admin bar
20. Click Clear Cache

Solution 2 – Exclude Landing Pages:

21. Go to Settings → Advanced Rules
22. Never Cache URL(s):

`
/landing-page/(.*)
/lp/(.*)
/shahi-landing/(.*)
`

Solution 3 – Disable JavaScript Optimization:

23. File Optimization tab
24. Excluded JavaScript Files:

`
/wp-content/plugins/ShahiLandin/assets/js/(.*)
`

Solution 4 – Disable Lazy Loading:

25. Media tab → Images
26. Excluded Images or Iframes:

`
.landing-hero
[data-shahilandin-image]
`

LiteSpeed Cache


Problem: Landing pages served from cache, bypass cache not working.

Solution 1 – Clear Cache:

27. LiteSpeed Cache menu → Purge All
28. Or click Purge All in admin bar

Solution 2 – Exclude Landing Pages:

29. Go to LiteSpeed Cache → Cache → Excludes
30. Do Not Cache URIs:

`
/landing-page/
/lp/
shahi-landing
`

Solution 3 – Exclude Query Strings:

31. Cache → Excludes → Do Not Cache Query Strings:

`
variant
shahilandin_variant
experiment
`

Solution 4 – Set Cache TTL:

32. Cache → Cache → Cache TTL for Pages
33. Set lower value (e.g., 600 seconds instead of 604800)

Object Cache Issues


Redis/Memcached


Problem: Landing page data cached in object cache causes stale content.

Solution:

34. ShahiLandin uses WordPress transients
35. Flush object cache:

`bash

For Redis Object Cache plugin


wp cache flush

Or via WP-CLI


wp transient delete-all
`

36. Exclude ShahiLandin transients from object cache:

`php
// Add to wp-config.php
$globalgroups = [‘shahilandincache’];
wpcacheaddglobalgroups($global_groups);
`

CDN Conflicts


Cloudflare


Problem: Landing page updates don’t appear for visitors, cached at edge.

Solution 1 – Purge Cache:

37. Log into Cloudflare dashboard
38. Caching → Purge Everything
39. Or purge specific URL

Solution 2 – Create Page Rule:

40. Page Rules → Create Page Rule
41. URL: yoursite.com/landing-page*
42. Setting: Cache Level → Bypass
43. Save and deploy

Solution 3 – Reduce Cache TTL:

44. Caching → Configuration
45. Browser Cache TTL: Set to 1 hour
46. Edge Cache TTL: Use Respect Existing Headers

Solution 4 – Disable Auto Minify for Landing Pages:

47. Can break custom CSS/JS
48. Speed → Optimization
49. Auto Minify → Uncheck JavaScript and CSS
50. Or use page rule to disable per URL

Other CDNs (BunnyCDN, KeyCDN, AWS CloudFront)


General Solutions:

51. Set shorter TTL for landing pages
52. Use cache invalidation API when updating
53. Add cache busting parameters: ?v=timestamp
54. Configure proper cache headers in WordPress

Plugin Conflicts


Page Builder Conflicts


Elementor


Problem: Cannot edit landing page with Elementor, or Elementor overrides ShahiLandin.

Solution:

55. ShahiLandin and Elementor can coexist
56. Don’t edit same page with both:

– Use Elementor OR ShahiLandin per page
– Not both simultaneously

57. To disable Elementor for landing pages:

`php
// Add to theme’s functions.php
addfilter(‘elementor/frontend/buildercontentdisplay’, function($display, $postid) {
if (getposttype($postid) === ‘shahilanding’) {
return false; // Disable Elementor for landing pages
}
return $display;
}, 10, 2);
`

Divi Builder


Problem: Divi theme interferes with landing page display.

Solution:

58. Use Canvas Mode for landing pages:

– Edit landing page
– Template → Canvas (Full Isolated)

59. Disable Divi builder for landing pages:

`php
addfilter(‘etbuildershouldloadframework’, function($shouldload) {
if (issingular(‘shahilanding’)) {
return false;
}
return $should_load;
});
`

Beaver Builder


Problem: Beaver Builder and ShahiLandin conflict on same page.

Solution:
Similar to above – use one or the other per page:
`php
addfilter(‘flbuilderrendermodule’, function($render, $module) {
if (getposttype() === ‘shahi_landing’) {
return false;
}
return $render;
}, 10, 2);
`

Form Plugin Conflicts


Contact Form 7


Problem: Contact Form 7 shortcode not working in landing page.

Solution 1 – Ensure Scripts Load:
ShahiLandin’s Canvas mode may not load CF7 scripts.

60. Add to landing page HTML:

`html

`

Solution 2 – Manually Load Scripts:
`php
// Add to functions.php
addaction(‘wpenqueue_scripts’, function() {
if (issingular(‘shahilanding’)) {
if (functionexists(‘wpcf7enqueue_scripts’)) {
wpcf7enqueuescripts();
}
if (functionexists(‘wpcf7enqueue_styles’)) {
wpcf7enqueuestyles();
}
}
});
`

Gravity Forms


Problem: Gravity Forms not displaying or submitting correctly.

Solution:

61. Gravity Forms usually works without issues
62. If form not displaying:

`php
// Force load Gravity Forms on landing pages
addfilter(‘gformforcehooks’, function($forcehooks) {
if (issingular(‘shahilanding’)) {
return true;
}
return $force_hooks;
});
`

WPForms


Problem: WPForms styles conflict with landing page design.

Solution:

63. Disable WPForms styling:

`php
addfilter(‘wpformsmodernformfields’, ‘_returnfalse’);
`

64. Or add custom CSS to override:

`css
.wpforms-container {
/ Your custom styles /
}
`

SEO Plugin Conflicts


Yoast SEO


Problem: Yoast meta boxes clutter landing page editor.

Solution:

65. Hide Yoast for landing pages:

`php
addaction(‘addmeta_boxes’, function() {
removemetabox(‘wpseometa’, ‘shahilanding’, ‘normal’);
}, 100);
`

66. Or keep but collapse by default:

– Screen Options (top right) → Uncheck Yoast boxes

Rank Math


Problem: Rank Math redirects or canonical URLs interfere.

Solution:

67. Exclude landing pages from Rank Math:

`php
addfilter(‘rankmath/frontend/disable’, function($disable) {
if (issingular(‘shahilanding’)) {
return true;
}
return $disable;
});
`

Security Plugin Conflicts


Wordfence


Problem: Wordfence firewall blocks landing page tracking or AJAX requests.

Solution 1 – Whitelist Landing Pages:

68. Go to Wordfence → Firewall → Manage Rate Limiting
69. Add landing page URLs to whitelist

Solution 2 – Allow Analytics Endpoints:

70. Firewall → All Options → Whitelisted URLs:

`
/wp-json/shahilandin/v1/view
/wp-json/shahilandin/v1/conversion
`

Solution 3 – Disable for Logged-in Admins:

71. Won’t affect most visitors
72. Wordfence → Login Security → Uncheck Enforce on administrators

Sucuri Security


Problem: Sucuri blocks HTML import or asset mirroring.

Solution:

73. Sucuri Firewall → Settings → Whitelist IP
74. Add your server’s IP address
75. Or temporarily disable Sucuri for import:

– Deactivate plugin
– Import landing page
– Reactivate Sucuri

iThemes Security


Problem: iThemes blocks REST API requests or file uploads.

Solution:

76. Security → Settings → REST API
77. Ensure REST API is not completely disabled
78. Or whitelist ShahiLandin endpoints:

`php
add_filter(‘itsec-filter-whitelisted-ips’, function($whitelisted) {
if (isset($SERVER[‘REQUESTURI’]) &&
strpos($SERVER[‘REQUESTURI’], ‘/shahilandin/’) !== false) {
$whitelisted[] = $SERVER[‘REMOTEADDR’];
}
return $whitelisted;
});
`

Performance Optimization Plugin Conflicts


Autoptimize


Problem: Autoptimize breaks landing page JavaScript or CSS.

Solution 1 – Exclude ShahiLandin Assets:

79. Settings → Autoptimize → JS, CSS & HTML
80. Exclude scripts from Autoptimize:

`
shahilandin-analytics, shahilandin-admin
`

81. Exclude CSS from Autoptimize:

`
shahilandin
`

Solution 2 – Disable Inline CSS Deferral:

82. CSS Options → Inline all CSS (uncheck)
83. This prevents critical landing page CSS from being deferred

Asset CleanUp


Problem: Asset CleanUp removes necessary scripts from landing pages.

Solution:

84. Go to Asset CleanUp → Settings
85. Post Types → Find Landing Pages (shahi_landing)
86. Load Exception → Check all ShahiLandin scripts/styles
87. Or disable Asset CleanUp for landing pages entirely

WP-Optimize


Problem: WP-Optimize minification breaks landing pages.

Solution:

88. WP-Optimize → Minify → Exclude
89. Exclude from minification:

`
shahilandin
analytics
`

Multilingual Plugin Conflicts


WPML


Problem: Landing pages not translating or wrong language displayed.

Solution:

90. Register landing page post type with WPML:

`php
addfilter(‘wpmloverrideistranslatedposttype’, function($override, $type) {
if ($type === ‘shahi_landing’) {
return true;
}
return $override;
}, 10, 2);
`

91. Configure translation:

– WPML → Settings → Post Types
– Enable Landing Pages
– Set to Translatable

Polylang


Problem: Language switcher doesn’t work on landing pages.

Solution:
`php
// Register post type with Polylang
addfilter(‘pllgetposttypes’, function($post_types) {
$posttypes[‘shahilanding’] = ‘shahi_landing’;
return $post_types;
});
`

Theme Conflicts


Common Theme Issues


Problem 1: Theme Styles Override Landing Page


Solution:
Use Canvas Mode to bypass theme entirely:

92. Edit landing page
93. Template → Canvas (Full Isolated)
94. Update page

Problem 2: Theme JavaScript Errors


Symptom: Theme JS conflicts with landing page scripts, console shows errors.

Solution:

95. Use Canvas Mode (loads minimal WordPress, skips theme)
96. Or disable theme scripts for landing pages:

`php
addaction(‘wpenqueue_scripts’, function() {
if (issingular(‘shahilanding’)) {
// Dequeue theme scripts
wpdequeuescript(‘theme-main-script’);
wpdequeuescript(‘theme-custom’);
}
}, 100);
`

Problem 3: Theme Adds Unwanted Elements


Symptom: Theme adds share buttons, author bio, breadcrumbs to landing page.

Solution:

97. Canvas Mode – cleanest solution
98. Or hide via CSS:

`css
.shahi-landing .share-buttons,
.shahi-landing .author-bio,
.shahi-landing .breadcrumbs {
display: none !important;
}
`

Premium Theme Conflicts


Avada Theme


Solution:
`php
add_action(‘wp’, function() {
if (issingular(‘shahilanding’)) {
removeaction(‘wphead’, ‘avadasetpost_header’, 10);
removeaction(‘wpfooter’, ‘avadarenderfooter’, 10);
}
});
`

Divi Theme


Already covered above – use Canvas Mode or disable Divi builder for landing pages.

Astra Theme


Solution:
`php
addfilter(‘astrapage_layout’, function($layout) {
if (issingular(‘shahilanding’)) {
return ‘page-builder’; // Full width, no sidebar
}
return $layout;
});
`

Identifying Plugin Conflicts


Systematic Conflict Testing


Step 1 – Deactivate All Plugins (Except ShahiLandin):

99. Go to Plugins page
100. Select all plugins EXCEPT ShahiLandin
101. Bulk Actions → Deactivate
102. Test landing page – does issue persist?

Step 2 – If Issue Resolved:

103. Reactivate plugins one by one
104. Test after each activation
105. When issue returns, you’ve found the conflicting plugin

Step 3 – If Issue Persists:

106. Reactivate all plugins
107. Switch to default theme (Twenty Twenty-Four)
108. Test again
109. If resolved, conflict is with your theme

Using Health Check Plugin


Better Method – Test without affecting site visitors:

110. Install Health Check & Troubleshooting plugin
111. Go to Tools → Site Health → Troubleshooting
112. Click Enable Troubleshooting Mode
113. Only YOU see plugins disabled, visitors see normal site
114. Selectively reactivate plugins to find conflict
115. Click Disable Troubleshooting Mode when done

Browser and JavaScript Conflicts


Problem 1: Ad Blockers


Symptom: Analytics not tracking, scripts blocked.

Solution:

116. ShahiLandin uses first-party tracking (usually not blocked)
117. If blocked, whitelist your site in ad blocker
118. For visitors: Can’t force them to disable, but most won’t have issues

Problem 2: Privacy Extensions


Symptom: Ghostery, Privacy Badger, uBlock Origin blocking features.

Solution:

119. Test in incognito/private mode without extensions
120. For your own testing, whitelist your site
121. For visitors: Accept that heavily protected users may have limited tracking

Problem 3: Content Security Policy (CSP)


Symptom: Browser blocks inline scripts, CSP violation in console.

Solution:

122. If your site enforces CSP, add ShahiLandin to whitelist:

`html

`

123. Or configure CSP header in server config to allow inline scripts

Debug Mode for Conflicts


Enable WordPress Debug


`php
// Add to wp-config.php
define(‘WP_DEBUG’, true);
define(‘WPDEBUGLOG’, true);
define(‘WPDEBUGDISPLAY’, false);
define(‘SCRIPT_DEBUG’, true); // Loads unminified scripts
`

Enable ShahiLandin Debug


`php
// Add to wp-config.php
define(‘SHAHILANDIN_DEBUG’, true);
`

Check Debug Log


124. View log file at /wp-content/debug.log
125. Look for:

– PHP errors
– ShahiLandin warnings
– Plugin conflict notices

126. Filter for relevant errors:

`bash

View ShahiLandin errors only


grep -i “shahilandin” wp-content/debug.log

View recent errors


tail -f wp-content/debug.log
`

Best Practices to Avoid Conflicts


127. ✅ Keep plugins updated – Many conflicts fixed in updates
128. ✅ Use Canvas Mode for full control over landing pages
129. ✅ Exclude landing pages from caching where dynamic features needed
130. ✅ Test with default theme first to isolate theme issues
131. ✅ Use Health Check plugin for safe conflict testing
132. ✅ Disable conflicting plugins only on landing pages (if possible)
133. ✅ Document conflicts you discover for future reference
134. ✅ Contact plugin authors if persistent conflicts occur
135. ✅ Regular backups before testing conflict resolutions
136. ✅ Staging site for testing without affecting production

Getting Help


If conflicts persist after troubleshooting:

137. Provide detailed information:

– Conflicting plugin name and version
– Theme name and version
– Steps to reproduce conflict
– Error messages (exact text)

138. Export debug log:

– Copy relevant portions of debug.log
– Include ShahiLandin-related errors

139. Site Health Export:

– Go to Tools → Site Health → Info
– Click Copy site info to clipboard
– Include in support request

140. Screenshots:

– Active plugins list
– Error messages
– Console errors (F12)

—

Related Articles:

• Installation and Activation Issues
• Performance Issues
• Display and Rendering Issues