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.

Site not visible after transfer to new host

August 17, 2010 5:40pm

Subscribe [5]
  • #1 / Aug 17, 2010 5:40pm

    fanderson

    899 posts

    I am in the process of transferring a site to a new server and am having trouble seeing the site in the test view. I put a standard html page in and it displays properly so there must be something wrong with the index.php, path.php or config.php but I am not sure which.

    Here is the current url: http://nu-living.com.s103645.gridserver.com/

    Any help would be greatly appreciated.

    Thanks.

  • #2 / Aug 18, 2010 1:52am

    webalite

    8 posts

    I had exactly the same problem. See: http://ellislab.com/forums/viewthread/164538/
    maybe this will help.

  • #3 / Aug 18, 2010 8:35am

    fanderson

    899 posts

    Hi Webalite, thanks for passing this along. I took a look, but unfortunately it does not help.

  • #4 / Aug 18, 2010 8:58am

    Sue Crocker

    26054 posts

    How about if you create a brand new template with just some minimal EE code in it. Does it work then?

  • #5 / Aug 18, 2010 9:01am

    fanderson

    899 posts

    Hi Sue. I was hoping you would be able to help out here. Currently I am just getting a blank screen, including the control panel. I know that something is working though because the database errors are gone.

  • #6 / Aug 18, 2010 9:08am

    Sue Crocker

    26054 posts

    Have you seen:

    http://expressionengine.com/wiki/HowTo_Turn_on_Error_Reporting/

    Let’s have you do that and see if any errors show up.

  • #7 / Aug 18, 2010 9:49am

    fanderson

    899 posts

    Alas, I am not even able to get into the control panel. I am going to do a fresh install and then see if I can rework it from there. I will be back after I try that. Thanks.

  • #8 / Aug 18, 2010 9:51am

    Sue Crocker

    26054 posts

    Sounds good to me. Let us know what happens, we’ll be here.

  • #9 / Aug 18, 2010 5:04pm

    fanderson

    899 posts

    Hi Sue, I did a fresh EE install and everything works fine, so I am more convinced than ever that something is missing with in a few documents in my attempts to breathe life into this site.

    Allow me to do a recap and then hopefully we can pinpoint where the problem is and then find a solution.

    I am moving a live EE 1.6.9 site from one host to a new host on Media Temple.

    I copied the database and imported it successfully. I downloaded all the files and uploaded them to the server. I then updated the config.php file to reflect the new database server, username and password. I know there was a connection here because I got an initial mysql error that I was able to correct.

    However, with all the correct information in place, going to the testing url, the home page and the control panel come up blank. To make sure that I had an active link I posted a generic index.html page there and it showed up fine, so I know the URL is valid.

    The site configuration leverages some unique information in the path.php file and also includes a login.php file so I am thinking that perhaps some of the customization in here may be the cause of the blank screens.

    I am unable to implement your earlier recommendation that I turn on error reporting because the control panel page does not load either.

    Are there any other steps I can take to troubleshoot this situation? I would really appreciate some guidance on this.

    Thank you,

    Forrest

  • #10 / Aug 19, 2010 3:50am

    John Henry Donovan

    12339 posts

    Forrest,

    I am unable to implement your earlier recommendation that I turn on error reporting because the control panel page does not load either.

    You don’t need to get to the control panel. That is usually turned on by default. Just do the following and try and visit your cp.

    Next, edit the /system/index.php file, and change the value of
    “error_reporting(0);”

    to
    “error_reporting(E_ALL);”

    The site configuration leverages some unique information in the path.php file and also includes a login.php file so I am thinking that perhaps some of the customization in here may be the cause of the blank screens.

    Can you share what’s in your path.php?

    Can you also run the Server Wizard on your new server please

  • #11 / Aug 19, 2010 8:34am

    fanderson

    899 posts

    Hi John, nice to see a smiling face this morning and thanks for looking into this.

    I added the error reporting and got the following error:

    Parse error: syntax error, unexpected ‘&’, expecting T_VARIABLE or ‘$’ in /nfs/c07/h03/mnt/103645/domains/nu-living.com/html/EjkbfeIt/extensions/ext.fieldframe.php on line 302

    I also ran the server wizard and everything check positive, so that is good.

    Here is what is in the path.php file:

    <?php
    
    // ------------------------------------------------------
    // DO NOT ALTER THIS FILE UNLESS YOU HAVE A REASON TO
    
    // ------------------------------------------------------
    // Path to the directory containing your backend files
    
    $system_path = "./EjkbfeIt/";
    
    // ------------------------------------------------------
    // MANUALLY CONFIGURABLE VARIABLES
    // See user guide for more information
    // ------------------------------------------------------
    
    $template_group = "";
    $template = "";
    $site_url = "";
    $cp_url = "";
    $site_index = "";
    $site_404 = "";
    $global_vars =
    array(
    $_SERVER['DOCUMENT_ROOT'] = '/home/103645/domains/nu-living.com/html'
    ); // This array must be associative
    
    ?>

    Please let me know if there is anything else I can provide. Again, I really appreciate the help.

  • #12 / Aug 19, 2010 7:13pm

    Brandon Jones

    5500 posts

    I added the error reporting and got the following error:

    Parse error: syntax error, unexpected ‘&’, expecting T_VARIABLE or ‘$’ in /nfs/c07/h03/mnt/103645/domains/nu-living.com/html/EjkbfeIt/extensions/ext.fieldframe.php on line 302

    That points to FieldFrame, a 3rd-party extension. Try disabling extensions via config.php and see if that lets you in.

  • #13 / Aug 19, 2010 7:32pm

    fanderson

    899 posts

    Brilliant! Thank you. Now I can take it from here.

  • #14 / Aug 20, 2010 7:15am

    Sue Crocker

    26054 posts

    Keep us in the loop, We’ll be here.

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

ExpressionEngine News!

#eecms, #events, #releases