Thanks for the assist, ralph.m.
Hitch, in addition to the suggestions ralph.m made, can you tell us more about your host? Can you also create a phpinfo file to test for how much memory is allocated to PHP?
See: http://expressionengine.com/wiki/Create_a_PHPInfo_file
Hi, Sue:
Have done all of the above. (First, just because I was ripping my hair out, I’ve purchased Engine hosting, and hopefully I’ll have that access today, but that’s neither here nor there. Because I’m trying to rebuild, from the ground up, an existing site, I’m using a different domain name at EngineHosting so I can get the site set up and get a redirect before I take the old one down…hope that’s okay, I will technically have two EE sites running for a day while I go up and down, if you see what I mean.)
@ralph.m.—uploaded and re-uploaded 3 times. I had changed the system folder’s name, but then changed it back when I ran into WSOD (White Screen O’Death) the first time. Actually, I ran into, this file doesn’t exist, so even though I’d edited index.php and changed the system variable, I changed it back. And I’m browsing to it just as I should; http://www.mysite/subdir/system.
@Sue—and I know you’ll sigh heavily—the existing host is GoDaddy, but I’ve run my phpinfo file, at 3-something this morning, (in addition to the compatibility wizard, which was green across the board), and according to it, my mem_limit is 64MB. I’ve got PHP 5.2.17; mysql 5.0.18. I set all the file and directory permissions and checked them 4 times.
I mean, I’m already running an EE 1.6.8 site merrily on this, and I managed to install that (admittedly, a while ago) without too much agita…but this is a poser.
IF I get the EH access today, I’ll try to take down everything at GD and upload to EH and see what happens, but I don’t see why this would be occurring, all things considered. So I’d still like some input, even though at EH it might go just fine. The WSOD is annoying; usually when my stuff goes wrong I get a total kablooey, not a whiteout.
Hitch