Hi Sandra;
Not sure what is happening, but can try forcing all to https by simply setting your CDN to https://yoursite.staging.wpengine.com/
If that doesn’t help, I’ll come and have a closer look at what might be going on.
frank
Hi Frank,
I had already tried that, no joy though. I contacted WP Engine to see if it may have been something at their end, but no.
Thanks,
Sandra
having that closer look now, what I know so far:
* all 3 autoptimized CSS-files are loading on the HTTPS-site, but the main one is missing quite a few selectors
* the main CSS-file on http is different (bigger) then that on HTTPS
this means that there’s probably one CSS-file which (for reasons I don’t know yet) can’t be included in the autoptimized CSS when in https.
i’ll keep you posted once I know more.
frank
Hi Frank,
I suspect it is the main CSS file – I use Headway for the theme framework. Here’s a link to the live site which doesn’t have Autoptimise installed, so you can see. It looks like there are 3 CSS files linked to Headway. From what I know if a change is made to the CSS the number in the filename changes, so adding them to the exclusion list won’t work.
Hope that’s a help…
Cheers,
Sandra
the problem indeed is that for unknown reasons AO doesn’t seem to succeed in sourcing in the main CSS-file when in HTTPS (general-https-9548b5a.css).
-> can you check if that file has filesystem rights that somehow prevent AO (well, any PHP) from reading it?
-> as a (temporary) workaround you could try if adding general-https- to the comma-seperated CSS optimization exclusion list works
-> if possible, do check if the same issue exists on your production site.
frank
