Problem: Using a pre-existing subdirectory install

  • Resolved thinbluesmoke

    (@thinbluesmoke)


    8 years, 6 months ago

    I had WordPress running but to access it via a browser the URL looked like; https://mywebsite.com/wordpress/ I tried to follow the instructions for moving the index.php & .htaccess files so that the base URL, https://mywebsite.com would automatically drive the user to the blog. I was following the instructions given here for using a pre-existing directory; https://codex.www.ads-software.com/Giving_WordPress_Its_Own_Directory

    I’m on a shared hosting plan which kind of convolutes the directory structure and I think I have some sort of path problem. Now when going to my site I get this warning;

    Warning: require(/usr/local/pem/vhosts/121764/webspace/httpdocs/thinbluesmoke.com/webspace/siteapps/WordPress-60594/htdocs/wp-blog-header.php): failed to open stream: No such file or directory in /usr/local/pem/vhosts/121764/webspace/httpdocs/thinbluesmoke.com/index.php on line 17 Fatal error: require(): Failed opening required ‘/usr/local/pem/vhosts/121764/webspace/httpdocs/thinbluesmoke.com/webspace/siteapps/WordPress-60594/htdocs/wp-blog-header.php’ (include_path=’.:/usr/libexec/php4-cgi/share/pear’) in /usr/local/pem/vhosts/121764/webspace/httpdocs/thinbluesmoke.com/index.php on line 17

    Here’s my index file;
    <?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( dirname( __FILE__ ) . ‘/webspace/siteapps/WordPress-60594/htdocs/wp-blog-header.php’ );

    I could use some assistance with this.

    Thanks

Viewing 3 replies - 16 through 18 (of 18 total)
  • Thread Starter thinbluesmoke

    (@thinbluesmoke)

    Ok, Before I do any further damage I think I’ll submit a support ticket to my web host to see what gives. I honestly don’t know how that URL resolves to my WordPress blog when the folder hierarchy is so convoluted. What you’re suggesting makes perfect sense to me. Thanks!

    Thread Starter thinbluesmoke

    (@thinbluesmoke)

    Ok, it looks like I’m back in business as far as the blog home page loading. I contacted my web host and they changed the URL path and my blog home page loads from the web root name; https://MySiteName.com. I have no clue where they made the change or what it was changed to but I assume it resolves to the WordPress directory.

    That part of the mission is accomplished but my one and only post won’t load when clicking the link. I remember seeing a note about this is the instructions for changing the web root location. I’ll see what I can do and if I have any further issues I’ll create a new topic here at the forum.

    Thanks Mark for riding this one out with me.

    I’m having a similar problem. I had a version of my site running at root (jliacademy.org), and a newer wp version running from a subdirectory (jliacademy.org/wp). I followed directions for getting the wp site to run from the root (changed wp site general setting, copied-not-moved .htaccess and index.php to root, edited index.php).

    Nothing changed. So I renamed my original index.html to index.old. The old site disappeared, but I got a “site not working” error instead of the wp site. So I restored my original index.html, getting old site back on line.

    Now when I try to reach wp site, or wp-admin I get the “site not working” error. I suppose that’s because my general settings have changed?

    So, how do I proceed now? I want to run the new wp site, not the original site. Do I need to clear all of the old site out of the root? Something else? I also want to reach wp-admin. How do I do that? Do I need to edit some wp files outside of the dashboard?

    Please help.

Viewing 3 replies - 16 through 18 (of 18 total)
  • The topic ‘Problem: Using a pre-existing subdirectory install’ is closed to new replies.