Moving Subdirectory Install To Root, Where 'Site address (URL)' Already Resides

  • Resolved joe miller

    (@iamburnsy)


    9 years, 2 months ago

    Probably not stated right, but here it is in more detail:

    The blog currently exists with the index.php and htaccess files in the root, while the rest resides in a sub-directory as per the instructions for Using a pre-existing subdirectory install.

    But now I need to have the whole thing reside in the root, so moving all the files into the root along with index.php and htaccess.

    I’m sure it’s not as simple as just moving all the files into the root (where index.php and htaccess already reside) and changing the “WordPress address (URL)” to reflect the root directory.

    Are there any step-by-step instructions on how to do this? I’ve searched but can’t see this particular scenario presented anywhere in the Forums …

Viewing 7 replies - 1 through 7 (of 7 total)
  • Moderator James Huff

    (@macmanx)

    Follow this guide: https://codex.www.ads-software.com/Moving_WordPress#Moving_Directories_On_Your_Existing_Server

    You’ll also need to undo the changes you made to the root index.php file, specifically this line:

    require( dirname( __FILE__ ) . '/wp-blog-header.php' );

    So that it reflects the new location of wp-blog-header.php relative to index.php.

    Thread Starter joe miller

    (@iamburnsy)

    Thanks for your help James, this seems fairly straightforward.

    As for the index.php, the original one is in the sub-directory with all the original core files, so I’m assuming I can just move all the contents of that folder into the Root, after changing the WordPress/Site URL’s in Admin/Settings/General ..

    The modified index.php and the htaccess file currently in the Root will be overwritten (although I’ve backed them up).

    The only real issue I’m bracing for will be the broken links for the uploaded images, but I will try using the plugin Better Search Replace as referenced in the article … unless there’s a more recommended/preferred one.

    Moderator James Huff

    (@macmanx)

    Yep, that should all work. ??

    Thread Starter joe miller

    (@iamburnsy)

    Hmmm … looks like I’ve hit a snag.

    When trying to log back in, it looks like a Plugin is interfering, because I get these Warning messages, and I can’t log in ..

    Warning: include(wpdm-core.php) [function.include]: failed to open stream: No such file or directory in /yadda/yadda/html/wp-content/plugins/download-manager/download-manager.php on line 102

    Warning: include() [function.include]: Failed opening ‘wpdm-core.php’ for inclusion (include_path=’.:/usr/local/php5/lib/php’) in /yadda/yadda/html/wp-content/plugins/download-manager/download-manager.php on line 102

    Warning: Cannot modify header information – headers already sent by (output started at /yadda/yadda/html/wp-content/plugins/download-manager/download-manager.php:102) in /yadda/yadda/html/wp-login.php on line 431

    Warning: Cannot modify header information – headers already sent by (output started at /yadda/yadda/html/wp-content/plugins/download-manager/download-manager.php:102) in /yadda/yadda/html/wp-login.php on line 444

    etc .. etc ..

    I replaced the download-manager.php with a backup, in fact replaced the whole plugin folder with a backup, but no change, and there’s not anything on ‘Line 102’ of that file, so now I’m not sure what to do.

    Moderator James Huff

    (@macmanx)

    Try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, access your server via FTP or SFTP, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue (theme functions can interfere like plugins).

    Thread Starter joe miller

    (@iamburnsy)

    Thanks for all your help !

    I didn’t actually need to do the reset options you suggested, because after examining more closely it turned out the ‘core” file for the Download Manager plugin [referenced in the 1st Warning] wasn’t appearing on the server via FTP even after multiple attempts and different FTP programs. It wasn’t until I used the Hosting Accnt’s File Manager to place it that the problem was resolved.

    Moderator James Huff

    (@macmanx)

    You’re welcome!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Moving Subdirectory Install To Root, Where 'Site address (URL)' Already Resides’ is closed to new replies.