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.

Blank screen when logging in to CP

July 05, 2010 6:34pm

Subscribe [2]
  • #1 / Jul 05, 2010 6:34pm

    Incite

    20 posts

    Recently we moved an EE site from one server to another. The site shows up, as does the login page for the CP. There is no formatting on the login page (a path issue to be sure).

    When I do log in, I end up on /index.php?S=0&C=login&M=auth. It’s just a blank white screen with (unfortunately) no error information at all.

    I’ve spent the last few hours pouring over the forums and have found several examples of this problem, but none appear to have a solution. I’ve re-uploaded files, checked permissions, etc. I’ve triple checked the path.php and config.php files and they appear to be fine.

    I’m hoping someone might have an idea.

    EE: 1.6.8 (the previous site was also 1.6.8)
    PHP: 4.4.9

  • #2 / Jul 05, 2010 7:08pm

    Brandon Jones

    5500 posts

    incitesolutions, let’s start with these:

    1. Make sure error reporting is enabled
    2. In your config.php file, try adding

    $conf['admin_session_type'] = "s";

    3. Completely clear your browser cache AND cookies. Then try logging in again.

  • #3 / Jul 05, 2010 8:13pm

    Incite

    20 posts

    Thanks for the prompt reply Brandon.

    Added all the error code you gave and changed the debug in the config file to 2 and finally got some errors.

    Notice: unserialize() [function.unserialize]: Error at offset 2845 of 3520 bytes in /home/website/public_html/system/core/core.prefs.php on line 129
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/website/public_html/system/config.php:31) in /home/website/public_html/system/core/core.functions.php on line 723
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/website/public_html/system/config.php:31) in /home/website/public_html/system/core/core.functions.php on line 296

    At least it’s something I can focus on.

  • #4 / Jul 05, 2010 8:19pm

    Brandon Jones

    5500 posts

    incitesolutions,

    Has the database been manually modified in any way, such as any find & replace operations? Also, would you say the front-end of the site is 100% working?

  • #5 / Jul 05, 2010 8:38pm

    Incite

    20 posts

    There have been 2 modifications to the database. The first was when moving it over I followed the moving servers article and ran this line;

    ALTER DATABASE `my_database` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

    The second modification was a manual modification of the site_system_preferences field where the paths to the themes were updated to the new server. I kept a copy of the old field contents which I’ll test quickly.

    Wow. You’re good.

    I’m not sure what happened. I added the old field contents manually back in and an extra space caused it to break (my shoddy copy and paste skills). I fixed the space and it started working. I then copy and pasted the update I made (the new field contents) back in just to make sure that’s what was the problem and it’s still working. Maybe there was a caching problem. There are some icons not showing up now but it looks like it’s just a path issue I’m sure I can resolve myself.

    Thank you very much for your help, it’s greatly appreciated.

  • #6 / Jul 05, 2010 9:03pm

    Brandon Jones

    5500 posts

    Yes, modifying the database manually will break data that is stored as serialized arrays, because you are not also updating the length of the data in the database. Hence, an error when doing an unserialize(). EE 1.6.9 has protections in place to prevent this.

    In any case, you’re back up and running?

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

ExpressionEngine News!

#eecms, #events, #releases