Migration of an old site to a local working version
Permalink
One of our clients has come to us with an old concrete5 site (5.5.2, by the looks of the code. Which makes it 1.5 years since it was updated).
I have very little to go on so i wanted to create a local version of the site to work on and possibly upgrade.
I downloaded all the files following the guide outlined on the site, i also made a copy of the sql (i didn't move the statistics table as this seems to have over 1.5million entries)
I then installed it on to my local MAMP stack.
The problem is that the site always seems to redirect to the login page and the login details that i have for the site do not seems to work correctly (even though they work fine on the live site).
This would be my first venture in to concrete5 so I'm not entirely sure where to start trouble shooting.
Any help would be appreciated Thank you.
I have very little to go on so i wanted to create a local version of the site to work on and possibly upgrade.
I downloaded all the files following the guide outlined on the site, i also made a copy of the sql (i didn't move the statistics table as this seems to have over 1.5million entries)
I then installed it on to my local MAMP stack.
The problem is that the site always seems to redirect to the login page and the login details that i have for the site do not seems to work correctly (even though they work fine on the live site).
This would be my first venture in to concrete5 so I'm not entirely sure where to start trouble shooting.
Any help would be appreciated Thank you.
I have done both of these things, I didn't download the cache file content how ever the file does still exist.
Try this to recover password.
http://www.concrete5.org/documentation/how-tos/developers/recoverin...
Rony
http://www.concrete5.org/documentation/how-tos/developers/recoverin...
Rony
Unfortunately this didn't work. Not sure if turning on the error reporting will help, Not sure if this is on by default or not.
That might help but you cannot do it without logging into dashboard. If you can do it through database that would be fine. Unfortunately I don't know how to do that. But I assume it is the cache that creates the mess.
Rony
Rony
under the db in the config table SITE_DEBUG_LEVEL is set to 1, so i guess its on.
Rony