Try getting rid of the trailing commas in your arrays.

@UncleCheese that wouldn't do anything :P This is PHP, not IE JavaScript

This looks like a memory problem - can you try increasing your memory limit to 64M? The most recent problems appear to be because the JavaScript minifier ran out of memory while parsing a file.

Alternatively, you can put "Requirements::set_combined_files_enabled(false);" in your_config.php file to disable file combining and reduce memory usage.

@ajshort -- You'd be surprised. I always thought that syntax error was isolated to IE javascript, but my PHP configuration barfs on it all the time. The only time I've been able to get away with it is when I'm running Symfony. I think there must be a flag somewhere upstream in the php.ini that toggles a tolerance for the trailing commas.

That said, yes, boost your memory. All my sites run on 128M.

I deleted the Commas, and added the line of code and now the admin page works!! Thanks guys!!

How do I boost the memory? I'm running on a host server through 3iX. It uses cPanel X.

I usually get away with "ini_set('memory_limit','128M');" in my _config.php.

Did this get solved? I am having the same problem. I got no errors while installing the CMS, but when I navigate to http://www.mysite.com/admin, I get a BLANK page.

To make things even more interesting, all the tabs in the CMS EXCEPT for "Site Content" load fine, eg. http://www.mysite.com/admin/security/, http://www.mysite.com/admin/assets/, etc. But the Main tab is a blank page. Someone please help! I have to deploy this TODAY!

Thanks,
Garrett

People,

You can't expect anyone to troubleshoot your problems if all you're reporting is a blank screen. You need to crank up your error reporting and get some tangible errors -- or check your error logs to see what's going on -- or set your config file to email errors with Debug::send_errors_to() -- or at least post a snippet of the code you suspect is the culprit.

A blank screen could be millions of different things, so please do your part and use your resource to find out the error rather than asking someone else to summon psychic powers. With a descriptive PHP, MySQL, or Apache error, we can not only figure out the problem, we can also figure it out quickly.

That's a totally fair comment! You're right. "Blank Page" is way too vague. I was just having a HECK of a time finding the PHP error log on this Unix box-- I am used to Windows-- and when I found it, it turned out to be a Memory issue indeed. Was set to 16M and I bumped it to 64 on php.ini. Thanks for your reply.

//Garrett