[DeMiNe0Participant]

I found the CSS to change this. title_breadcrumbs_bar and headline_breadcrumbs_bar for anyone else wondering.

Add New Note to this Reply

[DeMiNe0Participant]

Saw answer in the other thread:

– go to wp-content\themes\vozx\functions.php file
– find this line of code: wp_enqueue_style(‘ABdev_font_css’,’http://fonts.googleapis.com/css?family=Lato:300,400,400italic,700,900′);
– change it to wp_enqueue_style(‘ABdev_font_css’,’https://fonts.googleapis.com/css?family=Lato:300,400,400italic,700,900′);

This will work on https version.
Please, be sure that you have cleared your cache after the change.

Best Regards.

Thanks guys! A+++ support as always!

Add New Note to this Reply

[DeMiNe0Participant]

Any progress on this?

Add New Note to this Reply

[DeMiNe0Participant]

It looks like http://fonts.googleapis.com/css?family=Lato%3A300%2C400%2C400italic%2C700%2C900&ver=4.5.2 is being called in the http version but not in the https version.

Add New Note to this Reply

[DeMiNe0Participant]

Looking a little more closely, it’s actually more than just the tab boxes. The <h>header font is off too.

Add New Note to this Reply

[DeMiNe0Participant]

I copied my entire dev site over to the main site to see why the CSS wasn’t loading correctly for the tab box. After cloning the site, It still had the same exact issue. The only difference being that the site was now on https. So I went into my configuration for my site and removed the strict security headers and enabled plain port 80 http.

Now take a look at the tab box on the front page on http, compared to HTTPS. It looks to me like the CSS isn’t being applied when the site is loaded in https. Perhaps the browser is blocking the css from loading because it’s being loaded http?

http://www.pressz2poop.com vs https://www.pressz2poop.com.

Add New Note to this Reply

[DeMiNe0Participant]

Sure. Info is below.

Add New Note to this Reply

[DeMiNe0Participant]

Also, I’m fairly sure adding:
set_time_limit(600);

to my wp-config.php fixed the issue as well. set_time_limit() is hard coded to 60 seconds, so overiding that in the config seemed like a good bet.

Add New Note to this Reply

[DeMiNe0Participant]

fastcgi_read_timeout 10m;
Is the line I used. Just put that in the location block that calls php-fpm. Don’t keep it at 10m in production because that can cause php to get bogged down with long running processes.

Add New Note to this Reply

[DeMiNe0Participant]

I fixed this. For future reference I also had to set my php-fpm read timeout to greater than 60 seconds.

Add New Note to this Reply

[Author]

Posts