• I am looking at the codex page Giving WordPress Its Own Directory. I currently have WordPress in a sub folder, and want to get it to load at the site root, without moving the installation. I’ve done this once before, but it was a long time ago, and I need to get this right the first time.

    The second section on the page, Using a pre-existing subdirectory install, gives the instructions I need. Here is my question:

    Step 5 says “Edit your root directory’s index.php.” OK, I can do that, but what is going to happen the next time WordPress is upgraded. Index.php is part of my Theme, not part of WordPress, correct? So I should be OK. But what happens when the theme gets updated? Say my client, a year down the road, updates the theme, and the site disappears. Is this a possibility? I have never had this trouble with the site I did before, but I just want to make sure. Thank you!

Viewing 2 replies - 1 through 2 (of 2 total)
  • It’s not the theme’s index file, but the index file just below the three main folders of WordPress. That you may find just below the .htaccess file. It may have this:

    <?php
    /**
     * Front to the WordPress application. This file doesn't do anything, but loads
     * wp-blog-header.php which does and tells WordPress to load the theme.
     *
     * @package WordPress
     */
    
    /**
     * Tells WordPress to load the WordPress theme and output it.
     *
     * @var bool
     */
    define('WP_USE_THEMES', true);
    
    /** Loads the WordPress Environment and Template */
    require('./wp-blog-header.php');

    Thread Starter biodrama

    (@biodrama)

    I’m glad I asked!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Giving WordPress its own Directory – Question’ is closed to new replies.