• Hi,

    I’ve installed WordPress in its own directory (called efc) in the root directory(public_html folder)of my host server. In other words, it is similar to a sub-domain within my main domain, except that it isn’t an actual domain with a real domain name. I’m just building a WordPress site that will be transferred to the clients host server and domain in the future.

    What I want to do is have the url display as https://www.example.com instead of example.com/efc. I already have an index.php file in the root directory (my domain). So, I can’t copy the index.php file (and .htaccess file) from the WP(efc)folder putting it in the root to change the file path so I’ll get the clean url I want.

    I’m not sure this can even be done. The only way I can think of is using a (PHP) http 302 redirect in the top of my default index.php file. I’m a newbie at PHP (and WP for that matter) so I’d have to figure out the code.

    Anyway, suggestions, ideas appreciated.

Viewing 2 replies - 1 through 2 (of 2 total)
  • …similar to a sub-domain within my main domain, except that it isn’t an actual domain with a real domain name…

    https://www.example.com/

    I’m not sure this can even be done.

    I suspect not since there would be no DNS for https://www.example.com, but if you had an https://www.clientworks.com add-on domain of your own (as such would be called at BlueHost where I have a primary and three completely-independent add-ons with each in their respective folders) to use for any current project, I believe you could point that name to the project and then later move the finished product to its final destination and let Dashboard > Settings > General handle the switch to the client’s domain name.

    Thread Starter sonofadoc

    (@sonofadoc)

    That’s an excellent suggestion. I don’t know why I didn’t think of it. I believe I still have a parked add-on domain or two left that I didn’t let expire. I could just put the WP files in a folder named “my add-on domain” and that would work.

    So simple, thanks for your suggestion.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Installing WordPress in it's own directory’ is closed to new replies.