Overview
If your website is showing a “Not Secure” warning or your events page isn’t loading styles or scripts correctly after switching to HTTPS, you’re likely facing a mixed content issue. This happens when your site loads some resources (like images, scripts, or stylesheets) over HTTP on a page served over HTTPS..
What Is Mixed Content?
When a secure (HTTPS) page loads a resource (such as an image, iframe, script, or stylesheet) using an insecure (HTTP) URL, browsers may block those resources or show warnings, breaking functionality or layout.
Common Symptoms
- Event pages are missing styles or scripts
- Console errors like:
Mixed Content: The page was loaded over HTTPS, but requested an insecure resource http://example.com/...- Browser warnings: “Not Secure” in the address bar
- Embedded maps or videos fail to load
How to Fix Mixed Content Issues
- Update Site URLs
Ensure your WordPress and Site URLs usehttps://.
Go to:
WordPress Dashboard → Settings → General
Update both fields to begin withhttps://. - Use a Mixed Content Fixer Plugin
Install a plugin like Really Simple SSL. It detects mixed content and helps you transition to HTTPS safely. - Replace Old HTTP Links in the Database
Use a plugin like Better Search Replace to scan and update oldhttp://URLs in your posts, pages, and settings:
🔍Search for:http://yourdomain.com
👉Replace with:https://yourdomain.com
Run a dry run first to preview changes. - Update Theme or Plugin Assetsot drag-and-drop Elementor building.
If your theme or plugins (including custom code) load scripts or styles using hardcoded HTTP URLs, update those to usehttps://or protocol-relative URLs (//). - Check Embedded Content
Ensure embedded resources (like maps, iframes, or videos) use HTTPS. For example, if you’re embedding a Google Map, use the HTTPS version of the embed code.
Bonus Tip: Use Browser Dev Tools
Open Developer Tools in Chrome (F12 or right-click → Inspect), go to the Console tab, and refresh the page. Look for errors mentioning Mixed Content.