• I installed wordpress in its own folder so on root its /wordpress/

    I created all the pages and tested before going live. I changed the .htaccess to point to the new directory but when I entered the domain it resolved to mydomain/wordpress/

    I tried a few variations of the .htaccess from both Bluehost and the WP site below, but it still does not resolve to just mydomain going to WP root index.

    Giving WordPress Its Own Directory

    I also had a go at changing the Settings > General URL path. I then contacted Bluehost support and surprisingly they couldn’t fix it. I’ve no idea what the issue is as I thought it was fairly straight forward.

    What controls the domain pointing to the /wordpress/ directory? The root htaccess file or some setting within wordpress settings or both?

Viewing 7 replies - 1 through 7 (of 7 total)
  • > I then contacted Bluehost support and surprisingly they couldn’t fix it

    I assume this is sarcasm?????

    If it were me, the path of least resistance is to just install WordPress at the root, and then migrate using a migration plugin like this:
    https://en-ca.wordpress.org/plugins/all-in-one-wp-migration/

    Super easy, and should take 5 minutes.

    Otherwise, you’ll need to edit the sitehome and siteurl values in the _options table of your database.
    https://www.wpbeginner.com/wp-tutorials/how-to-change-your-wordpress-site-urls-step-by-step/

    Hi @vitualbob

    Sorry to hear about the ongoing troubles with resolving your domain from the root to the subfolder. I can only imagine how frustrating it would be to not be able to find a fix for this. I’d be happy to take a look at this and see how I can support you.

    Just to make sure that we are on the same page here – you are trying to keep your domain to keep pointing to: https://mydomain while your WordPress install lives in: https://mydomain/wordpress – did I get that right?

    From your steps, it looks like you missed a step or two. I’m not sure if you have done this already, but can you try all steps in Method 2. Make sure that you create a copy of the index.php file and place it in the root URL as mentioned in the instructions (Step 8 and 9). Can you try those steps and see if this helps?

    Feel free to take a look at the following article as well, which offers some more guidance: https://wpmudev.com/blog/install-wordpress-subdirectory/

    I hope this helps. Let us know if you are still running into troubles.

    Thread Starter VitualBob

    (@vitualbob)

    I couldn’t get it to work as the inlcudes worked but the page bodies were missing with errors. The original support pages I was trying to follow were a mess – poorly written and it was difficult to know which option to follow. But when I did work it out there was still errors. But I’m not using /wordpress/ any more, but it shouldn’t be this difficult.

    Bluehost really don’t know the way to do it properly so one support person broke the site and the other just copied it to root. There are still a lot of mysite/wordpress/ links on the site but somehow they are not breaking anything. No idea why as /wordpress/ is now empty and the URL in the general panel are both just mysite.

    Which is exactly why I suggested a migration tool. It take minutes.

    At this point, if you just need to update links in the site from oldurl –> newurl, just use this:
    https://en-ca.wordpress.org/plugins/better-search-replace/
    or this:
    https://interconnectit.com/search-and-replace-for-wordpress-databases/

    Thread Starter VitualBob

    (@vitualbob)

    Before I start changing anything I need to know why so many links containing /wordpress/ are being resolved to root on the fly and not causing issue. What change was implemented to do this? Where do I look? Some resolve correctly and some don’t. I don’t want to do a global replace and find I’ve broken everything.

    I need to know why so many links containing /wordpress/ are being resolved to root on the fly and not causing issue. What change was implemented to do this? Where do I look?

    @vitualbob if you are expecting detailed respsones to these questions, you are not sharing even close to enough information. At minimum, you would need to share the URL of your site, and outline all the process and action you have done to date.

    Otherwise – just make a backup, and implement what has been already suggested.
    It’s exceedingly straight-forward. You could have had this fixed in less time than we have already taken to discuss it on the Forums.

    Thread Starter VitualBob

    (@vitualbob)

    I didn’t do anything. The Bluehost guy changed stuff and I’m trying to work out what he did. I’m going to copy it back to another directory and play around with. Don’t want to mess with a live site.

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

The topic ‘URL not resolving to subdirectory’ is closed to new replies.