Have you checked the database? Especially “wp-options” and there the key “siteurl”. Best would probably be to do a complete dump, search for https://www.yourdomain.com and replace it with http://www.yourdomain.com
I’ve experienced this problem in the past. In my opinion, the easiest way is by making use of the plugin: https://wordpress.org/plugins/search-and-replace/ Always perform a backup of your database before performing a search and replace. Make sure you do a “Dry Run” first. If you do not already have good backup procedures in place, check out … Read more
In case this helps anyone in the future: The problem was not a WordPress issue, it was a server configuration issue. Useful explanation on checking which stream wrappers are enabled on your server (used this to make sure https was enabled on my server) Enable Stream Wrappers Someone with the same issue found that their … Read more
You need to install these two plugins. CloudFlare Flexible SSL – https://wordpress.org/plugins/cloudflare-flexible-ssl/ Really Simple SSL- https://wordpress.org/plugins/really-simple-ssl/ After both the plugins are installed and activated, you will get a message at the top of your dashboard to activate SSL. Click on activate and you are done. You will be logged out. Because your domain has changed … Read more
You can install HTTP/HTTPS Remover plugin to fix the issue. Generally, it works with all the plugins and themes. You can download and install the plugin from https://wordpress.org/plugins/http-https-remover/
If assets are enqueued properly they are using the exact URL they are enqueued with. If the protocol in URL is hardcoded that causes mismatch issues you are seeing. For proper protocol support enqueued URLs need to be either: created with protocol-aware API function from WP API (most if not all functions that produce URLs … Read more
You’ll need to update all of the URLs in your database to the HTTPS protocol: Go and download Interconnect IT’s Database Search & Replace Script here Unzip the file and drop the folder where your WordPress is installed (the root) and rename the folder to replace (screenshot) Navigate to the new folder you created in … Read more
I just saw this problem myself on my site. The issue for me was that the site was available as both https://example.com/ and http://example.com. If the first request to a page was for the http version, the links to assets would be to http: http://example.com/wp-content/themes/customizr/assets/front/img/thumb-standard-empty.png http://example.com/wp-content/uploads/… etc. These http asset links would get put into … Read more
Pointing SSL Enabled URL at Single WordPress Page
There is no need to hardcode anything and/or alter database entries. I’d highly recommend you’d check out the following plugin: WordPress HTTPS – it’s quite versatile and will handle everything for you.