ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

EE2.1.3 CPcomes up blank

January 11, 2011 1:46pm

Subscribe [4]
  • #1 / Jan 11, 2011 1:46pm

    stubear

    114 posts

    I first tried moving a development site to a staging server on Media Temple but nothing I did seemed to make the site function at all.  The CP and the site itself were all blank.  I tried installing a fresh copy of EE and while the install scripts worked fine, the site and control panel also come up empty.  If you look at the source code it’s empty, nothing, nada.  I’m really at a loss here.  I followed the installation instructions to a tee despite having installed EE2 and EE1 on more than a few occasions, even on Media Temple.  Is there something I can do to narrow this down to an EE issue versus a hosting issue?

  • #2 / Jan 11, 2011 2:10pm

    I first tried moving a development site to a staging server on Media Temple but nothing I did seemed to make the site function at all.  The CP and the site itself were all blank.  I tried installing a fresh copy of EE and while the install scripts worked fine, the site and control panel also come up empty.  If you look at the source code it’s empty, nothing, nada.  I’m really at a loss here.  I followed the installation instructions to a tee despite having installed EE2 and EE1 on more than a few occasions, even on Media Temple.  Is there something I can do to narrow this down to an EE issue versus a hosting issue?

    Check in the control panel or w/ a php_info() script to see if you have PHP5 enabled.  Dedicated servers come with PHP4 installed by default, you may need to manually update PHP…

    We’re using MediaTemple for all of our sites and EE 2.1.3 works fine on our GS servers, but not our DV servers. (due to PHP4)

  • #3 / Jan 11, 2011 5:32pm

    stubear

    114 posts

    PHP5 is enabled.  I checked that first.  Also, the EE Server Wizard confirmed PHP5 being present.

  • #4 / Jan 12, 2011 8:08am

    Sue Crocker

    26054 posts

    stubear, are you using GS or DV for your MT site?

  • #5 / Jan 12, 2011 9:40am

    stubear

    114 posts

    It’s a GS.

    update: it was recently converted from a SS site (needed more web space and databases).

  • #6 / Jan 12, 2011 6:32pm

    Sue Crocker

    26054 posts

    What I’d do first is install 2.1.3 on the new GS site. Get that working first, then get your database in there from your dev site.

    At least that way you have a good foundation to work with. Does that help?

  • #7 / Jan 12, 2011 6:48pm

    stubear

    114 posts

    That was the second thing I tries.  I created a new DB and everything.  Same result, correct URL, but blank page with no code, errors, or anything at all.  This was on both the login and the home page.

  • #8 / Jan 13, 2011 8:15am

    Sue Crocker

    26054 posts

    Huh. Did you try with the Agile templates active during install? I haven’t installed in a few weeks on my GS.

    What FTP program are you using? Can you try turning on $debug = 1; in the index.php file in your root?

  • #9 / Jan 13, 2011 1:03pm

    stubear

    114 posts

    OK, I’ve narrowed this down to a potential issue with MySQL.  I setup a subdomain on my personal GS site to install the Agile site and everything worked fine.  One difference I noticed was my GS account databases are still on MySQL 4 but on this new GS server I’m setting the site up on is using MySQL 5.  The EE Server Wizard didn’t seem to have any issues with this and I can’t really think of any but this is the only difference I can find between the two accounts.

    UPDATE:
    I just tried installing 2.1.3 on a co-workers GS account and had the same problems.  This account and the account I originally tried both run MySQL 5 while my account is still on MySQL 4.  Could just be coincidence and there are other issues with MT unrelated to MySQL.

    UPDATE 2:
    Fresh install again and this time I switched on $debug before leaving the installation successful screen.  I got this error message:

    Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 92 bytes) in /nfs/c08/h02/mnt/115415/domains/staging.monderer.com/html/ee_sys/expressionengine/core/EE_Lang.php on line 192

    UPDATE 3:
    It appears to be an issue with memory and php.ini.  I bumped up the limit and things are starting to work.  EE thinks the login page is the home page but I’m gong to try to upload the dev files I tried to originally upload and work from there.

  • #10 / Jan 14, 2011 2:37am

    John Henry Donovan

    12339 posts

    stubear,

    Glad you pinpointed the source of the problem. I’ll keep this thread open a while longer while you up the dev files in case of further issue

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases