Thread

I’m working on a site where I get a blank pages on all the weblog admin pages (e.g. manage weblogs, custom field, file uploads) and also on the Utilities / PHP Info page. I read in some other threads that it might be related to memory limit, but the server’s limit is 64Mb. I’ve also reuploaded all CMS folders & files. Is there anything else that would be causing it?

Hi, Tyssen. 64 megs should be enough for EE1.x (EE2.x too.)

Are you loading in any sort of extensions?

Are you on the most recent 1.6.9 build?

Hi Sue, yes using the latest build and I tried disabling extensions and the problem remained.

Tyssen,

Please enable error reporting and let us know what you find.

The value for display_errors is set to STDOUT; is that the same as on? I added

ini_set(‘display_errors’, 1);
error_reporting(E_ALL);

to system/index.php but am still getting blank pages.

STDOUT should be the normal output, but consult your server’s PHP error logs for clues just in case. To clarify, you have extensions currently disabled via config.php, correct?

Yep, extensions are disabled in config.php. I’m not able to access the PHP error logs on this server.

John,

Is this something that just started happening all of a sudden?
Can you ask you host if anything has recently changed on their side?

Is the front-end working for you?

Can you run our Server Wizard just for piece of mind please

It’s a new site I’m setting up and I haven’t dealt with this host before. Front end works OK although I haven’t really done much with it yet. Just ran the wizard and got the OK on everything.

Tyssen, ask your host about getting access to the error logs, or have them look as you get a blank page. If possible you might try raising the memory limit also to rule that out.

I was just about to contact the hosts about the issue when I thought I should log in again so that I could give them a more up-to-date time to look for errors, but I couldn’t actually log in. I could see the login page OK, but after submitting, I got the following:

Notice: Trying to get property of non-object in /home/xxxxxx/public_html/store/cms/core/core.session.php on line 1049

Warning: Cannot modify header information - headers already sent by (output started at /home/xxxxxx/public_html/store/cms/core/core.session.php:1049) in /home/xxxxxx/public_html/store/cms/core/core.functions.php on line 742

Warning: Cannot modify header information - headers already sent by (output started at /home/xxxxxx/public_html/store/cms/core/core.session.php:1049) in /home/xxxxxx/public_html/store/cms/core/core.functions.php on line 315

I found another thread that suggested to try logging in with admin.php which was successful and then after that I was able to access /system/index.php too. So what does that mean? :?

Honestly, I have no idea what causes that kind of problem other than were you using sessions?

I’m just glad things are working again.

Tyssen, ask your host about getting access to the error logs, or have them look as you get a blank page. If possible you might try raising the memory limit also to rule that out.

I had a lot of trouble getting to the point where I could even get error messages with this host, but finally here they are:

Trying to get property of non-object in /home/xxxxxxxx/public_html/system/core/core.session.php on line 1049

PHP Warning:  Cannot modify header information - headers already sent by (output started at /home/xxxxxxxx/public_html/system/core/core.session.php:1049) in /home/xxxxxxxx/public_html/system/core/core.functions.php on line 742

PHP Warning:  Cannot modify header information - headers already sent by (output started at /home/xxxxxxxx/public_html/system/core/core.session.php:1049) in /home/xxxxxxxx/public_html/system/core/core.functions.php on line 315

What version of PHP are they running? If 4.x, try switching to 5.x. Or vice-versa, perhaps.

If there’s still no change, try uploading a fresh set of files (essentially performing a build update).

They’re on 5.x. And I’ve just reuploaded all the system files again and same result. I don’t really want to downgrade to 4.x as there’s a few add-ons I use that require 5.x (on top of which the server support aren’t particularly helpful).