404 when Google Fonts are loaded using relative protocol

  • Resolved rokesmith

    (@rokesmith)


    4 years, 11 months ago

    This is an awesome plugin, thank you!

    I am having some difficulty with Beaver Builder and your plugin. I think the problem is related to the fact that they are loading Google Fonts using the relative protocol (//fonts.googleapis.com instead of https://fonts.googleapis.com). The problem I am ending up with is a 404 on the page. It seems like FVM is treating this like a directory rather than an external link which results in the 404. If I am right could you consider fixing this? If not, is there some way to stop this happening?

    Best,

    Joseph

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author Raul P.

    (@alignak)

    Hi, sorry the late reply.

    I cannot reproduce your error.
    I tested enqueueing 2 google fonts with dynamic protocols and it worked as intended on a few tested themes.

    function custom_theme_name_scripts() {
    wp_enqueue_style( 'style-name1', '//fonts.googleapis.com/css?family=Roboto&display=swap');
	wp_enqueue_style( 'style-name2', '//fonts.googleapis.com/css?family=Open+Sans&display=swap');
}
add_action( 'wp_enqueue_scripts', 'custom_theme_name_scripts' );

    I also tested beaver builder and no problems as well.
    It could be some theme or plugin modification you done somewhere?

Viewing 1 replies (of 1 total)
  • The topic ‘404 when Google Fonts are loaded using relative protocol’ is closed to new replies.