Versioning Not Working for Fonts or Media

Problem: CSS, JS, and Images get versioned correctly, but Fonts and Media files don't have the ?1cdnver= parameter.

Step 1: Verify CDN is Enabled

Go to 1 CDN Manager → Settings → CDN Settings Tab

Check these toggles are ON:

  • Enable Media CDN toggle (for videos/audio)
  • Enable Fonts CDN toggle (for fonts/documents)

Check URLs are filled in:

  • Media CDN Base URL: https://media-cdn.example.com
  • Fonts CDN Base URL: https://fonts-cdn.example.com

Step 2: Verify Versioning is Enabled

Go to 1 CDN Manager → Settings → Advanced Tab

Check these toggles are ON:

  • Media Versioning toggle
  • Fonts Versioning toggle

Check version strings are filled:

  • Media Versioning: 1.2 (or your version)
  • Fonts Versioning: 1.5 (or your version)

Step 3: Test File Detection

View your page source (Right-click → View Page Source) and search for:

For Fonts: search for ".woff2" For Media: search for ".mp4" or ".mp3"

If you DON'T see your CDN URL, the file isn't being detected. Check:

Step 4: Clear All Caches

  1. WordPress Cache: If using WP Rocket, W3 Total Cache, etc., clear cache
  2. CDN Cache: Purge Cloudflare or your CDN cache
  3. Browser Cache: Hard refresh (Ctrl+Shift+R or Cmd+Shift+R)
  4. Plugin Cache: Go to Tools → Clear All Cache

Step 5: Check URL Structure

Working Example:

Before CDN: https://example.com/wp-content/uploads/video.mp4 After CDN: https://media-cdn.example.com/wp-content/uploads/video.mp4 With Version: https://media-cdn.example.com/wp-content/uploads/video.mp4?1cdnver=1.2

Step 6: Check for Conflicts

Disable other caching plugins temporarily:

Test if versioning works with those disabled. Re-enable one by one to find the conflict.

CDN URLs Not Being Applied

Problem: URLs still point to original domain instead of CDN

Solution 1: Check CDN Toggle

Each CDN type has an "Enable" toggle. Make sure it's ON for the asset type you want to use.

Solution 2: Verify URL Format

Correct format:

✅ https://cdn.example.com ✅ https://d1a2b3c4d5.cloudfront.net ✅ https://img-cdn.example.com

Incorrect format:

❌ https://cdn.example.com/ (trailing slash) ❌ http://cdn.example.com (http instead of https if site is https) ❌ cdn.example.com (missing protocol)

Solution 3: Check Source Host

Plugin only rewrites URLs from your site domain. If URL is from external source, it won't be rewritten.

✅ Will rewrite: https://example.com/image.jpg ❌ Won't rewrite: https://external-site.com/image.jpg

Broken Images or 404 Errors

Cause 1: CDN Not Configured Correctly

Solution: Verify your CDN points to your website's root directory

Cause 2: Path Structure Different

CDN must preserve full path structure

Original: https://example.com/wp-content/uploads/2024/10/image.jpg CDN URL: https://cdn.example.com/wp-content/uploads/2024/10/image.jpg ← Must keep full path unchanged

Cause 3: CORS Issues (Fonts)

Font files require CORS headers. Check browser console for errors like:

Access to font at 'https://cdn.example.com/font.woff2' from origin 'https://example.com' has been blocked by CORS policy

Solution: Add CORS headers to your CDN:

Access-Control-Allow-Origin: * Access-Control-Allow-Methods: GET, HEAD

CSS/JS Not Loading

Cause: CORS Headers Missing

CSS and JS from CDN need proper headers if domain is different from main site.

Required headers:

Access-Control-Allow-Origin: * Content-Type: text/css (for CSS) Content-Type: application/javascript (for JS)

Test CORS Headers

Open browser console (F12) and run:

fetch('https://cdn.example.com/style.css') .then(r => r.headers.get('Access-Control-Allow-Origin')) .then(console.log)

Should output: * or your domain

Performance Issues

Cause 1: Too Many CDNs

Problem: 5 different CDN domains = 5 DNS lookups = slower

Solution: Use 1-2 CDN domains for all assets instead of 5

Cause 2: Cache Not Working

Problem: CDN fetching from origin every time

Solution: Check CDN caching rules

Cause 3: Aggressive Rewriting Enabled

Problem: Content Rewriting → Aggressive Mode slows page generation

Solution: Disable Aggressive Mode unless absolutely needed

Tools Page Shows Error

Critical Error Message

If Tools page shows "There has been a critical error on this website":

Solution 1: Check PHP Version

Plugin requires PHP 7.4+. Check: Tools → Site Health

Solution 2: Check for Conflicts

Temporarily disable other plugins to find conflict

Solution 3: Check Error Logs

wp-content/debug.log (if WP_DEBUG enabled) Server error logs (Apache/Nginx)

Cloudflare Integration Not Working

Test Connection Fails

Possible causes:

  1. Wrong Zone ID: Get from Cloudflare dashboard → Overview → Zone ID (right sidebar)
  2. Wrong API Token: Token must have "Cache Purge" permission
  3. API Token Restrictions: Check token isn't restricted to specific IPs

Creating Correct API Token

  1. Go to Cloudflare Dashboard
  2. My Profile → API Tokens → Create Token
  3. Use "Edit Zone" template
  4. Permissions: Zone.Cache Purge
  5. Zone Resources: Include → Specific zone → Your domain
  6. Create Token and copy it

Debugging Tips

1. View Page Source

Right-click on page → "View Page Source" → Search for your CDN URL

This shows exactly what URLs are in the HTML

2. Browser Developer Tools

Press F12 → Network tab → Reload page

Click on any asset to see:

3. Test Individual URLs

Copy a CDN URL from page source and paste in new browser tab

Should load the file. If 404, CDN configuration issue

4. Use Tools Page

Go to 1 CDN Manager → Tools

5. Enable WordPress Debug Mode

Edit wp-config.php and add:

define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); define('WP_DEBUG_DISPLAY', false);

Check wp-content/debug.log for error messages

Getting Support

Before Contacting Support

Gather this information:

Support Channels