I’ve over written my index.php page (I *think* only this page.
Front-end is down - http://www.waxonrecords.com
back-end is up - http://www.waxonrecords.com/ee_admin
Debug = 1 does nothing in the config file, help!!
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
January 27, 2011 12:16pm
Subscribe [3]#1 / Jan 27, 2011 12:16pm
I’ve over written my index.php page (I *think* only this page.
Front-end is down - http://www.waxonrecords.com
back-end is up - http://www.waxonrecords.com/ee_admin
Debug = 1 does nothing in the config file, help!!
#2 / Jan 27, 2011 12:34pm
I just need to find some kind of useful error message!
#3 / Jan 27, 2011 1:07pm
Hm… some things that will help tech support get you back up faster:
Is this a brand new install, or version upgrade from 1.6.x to 2.1.3 or just a site that was alive and healthy until the index.php file got zapped?
If you’re just replacing the index.php file from a fresh download, there are a couple of paths in there you might need to reset.
#4 / Jan 27, 2011 1:09pm
It was a completely healthy site, I just zapped the index.php file and (99% sure) nothing else.
Do I need to change more than the system_path?
#5 / Jan 27, 2011 1:13pm
Hmm I’ve found a back up of the index.php file, and it is identical to the one that has now been uploaded… I’m fairly certain that is fine… I just can’t see what else has changed!!
#6 / Jan 27, 2011 1:43pm
If it was just the index.php file then, system path would be main thing to adjust. If this is was part of an MSM site or site with the (no-longer supported) multi-site method then there’s a few other paths you might have needed set also farther down in the file.
More “silly” questions for you then.
Any changes to you .htaccess file (assuming you are using one)?
Also, any chance you had been calling the index.php file something else in this site, to have a cooler sounding /segment_1/ in your URI’s?
Oh… we should rule this one out too; You do have the /index/ template of some template group assigned within EE’s template manager as the main site file right?
Also, are the permissions set right on this newly replaced index.php file?
#7 / Jan 27, 2011 1:46pm
Ah… looks like you’ve just got a path issue to resolve.
Your system folder path does not appear to be set correctly. Please open the following file and correct this: index.php
#8 / Jan 27, 2011 2:00pm
Thanks all. This is issue is now resolved. Annoyingly, the problem appears to be on the network I was viewing the site on (another office). I’ve just dashed all the way home, tested it here and saw the config error message. Once I saw that, it was a doddle to fix.
I’m going to spend some time getting a proper staging/deployment/backup plan sorted this evening… Any tips?
#9 / Jan 27, 2011 2:06pm
Actually, my host has just been in touch. They fixed it - it was a permissions issue!
#10 / Jan 27, 2011 2:15pm
Hi Dominic,
For the record, when I first visited your site, it had a 500 type error. The EE specific path error didn’t show up until later for me, so it might not have been the network issue at the office.
So it was the permissions after all!
I’ll let someone else here tackle your dev environment question. I just wanted to help you get your site back up.
Enjoy!
#11 / Jan 27, 2011 2:16pm
Yup, permissions! Thanks for helping out, panic over 😊
#12 / Jan 27, 2011 4:07pm
Glad to see you’re up and running 😊 Please post again as needed.