Today we pushed our new EE2 site live on a new server. It looks good, works well, etc.
Due to time constraints, we were not able to upgrade the entire site, and left several sections on our old EE1 server. These are relatively contained areas, such as a customer area with its own login.
This did not work cleanly, and I could use some help resolving (yuk yuk) the issue.
We started with:
EE1 Server: companyname.com
EE2 Server: dev.companyname.com
We pointed companyname.com to EE2, and pointed legacy.company.com to EE1. So we have:
EE1 Server: legacy.companyname.com
EE2 Server: companyname.com
Problems:
- Many instances of companyname.com appear to be hardcoded into pages. We expect to have to adjust these
- When we attempt to login to EE1 , we are refused access. Similarly, no one can log into the customer areas on EE1 server.
I assume we need to update the new domain name in config.php and also in the admin section.Is there a list of areas that need to be updated?
As a “quick fix” we reverted EE1 to companyname.com and EE2 to http://www.companyname.com hoping this would fix the database issue.
EE1 Server: companyname.com
EE2 Server: http://www.companyname.com
However this still seemed to cause issues as there were still some constant calls from EE1 to http://www.companyname.com. This leads me to believe I am not getting all the hardcoded instances of the domain in EE1.
Any input appreciated.
Thanks,
jcd