Yeah, that would do it.
Good luck with the update. Basically before I ran into the same issue it was because of the path.php file. Knowing that I needed to restore it this time around helped.
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
April 26, 2011 2:58pm
Subscribe [3]#16 / Apr 26, 2011 5:41pm
Yeah, that would do it.
Good luck with the update. Basically before I ran into the same issue it was because of the path.php file. Knowing that I needed to restore it this time around helped.
#17 / Apr 26, 2011 5:43pm
OK ... I just restored and changed the cp url in general setting and it broke the main site. Are you saying that this breaks the path.php ?
#18 / Apr 26, 2011 5:45pm
I have no clue in your instance. My path is always been the default blank.
#19 / Apr 26, 2011 5:50pm
Mine is ok same as it has alway been. All I did was change the domain name and it breaks the site? Man total confusion here
#20 / Apr 27, 2011 6:22am
Mark,
You are upgrading from 1.6.8 to 1.7.1 which is a version update and not a build update.
You actually linked to the EE2.x build update docs
What you need to follow is the EE1.x version update docs available here
Can you revert and follow those docs and see if your issue still persists please