We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 13622
    • 74 Posts
    Hi,

    My apologies if this has already been covered...I must not be typing the right search terms.

    I just launched this site I designed for a non-profit I'm doing some side work for: http://www.transplanthouse.org/

    The only page this requires a secure connection is the application page: https://www.transplanthouse.org/apply-for-housing

    I'm running Evo v1.5 with the SSL plugin.

    It seems to be loading correctly, except for a few elements (using firebug) which appear to be loading via http:

    1. bg_blank.jpg
    2. screen.css
    3. spriteme.png

    The paths are relative, so I don't understand why they are loading with http and not https. Does anyone have any suggestions?

    I appreciate the help!

    -Jason
      • 4310
      • 2,310 Posts
      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.
        • 13622
        • 74 Posts
        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?
          • 4310
          • 2,310 Posts
          The only page this requires a secure connection is the application page: https://www.transplanthouse.org/apply-for-housing
          You'd need to serve document [~8~] {the css page) as https as well wouldn't you?
            • 13622
            • 74 Posts
            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!