Upgrading to 1.3.5 seems to have broken certificate.

Hi,

Just been updating the site:

https://www.sexykaftans.com

to 1.3.5 from 1.3.0.2. When I now add a product to the basket and then go to checkout, I get a certificate problem which wasn't happening with 1.3.0.2. None of the images are hard coded no I'm at a bit of a loss. Any ideas?

Thanks, Richard

You have several things wrong on your site ...

If you click the Login link, the page is not secure ...

If you are not logged in and click the checkout, you are calling images that are not secure ...

First, switch to Classic ... does this fix the links so that clicking Login is secure and clicking checkout from shopping_cart does not throw the secure issue or show a broken or missing lock?

Hi - ok, just quickly I've set the template back to classic. I know the login link at the top wasn't secure - that was something I was going to be doing tomorrow.

As far as I can see, I've only used images relatively.

Thanks for your quick reply.

All of your checkout links need to call the secure page and they do not ...

Look in the original header and how the checkout_shipping is called ... you need to use that same method for your sidebox link ...

NOTE: It looks like some of the files were overridden and others you either started out using Classic or have used core code ... be sure to check that all changed/modified files are using your template and overrides directories ...

Note: the View Past Orders is broken in Classic so you are either calling a bad link or moved/deleted a file physically out of Classic ...

If you peek at your site in FireFox ... when you try to go to a secure page and get the warning, you can click on the broken lock and then the Media Tab to see what images are not being called right ...

Most likely most of these are in your header ...

Yep - I know and it says that they're all from http:// but when I look at the code the only http:// references are links - not image paths.

Would it have anything to do with the <base href="http://www.sexykaftans.com/" />?

Cheers,

Richard

Sorry, just to add, I have done a fair bit of hard coded link adjustment but I just want to be at a point where I can get one page running securely by itself. It all seems to be ok in the admin login screen.

Did you hardcode the base href?

Nope - the base ref was just created in the html_header file. I have a couple of other sites where I disabled it and everything was fine but when I disabled it here just now, it made no difference.

The problem with this site is that I had to completely redesign everything as you can see so I just need to work out what the new version has done.

Any further ideas? I made a backup of the old site so will try restoring the template from there so I can see whether it is the template or worse still a change to one of the core files that's causing the trouble.

Richard

Just to follow up, it was the link to the google analytics script that was causing the trouble. Obvious really but I ignored it as a problem as it had been working earlier yesterday and wasn't modieifed at all in the update.

Thanks for your suggestions,

Richard