EDZNET WP HTTPS
EDZNET WP HTTPS automatically resolves mixed content warnings on WordPress sites served over HTTPS. Once activated, it converts http:// URLs to https:// across: WordPress-generated URLs (home, site, includes, content, plugins, theme assets) Enqueued scripts and styles Attachment URLs and image srcse
EDZNET WP HTTPS automatically resolves mixed content warnings on WordPress sites served over HTTPS. Once activated, it converts http:// URLs to https:// across:
- WordPress-generated URLs (home, site, includes, content, plugins, theme assets)
- Enqueued scripts and styles
- Attachment URLs and image srcsets
- Post content and widget text
- Post thumbnails and avatars
- All frontend HTML output (via output buffering)
No configuration required — simply install, activate, and your HTTPS resources will load securely.
- 01Upload the edznet-wp-https folder to /wp-content/plugins/ .
- 02Activate the plugin through the Plugins screen in WordPress.
- 03That’s it. Your site’s resources will now be served over HTTPS.
Frequently asked questions.
Will this affect external HTTP links?
All http:// URLs are converted to https:// . External sites linked from your content will be accessed via HTTPS where supported.
Why are some http:// addresses left alone?
XML namespace identifiers such as http://www.w3.org/2000/svg are names, not links, and must stay exactly as written. Changing them stops SVG images and icons from rendering (for example Divi section dividers). The same applies to XML sitemaps and RSS/podcast feeds, whose namespaces search engines and feed readers check exactly. These hosts are skipped: www.w3.org, ns.adobe.com, ogp.me, purl.org, xmlns.com, schemas.xmlsoap.org, schemas.microsoft.com, creativecommons.org/ns, web.resource.org, www.sitemaps.org, www.google.com/schemas, wellformedweb.org, search.yahoo.com/mrss, www.itunes.com/dtds, www.georss.org and archipelago.phrasewise.com. Developers can change the list with the edznet_https_skip_hosts filter.
