Fixing CORS Errors

CORS (Cross-Origin Resource Sharing) errors occur when resources (fonts, scripts, images) load from a domain or subdomain different from your primary domain. These errors often happen:

• After migrating a website.
• If the URLs (e.g., www vs. non-www) do not match the primary domain.
• If resources load over HTTP instead of HTTPS.

This guide explains how to resolve CORS errors using Staq tools.

Common Causes of CORS Errors

1. Primary Domain Mismatch:
   • Example: Resources load from https://example.com instead of https://www.example.com.
2. Outdated Resource Links:
   • Example: HTTP links instead of HTTPS.
3. Cached Files:
   • Theme, plugin, or server-side caches retain incorrect URLs.

Step-by-Step Solutions

1. Verify and Update Resource URLs Using Search & Replace

To perform a Search & Replace in the database, you have two options:

Option 1 – Via Staq Panel

1. Go to the site’s Staq Panel.
2. Under Databases, click Search & Replace.

3. Use the Search & Replace tool to replace outdated URLs:
   • Example: http://example.com → https://www.example.com.

Option 2 – Via WordPress Backend

1. Log in to the website backend.
2. Hover over Staq Hosting in the top toolbar → Select Settings.
3. Go to Advanced → Search & Replace.

4. Replace the incorrect URLs with the correct ones.

2. Clear Staq Cache and Redis Object Cache

Clear Staq Cache:

• In WordPress backend → Hover over Staq Hosting → Click Clear Site Cache.
• OR in the Staq Panel → Under Files, click Cache → Click Clear Cache.

Flush Redis Object Cache:

1. Go to the site’s Staq Panel → Under Database, click Redis Object Cache → Click Flush.
2. OR in WordPress backend → Go to Staq Hosting → Object Cache → Click Flush Cache.

3. Reset Theme and Plugin Caches

Certain themes store cached URLs. Reset caches as follows:

4. Verify CORS in Browser Developer Tools

1. Open Developer Tools in your browser (right-click → Inspect → Console).
2. Check for CORS errors (e.g., font or script file blocked).

If the issue persists, ensure all URLs are consistent and contact Staq Support for server-side fixes.