Sign in

a static portfolio after the https move: a half-styled page, culprit unknown

Solvedhttpsmixed-contentssl4 replies · 228 views · started
Reply
Accepted solution by Kenji Z. — for WordPress, old URLs live in the dataabse. use WP CLI: wp search replace 'http://example.com' 'https://example.com' all tables dry run,…
  1. Leon
    @leon.brandt52

    finally moved a static portfolio to HTTPS... certificate installed, the host says its valid, teh checker says its valid... but visitors see a half-styled page.

    i think it has to do with teh stylesheet still loading over plain http, but i have no idea where those links come from. i didnt hardcode anything, at least not on purpose. How do i find every insecure reference without reading every file by hand?? seriously need help here 😭

    2
  2. Eamon Rossi
    @loosenomad

    which URLs exactly does teh console list as mixed content? ??

    25 0 helpful
  3. Leon
    @leon.brandt52
    in reply to @loosenomad

    sorry forgot to say i only installed the certificate... the app settings still have teh http:// address for a static portfolio. hope thats enough info 😅

    9 12 helpful
  4. Kenji Z.
    @kenjiz943
    in reply to @leon.brandt52

    hmmm open DevTools > Console. each mixed content warning names the exact insecure URL: Mixed Content: The page at 'https://...' was loaded over HTTPS, but requested an insecure resource 'http://...'. collect those URLs; the domain and path usually tell you whether it's theme code, uploaded content or a third-party embed. worked for me anyway 🤷

    0 3 helpful
  5. Kenji Z.
    @kenjiz943
    Accepted solution

    for WordPress, old URLs live in the dataabse. use WP-CLI: wp search-replace 'http://example.com' 'https://example.com' --all-tables --dry-run, check the count, then run it without --dry-run. It handles serialized data safely, unlike a raw SQL replace 👍 Take a database backup first.

    1 6 helpful

Reply to this topic

Sign in or create an account to reply.