Jump to content

(SOLVED) New upgrade from 1.1 > 1.2.5


Recommended Posts

Hi there..

I have completed the upgrade and everything seemed successful so far. When I transferred the test site to the main domain (copying over the previous 1.1 upload/install), I found I've got some SSL issues.. It seems as though the site (even though I have selected SSL in the preferences) is still refering to scripts and the like as http:// ?

Is this a known fault..? Or am I being an idiot!? :) I've changed a few bits on there with no joy, just wanted someone to back me up on my diagnosis really as if I am correct I will have to go through the code and change every link to a HTTPS myself I guess..?

I could clear the server and just upload the clean 1.2.5 install as I have backups of both, but I would of assumed this should not be the case, as all important and referential files would have been overwritten.(?)

Any input or ideas here are appreciated!!!!

Thanks in advance

Link to comment
Share on other sites

quick update: i've noticed that the SSL seems to be more restricted to the ordering phase now.. maybe this is where my confusion lies..? my browser appears to throw no errors if I stay on HTTP until ordering time, then it switches onto HTTPS without any errors it seems..

although the category menu is still not showing for some reason either...

thoughts still appreciated fellow Presta lovers! :)

Link to comment
Share on other sites

yes it seems to have settled down down. where before on v1.1 it was constantly on https:// no matter which part of the site the user was on. now it seems to only switch to the https when the user goes into the order stages. Because on the v1.1 site I had coded a lot of the links in as https links, everytime I clicked them and browsed to a page that now was not https on v1.2.5, it seemed to give me a SSL authenticity error. I've now removed these links, and the site functions fine on http, and also so far functions without error on v1.2.5 either. Links, coding and making sure you have the right settings is also helpful. I read on another guys post that he fixed his issues by turning the v1.1 Compatibility option on in the Preference settings on the admin side.

hope this helps!

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...