Jump to content

Upgrade to test subdomain crossed up, then can't login to BO


Recommended Posts

I've been trying to upgrade my 1.4.4 install to the current 1.6, installing the upgrade first on a test subdomain. The creation of the subdomain and copy of the 1.4 install onto it seemed to go fine. The upgrade itself didn't show any problems, but I had various problems operating on this install such that I rolled back the upgrade twice and repeated the process. The problem has two aspects: first the ssl, when enabled is completely mixing up the sites and databases, the second is a login problem if the ssl is turned off.

 

I eventually understood the first problem goes like this: http://test.mydomain.com takes me to the upgraded 1.6 install, whereas https://test.mydomain.com will actually take me to my live shop with the 1.4 install. More precisely, if I type in https://test.mydomain.com (FO) the browser will redirect to http://mydomain.com with an "unsecure site" warning, but https://test.mydomain.com/admin(BO) will actually take me to the 1.4 login page without redirecting at all, and from here I can login without problems.

 

The second problem is if I turn off the SSL to the site and go to test.mydomain.com/[bO]. Now I see the 1.6 install. And I was able to sign into this site, a few times it seems (although I was trying every browser on every computer in the house, so I can't remember for sure if I got in through the same way twice or not, but I believe I did). I've done all the things recommended in similar threads here, clear cookies, browser cache, etc. The dev console shows no errors, and the sign in with the correct data flicks over and clears the data with no other change, sign in with incorrect data will give the "user not recognized" message. I think I did see in one of the threads that SSL has to be turned on in the back office in 1.6, so it could be that my second problem isn't the problem really, only the first one is. 

 

Ideas?  :mellow:

Edited by paciocco (see edit history)
Link to comment
Share on other sites

I've come up with a sort of solution, but I have doubts still. I ended coping all my files from /public_html/test/ to /public_html/newtest so now my BO login is https://mydomain.com/newtest. Now it logs in fine in SSL.

 

I guess my doubt lies in the fact that we were recommended to set up the test install in a subdomain instead of a subfolder, and I assume there is a reason for that. Might I face a consequence of this workaround later on, like when I try to migrate the upgraded install to the live site?

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...