Secure and unsecure items problem

[authenticnz]

That wasn't the problem - I removed the image and associated script and I still have the problem.

[authenticnz]

I was checking similar threads and followed the advice to double-click the broken padlock for more information. This is the list of media for the page:

http://store.authenticnz.com/include.../tile_back.gif
https://store.authenticnz.com/images/anz-logo.gif
http://store.authenticnz.com/include...tton_login.gif
http://store.authenticnz.com/include...ton_submit.gif

As you can see, my background image and a couple of the buttons point to http:// instead of https://. These are zen-cart generated, so I am not sure how I can set them to load from https instead. That's the same problem I had with my logo, which as I said I hard-coded to load from https.

Any help would be appreicated!

[Merlinpa1969]

there is a hard coded link to

http://store.authenticnz.com/include.../tile_back.gif

[authenticnz]

I didn't hard code it. I just used the classic template through zen cart. I don't know how to set it to point to the secure site (i.e. https://) rather than http://

In the css code, it's set to ../images/tile_back.gif so it's a relative link.

I don't want to hard code it because that appears on all the pages, secure and non-secure.

[kobra]

Think this is more basic than an image or two as when viewing your source for this page:

your site login page source:

<base href="http://store.authenticnz.com/" />

other sites:

<base href="https://www.XXXXXXX.com/" />

Might begin with posting the first 15-20 lines from your includes/configure.php file

[authenticnz]

Here's my code from includes/configure.php

// Define the webserver and path parameters
  // HTTP_SERVER is your Main webserver: eg, http://www.yourdomain.com
  // HTTPS_SERVER is your Secure webserver: eg, https://www.yourdomain.com
  define('HTTP_SERVER', 'http://store.authenticnz.com');
  define('HTTPS_SERVER', 'https://store.authenticnz.com');

  // Use secure webserver for checkout procedure?
  define('ENABLE_SSL', 'true');

// NOTE: be sure to leave the trailing '/' at the end of these lines if you make changes!
// * DIR_WS_* = Webserver directories (virtual/URL)
  // these paths are relative to top of your webspace ... (ie: under the public_html or httpdocs folder)
  define('DIR_WS_CATALOG', '/');
  define('DIR_WS_HTTPS_CATALOG', '/');

  define('DIR_WS_IMAGES', 'images/');
  define('DIR_WS_INCLUDES', 'includes/');
  define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');
  define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');
  define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');
  define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');
  define('DIR_WS_DOWNLOAD_PUBLIC', DIR_WS_CATALOG . 'pub/');
  define('DIR_WS_TEMPLATES', DIR_WS_INCLUDES . 'templates/');

[richcolour]

I've just solved this problem on my site. The offending bit of code was in the stylesheet.css for my chosen template. I had hard-coded the URL of the header background gif. To solve it I made it a relative link (../images/header_bg.jpg) and uploaded a copy of the gif into the template's images folder.

Your problem sounds more complex but this might help.