Sub directory install going live

  • domain.com is an existing website, and we are now redesigning a new WP version on the same domain

    i did a trial run of installing WP on domain.com/sub/folder and it works fine, but now i’m wondering how to hook it up when we go live and replace the existing top level site?

    current homepage is domain.com/index.php but the WP default is domain.com/SUB/index.php
    i guess we’re best with it in the /public_html/ top level, but what’s the best way to manage that when the time comes?

    i’m familiar with using .htaccess to redirect homepage if that helps?

    or maybe this

    require DIR . ‘/SUB/wp-blog-header.php’;

Viewing 4 replies - 1 through 4 (of 4 total)

  • Normally I’d just move all of the new sites files to the root directory of your hosting service and update the URL’s to set the correct URL.

    Thread Starter David Sutherland

    (@escocia1)

    but the existing site files at the top level will be remaining in place after the new sublevel site is launched, using 301 redirects to tell the search engines about the new page locations, so would there not be potential issues using your “move” into the root directory?

    Thread Starter David Sutherland

    (@escocia1)

    thinking it over, am quite happy leaving the WP core in the original subdirectory, all that’s required is for the current (old) homepage domain.com/index.php to be replaced by new domain.com/SUB/index.php homepage. What’s the best practice for this?

    Thread Starter David Sutherland

    (@escocia1)

    still no solution here? many of the new pages are going to have similar names to the old (existing) pages, e.g. /place.php, /event.php, etc. Will there not be a risk of page name conflicts? for a site with nearly 100 pages. Or is that part of the process, going through all the names and naming the new pages differently e.g. place-new.php, event-new.php etc.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Sub directory install going live’ is closed to new replies.