JavaScript for WordPress Forums Gutenberg Development Mixed Content: The page was loaded over HTTP but requested an insecure styleshee

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #38879
    bobbingwide
    Participant

    I’m running the course in my local machine called qw and get the following message in Chrome.

    Mixed Content: The page at ‘https://qw/src/wp-admin/post-new.php’ was loaded over HTTPS, but requested an insecure stylesheet ‘http://fonts.googleapis.com/cssfamily=Archivo+Black|PT+Sans:400italic,700italic,400,700’.
    This request has been blocked; the content must be served over HTTPS.

    I realise the problem is to do with the scheme on the import statement in some .scss files, so I have changed it to

    @import url(https://fonts.googleapis.com/css?family=Archivo+Black|PT+Sans:400italic,700italic,400,700);

    I have two problems
    1. How do I change it work correctly regardless of scheme ( https or http )?
    2. npm run build seems to halt in sass-loader. I believe this is a known problem but can’t find the fix on my Windows machine.

    Setting UV_THREADPOOL_SIZE=100 doesn’t resolve the problem, but commenting out the imports for .scss files does allow the build to complete, sometimes.

    #38901
    bobbingwide
    Participant

    I believe I’ve resolved the second part.
    1. The css files were being written to the wrong directory ( in the plugins/css folder )
    2. npm run build was being run with watch: true. I changed it to false.

    The UV_THREADPOOL_SIZE=nn setting was a red herring.

    #38910
    Zac Gordon
    Keymaster

    Oh good glad you got it solved!

    I did post a patch to that css issue, but if it fixed it once it should continue to work properly for you 🙂

    Please post up if you have any other issues!

    #38981
    bobbingwide
    Participant

    Hi Zac, I didn’t make it clear what I needed to change.
    1. To make the CSS work for http and https I removed the scheme
    2a. To recreate the files in assets/css I needed to get the latest version of the repo, with changes to the output paths in webpack.config.js
    2b. And in webpack.config.js I changed watch: to false to allow npm run build to complete.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.