Site logo

Archived topic

Navbar display broken

9 replies · Started by Scott on June 2, 2021

Viewing posts 1–10 of 10

One of our sites, PurpleRoofs.com, has had this issue now 3 or 4 times since January. The navbar loses all of its formatting on a pc browser and presents as a long text list. The first time it happened, I was able to pull some css files from a backup and replace them, and that seemed to fix it. My developer rolled back the theme once, and that seemed to work. But now nothing I try will fix it, including loading in the whole theme and child theme from a backup two days back. The only change I know of last night was a wp upgrade, but rolling that back also didn't fix it.

I am hosted at WP Engine.

Here's what they see:

So I'm seeing this in the console logs:

Mixed Content: The page at 'https://purpleroofs.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/themes/south-street/jquery-ui.css?ver=1.19'. This request has been blocked; the content must be served over HTTPS.
...
so it looks like the site is trying to load an external resource over https, we could try toggling the theme / plugins to see if that helps
...
So it looks like I'm not seeing the same type of error when I set the theme to a default - based on that plus the error I'm seeing in the console logs it seems like it's likely a theme issue; I'd recommend reaching out to the theme developers directly to see if they can provide any additional insight as to why that error is occurring

I need to get this fixed ASAP as the site looks awful. What do you need from me?

HI there,

Mixed Content: The page at ‘https://purpleroofs.com/' was loaded over HTTPS, but requested an insecure stylesheet ‘http://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/themes/south-street/jquery-ui.css?ver=1.19'. This request has been blocked; the content must be served over HTTPS.

This isn't a file from GP or GPP so I'm not sure why your hosting would say that.

The theme itself has no control over the SSL side of things. This article explains what the warning means:
https://web.dev/what-is-mixed-content/

I would recommend going through some debugging steps like disabling all plugins and custom functions, activate the parent theme if you are using a child theme etc.

They already tried a different theme and the problem went away. My developer also tried backing up to a previous version of the GP theme and the issue went away last time. So all signs point to a GP issue.

Did you take a look at the site to see the actual issue?

Thanks!

Have you done the debugging steps here first?

I would recommend going through some debugging steps like disabling all plugins and custom functions, activate the parent theme if you are using a child theme etc.

OK, I activated the main theme instead of the child theme, and the issue went away. So what next to fix it?

That means something in your child theme is causing the issue so it's not a theme issue.

I'd assume your developer created the child theme and added content in it so I'd recommend you to contact him.

OK, here's my developer's reply, and a question:

Tell them this is the enqueueing in the child theme and ask if it should be using a different css file

function moobdir_child_theme_enqueue_styles() {

$parent_style = 'generate-style'; // This is 'twentyfifteen-style' for the Twenty Fifteen theme.

wp_enqueue_style( $parent_style, get_template_directory_uri() . '/style.css' );
wp_enqueue_style( 'child-style',
get_stylesheet_directory_uri() . '/style.css',
array( $parent_style ),
wp_get_theme()->get('Version')
);
}
add_action( 'wp_enqueue_scripts', 'moobdir_child_theme_enqueue_styles' );

I'd recommend starting with a blank child theme from our documentation here:
https://docs.generatepress.com/article/using-child-theme/

We can't really help with debugging the custom functions you've added.

The best way to solve issues like this is to remove each function and identify the one that's causing the issue.

She fixed it. And she's amazing.

Glad to hear :)

Always good to check the custom functions in the child theme before identifying the theme as the issue.

This archived topic is closed to new replies.