I’m using the Vantage theme and have the Search Menu integrated directly in the navigation menu per the theme settings.
I’m using the flexible SSL available through Cloudflare to provide HTTPS pages and I’ve made the URLs under General WordPress Settings to reflect https://www.mustangexclusives.net (the site is work under construction) so disregard the content.
Everything seems to be working correctly using https (which is preferred anyways); however, I noticed if you elect to visit the site using http rather than https the search icon in the navigation menu displays as Chinese lettering instead of a magnifying glass.
Ideally, I’m working on forcing https but having some redirect issues and while I prefer individuals use https I want to have an understanding of why the search icon doesn’t display correctly when using standard http now that I’ve enabled https.
An update: I’m now forcing HTTPS via .htaccess
The original .htaccess is as shown:
# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress
I altered the code as shown:
# BEGIN WordPress
RewriteEngine On
RewriteCond %{HTTPS} on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress
While I still don’t necessarily understand why the icon wasn’t displaying correctly without https, I am now at least forcing visitors to use https which is preferred for security anyways.
Unfortunately, while it appears this is working for most inbound links, interestingly I don’t think inbound links from Google that are still showing up as without http are forwarded to https. Perhaps over time they will hopefully be replaced by the https versions.
Never mind the .htaccess above it resulted in redirect errors on Chrome.
Downloaded a plugin called HTTPS Switcher that apparently loads resources and content in either http or https and that appears to have fixed the issue.