Your call to https...screen.css is redirecting to http...screen.css.
So the relative background images referenced in the css are coming from http, not https.
Probably something in the .htaccess file or your SSL plugin.
Thanks for the help!
The problem is with serving the css via a modx resource (e.g. [~8~]). Which is a preferable method because I can create dynamic variables. However it is not served via SSL. I've confirmed that the resource:
1. the template set to blank,
2. the internet media type is set to css/text,
3. rich text is unchecked.
If I externalize the file (i.e. /assets/templates/screen.css) it works fine and the connection is secure. However, I no longer have dynamic variables.
Does anyone know why this would be happening or how to fix it?
You are correct. Simply putting: [~8~} will not work, nor will:
1.[(base_url)]/[~8~]
2. [(base_url)]/screen.css
3. screen.css
The only way it works is a hard-coded file, in other words NOT a resource that is accessible from the doc tree. I may just have to live with it. MODx has always been fussy about screen.css as part of the doc tree.
Thank you for your help!