Thread

I cannot access my website and I am not sure what is the problem.

sjc.org.sg

Help appreciated.

Bearelite,

have a look here

EE KB : Visiting my site results in a blank page.

Make sure the contents of your index.php and path.php are intact.

I have not changed my index.php and path.php files. The site went dead all of a sudden.

I use this link, but I cannot figure out what it is instructing me to do. 

Do you want me to paste the index and path files here?

I tried adding error_reporting(E_ALL); and ini_set(‘display_errors’, 1); to the index.php lines.

Nothing changed.

I am also not sure which index.php files are being referrred to - at root or system folder?

At the root. See also this article: http://expressionengine.com/wiki/HowTo_Turn_on_Error_Reporting/ It’s most likely a PHP error of some kind, perhaps running out of memory. Do you know how much RAM you have on the server?

The problem is now I cannot even go into my control panel. I tried changing the path.php file (trying to turn on error reporting), and that must have compounded the problem further.

Ram on server? I have to wait for Monday working day to ask those server guys. But pls, I need some solution - it’s unnerving that the site can be that unstable. Also need more hand holding on those php stuff and it is beyond me.

Manage to go to Cp. But site still down.

...

Bearelite:

Do you have access to your hosting control panel?  If so, can you see your apache logs in there?  There is probably something in those that can let us know what is going on.  Also, do you remember what version of ExpressionEngine you are running?

-greg

EE 1.6.7
I can go into my control panel.
Apache log - what is that and how do I access that?

The log location in your hosting control panel (not EE) is going to vary, so you’re best to ask your host.  Sorry, I missed it above, but did you add the display_errors lines to your index.php files?  I’d go ahead & add them to both files for the time being.

-greg

Even switching on error reporting is difficult. I find those documentaiton (links above) hard to follow and so many ways a non-tech-php guys like me can trip up:

Which index.php file - which is for root and which is for system? Where is the line to insert if the file is accessed?

And here is the rub - each time i change the system index.php file, I can no longer access my CP. And so I have to ftp my original index.php to system folder.

In short, I don’t know how to turn error reporting on and any attept to take those steps complicate my problem.

okay, download the main site index.php file, look for:

error_reporting(0);

Change that to:

error_reporting(E_ALL);

Right below that line, add:

ini_set('display_errors', 1);

Upload the file to replace the main index.php file.  Then go into the system folder, download the index.php file & repeat the same steps.

-greg

Ok i did that. Swith on ourput debuggin to be viewed by all and accessing the site reported below. Ok I will switch offf bad behaviour extension:

- info deleted for security reasons -

And..it is now back on. Thanks so much Greg.

Perhaps those error reporting instrucitons can be made more clear and it will be helpful to others.

I wil need now to find out why bad behavour is blocking access to site.