URLs of css files not https -> mixed content problem

HP · 2017-02-20 03:03:14

Hi,

I just came across a problem when I was testing my site with Firefox... Chrome was just showing the mixed content...

When I click on the "external link" for my blog -> the page opens the Wordpress blog. The design looks so far ok...
The search button and the special arrows in the menue do not show up correctly...

When I checked the source code of the page I saw that two ccs files are loaded as http: // instead of https:// therefore the mixed content problems occurs.

Any idea where to fix this?

Thanks and regards
HP

rod barbee · 2017-02-20 03:36:01

did you update the page template used to create your WordPress theme? Did you re export that theme?

rod barbee · 2017-02-20 03:41:49

also try clearing template cache

HP · 2017-02-20 03:42:45

Hi Rod,

yes - several times... all other URLs are correctly set to https:// only the two stay on http://

I also renamed it, deleted it in the themes folder and repubished it... no way to get it fixed... cache deleted...

This line of loading the style-css is correct... Just the awsome and the custom fail...

Regards
HP

rod barbee · 2017-02-20 03:59:30

my guess is this could be a .htaccess file issue, something I know very little about. Ben will need to comment about that.

is this happening only with the WordPress theme?

If so you could try enqueuing those two css files. You'll want to use a child theme for that.

HP · 2017-02-20 05:46:02

Here is my .htaccess (from Pages 1.1.1)

# ------------------------------------------------------------------------------
# | Web fonts access |
# ------------------------------------------------------------------------------

# Allow access from all domains for web fonts

<IfModule mod_headers.c>
<FilesMatch "\.(eot|font.css|otf|ttc|ttf|woff)$">
Header set Access-Control-Allow-Origin "*"
</FilesMatch>
</IfModule>

<IfModule mod_rewrite.c>
RewriteEngine On

###################################
# Redirect all traffic to HTTPS
###################################

RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

############################################################################
# Edit this section for servers using FastCGI

# For FastCGI (or seeing the error message 'No input file specified.':
# add # to the start of the next line
RewriteBase /

RewriteCond $0#%{REQUEST_URI} ([^#]*)#(.*)\1$

# For FastCGI (or seeing the error message 'No input file specified.':
# add # to the start of the next line and remove # from the line after)
RewriteRule ^.*$ - [E=BASE:%2]
#RewriteRule ^(.*)$ - [E=BASE:]

############################################################################

RewriteRule ^(.*)$ - [E=QS:mod_rewrite=on]

RewriteRule ^([^\/.]*)-single.php$ %{ENV:BASE}single.php?%{ENV:QS}&id=$1 [QSA,L]

RewriteRule ^([^\/.]*).css$ %{ENV:BASE}index.php?%{ENV:QS}&extension=css&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).js$ %{ENV:BASE}index.php?%{ENV:QS}&extension=js&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).gif$ %{ENV:BASE}index.php?%{ENV:QS}&extension=gif&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).png$ %{ENV:BASE}index.php?%{ENV:QS}&extension=png&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).jpg$ %{ENV:BASE}index.php?%{ENV:QS}&extension=jpg&name=$1 [QSA,L]

#RewriteCond %{QUERY_STRING} !mod_rewrite=on
#RewriteRule ^index.php$ %{ENV:BASE}index.php?%{ENV:QS} [QSA,L]

RewriteCond %{QUERY_STRING} !mod_rewrite=on
RewriteRule ^mobile.php$ %{ENV:BASE}mobile.php?%{ENV:QS} [QSA,L]

RewriteCond %{QUERY_STRING} !mod_rewrite=on
RewriteRule ^(.*)download.php %{ENV:BASE}download.php?%{ENV:QS} [QSA,L]

RewriteRule ^$ %{ENV:BASE}index.php?%{ENV:QS} [QSA,L]

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d

RewriteRule ^(.*)$ %{ENV:BASE}index.php?%{ENV:QS}&page=$1 [QSA,L]

</IfModule>

michilge · 2017-02-20 05:58:03

1. Log into backlight admin via a https-URL.
2. open the templateon which your wp-theme-template is based on in the designer, apply some change ans save.
(3. revert that change and save again)
4. export your wp-theme
5. clear template cache and browser cache

additionally

6. get the wp plugin "Better Search Replace" and use it to search the wp_posts and wp_options tables of your wp installation for the string "http:" (the prefix wp_ may vary)
7. replace them by "https:"
8. live long and prosper

Last edited by michilge (2017-02-20 05:58:12)

HP · 2017-02-21 03:17:57

Hi michilge,

I followed your steps 1-5 and it looks like the https problem has gone and the page look ok now.

I will continue with step #8 then.

Thanks a lot for your help!

Regards
HP

michilge · 2017-02-21 04:51:53

6+7 might be of interest in case you have cross referencing links from one post to another. Also if you have taxonomy and archive links to existing posts.
You might also search for old "http:" occurrences with PHPmyAdmin if it is installed on your hosting platform.

HP · 2017-02-21 05:26:01

Yes I checked all the WP tables for http: -> all fine nothing to change...

I also went through all the db files of Backlight - at the end I was expecting some hard coded http:

Regards
HP

Community @ The Turning Gate

#1 2017-02-20 03:03:14

URLs of css files not https -> mixed content problem

#2 2017-02-20 03:36:01

Re: URLs of css files not https -> mixed content problem

#3 2017-02-20 03:41:49

Re: URLs of css files not https -> mixed content problem

#4 2017-02-20 03:42:45

Re: URLs of css files not https -> mixed content problem

#5 2017-02-20 03:59:30

Re: URLs of css files not https -> mixed content problem

#6 2017-02-20 05:46:02

Re: URLs of css files not https -> mixed content problem

#7 2017-02-20 05:58:03

Re: URLs of css files not https -> mixed content problem

#8 2017-02-21 03:17:57

Re: URLs of css files not https -> mixed content problem

#9 2017-02-21 04:51:53

Re: URLs of css files not https -> mixed content problem

#10 2017-02-21 05:26:01

Re: URLs of css files not https -> mixed content problem

Board footer