The Foxy forums are on the move!

We're in the process of moving our forums over to a new system, and so these forums are now read-only.
If you have a question about your store in the meantime, please don't hesitate to reach out to us via email.

automagicache reference to non-secure image, only on cart & checkout, not receipt.

ahsodesignsahsodesigns Member
in Important News edited September 2014

here's the store domain :

we're working on the purchase flow for for reba on the wpengine staging server :

we're cacheing wordpress pages as templates for cart / checkout / receipt

and having an issue w/ a singular image :

this guy ->
when updating the cart and checkout templates, after cacheing we get the warning :
A reference to a non secure image was found
( suddenly, a non-secure image appeared! )
but just for that one image, and not on the receipt page, where the css reference for it is also present.

the image is referenced from a block of custom CSS developers can add via an admin texteditor, that gets output in the head, here :
<style id="ahso-custom-code-css" type="text/css"></style>

it's being referenced in two places in the custom css, here are the selectors :
.television-episode-area .wpb_wrapper {
    background-image: url( !important;
    background-position: right bottom !important;
    background-repeat: no-repeat !important;
/* Diamond on the border */
.album-video-area .wpb_wrapper, .diamond-top .wpb_wrapper {
    background-image: url( !important;
    background-position: right bottom !important;
    background-repeat: no-repeat !important;

what's blowing my mind is this :
there are several references to other images in the custom css, in the same directory, with absolute paths, and id params in the URL,
and it's not an issue on the receipt template.

let us know what we're missing or need to do differently.
thanks again!

stay foxy.
  • fc_adamfc_adam FoxyCart Team

    I just saved your template locally and did a quick test - trying with and without the querystring on the end of the image URL and it cached fine without the query string, but failed to with it present. Unfortunately we don't currently support query strings appended to assets to be cached.
  • excellent, a super easy fix.
    thanks again!
Sign In or Register to comment.