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.

Renaming index.php not working - additional troubleshooting steps?

August 01, 2010 6:09pm

Subscribe [0]
  • #1 / Aug 01, 2010 6:09pm

    Lesli

    92 posts

    Hi all,

    I’ve had A Week. Network techs upgraded some software, broke EE, I fresh-installed and began manually moving my sites over, they had to tweak and recompile again because I couldn’t send out emails, and EE broke again.

    I’m running EE 1.6.9 build 20100415. Server environment: CentOS, Apache 2.0.63, PHP version 5.2.9, MySQL 4.1.22, PHP running as CGI, PHPsuexec.

    Now EE 1.6.9 is working…all except for one aspect. I cannot rename the index.php file to anything else - like MMU or i-still (or even plain index, with no .php extension). I’d like some help figuring out all possible troubleshooting steps.

    I am successfully running multiple sites off of this installation, using the “oldschool” method of defining the variables in the path.php files: http://www.sparklecrackcentral.com and http://www.beautyblogsbackstage.com There’s another site, http://www.cynicsteaparty.com , that’s running off of the same installation. The only difference is that that site is trying to use a renamed index.php. This problem shows up whether I’m running a single site or multiple sites off of this installation.

    I’m currently using the following code in my .htaccess file:

    <Files i-still>
    SetHandler application/x-httpd-php
    </Files>
    
    DirectoryIndex i-still index.php

    Path to this site’s index files (partially obscured / misnamed for security reasons) is

    /home/USR/public_html/cynicsteaparty/.htaccess
    /home/USR/public_html/cynicsteaparty/path.php
    /home/USR/public_html/cynicsteaparty/i-still

    This domain’s doc-root is a peer to the sites for sparklecrackcentral.com and beautyblogsbackstage.com:

    sparklecrackcentral.com paths/document root:
    /home/USR/public_html/sparklecrackcentral/.htaccess
    /home/USR/public_html/sparklecrackcentral/path.php
    /home/USR/public_html/sparklecrackcentral/index.php

    beautyblogsbackstage.com paths/document root:
    /home/USR/public_html/beautyblogsbackstage/.htaccess
    /home/USR/public_html/beautyblogsbackstage/path.php
    /home/USR/public_html/beautyblogsbackstage/index.php

    And in the .htaccess and path.php files for the latter two domains, the site’s index file is defined as index.php. The latter two domains work, while cynicsteaparty.com doesn’t. The only difference is the name / definition of the site index file.

    I’ve tried changing the SetHandler declaration to ForceType, and that didn’t work.

    What else can I try?

  • #2 / Aug 01, 2010 6:14pm

    Lesli

    92 posts

    Forgot to add:

    The control panel for this install is on the parent domain of all three of those domains. It’s parked at

    /home/USR/public_html/cms/

    I am running the default site off of that top-level site, and same thing happens: when I try to rename that index.php file to anything else, it turns up its toes and dies. So this problem won’t disappear if I only ran one single site, on the same domain as the control panel installation.

  • #3 / Aug 01, 2010 6:30pm

    Lisa Wess

    20502 posts

    Hi, Lesli -

    See the Legacy Docs on renaming the main site file - there are a few other methods of handling this, could you see if any of those work for you?

    I’d give the first example a shot and see if that helps.

  • #4 / Aug 01, 2010 6:41pm

    Lesli

    92 posts

    Hi Lisa,

    The Apache 2.x code

    <Files i-still>
    AcceptPathInfo on
    SetOutputFilter PHP
    SetInputFilter PHP
    </Files>

    just makes the code itself display. Same with the SetHandler and ForceType options (I tried everything, just to see if they worked.)

    I also tried changing the file properties for i-still from 644 to 755. Both options displayed the code of the index.php file itself.

  • #5 / Aug 01, 2010 7:01pm

    Lisa Wess

    20502 posts

    Makes the code itself display - as in the PHP code when you go to view your site?

    If none of those methods are working, they may be disabled on the server.  I hate to send you back to your host, as I know you’re already working with them - but this is ultimately a server-side change, and we’re limited in our ability to troubleshoot it.  Your host/admin has much more access to have a look at this and find out what is going on.

  • #6 / Aug 01, 2010 7:04pm

    Lesli

    92 posts

    Yep - the PHP code of the index.php file itself displayed. Partial view of what I saw:

    <?php
    /*
    =====================================================
     ExpressionEngine - by EllisLab
    -----------------------------------------------------
     <a href="http://expressionengine.com/">http://expressionengine.com/</a>
    -----------------------------------------------------
     Copyright (c) 2003 - 2010 EllisLab, Inc.
    =====================================================
     THIS IS COPYRIGHTED SOFTWARE
     PLEASE READ THE LICENSE AGREEMENT
     <a href="http://expressionengine.com/docs/license.html">http://expressionengine.com/docs/license.html</a>
    =====================================================
     File: index.php
    -----------------------------------------------------
     Purpose: Triggers the main engine
    =====================================================
    */
    
    // URI Type
    // This variable allows you to hard-code the URI type.
    // For most servers, 0 works fine.
    // 0 = auto  
    // 1 = path_info  
    // 2 = query_string
    
    $qtype = 0; 
    
    
    // DO NOT EDIT BELOW THIS!!!

    I came back here for troubleshooting help to make sure that I’d tried everything. I’d seen this page in my local documentation, but thought that I might have missed something in the documentation (or someone else would have insight as to why it didn’t work.) I’ll go work with my server provider and get them to figure this out.

  • #7 / Aug 01, 2010 7:09pm

    Lisa Wess

    20502 posts

    Thanks Lesli.  I’m sorry I couldn’t help out more.

    I’m going to keep this open - when you do figure this out, would you let us know the solution, please?  I’ve rarely seen this fail so would love to know to help others in the few cases it might come up.

    Thanks!

  • #8 / Aug 01, 2010 7:27pm

    Lesli

    92 posts

    We got it (in case anyone else has this problem.) The solution was a variation of the SetHandler option:

    <Files mynewindex>
    SetHandler application/x-httpd-php5
    </Files>

    So in case anyone else has this problem…there’s something else to try.

  • #9 / Aug 01, 2010 7:29pm

    Lisa Wess

    20502 posts

    That was fast! Thanks for updating us, Lesli, and glad you got this fixed up.

    If anything else comes up, please don’t hesitate to start a new thread.

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

ExpressionEngine News!

#eecms, #events, #releases