By default, WordPress now installs to a single “wp” directory.
WordPress installs wherever you upload the files. Your host may have a script that puts it in a wp folder.
This plugin is written, expecting the three separate “wp-…” directories at the root and not within a single “wp” directory.
Domain Mapping only works when the main site URL is located in the root of the website. The limitation is in this plugin because it’s not possible to set up DNS for a domain and folder.
True, the specifics of installation are up to the user during any manual install and even so using my scripted install. I oversimplified for the most popular among distribution scripts.
The message I received specifically referenced the WordPress installation directory (“/wp/”) and seemed to have nothing to do with the site itself. Are you familiar with that particular type of message? Or, should I reinstall it to get the exact message?
Are you familiar with that particular type of message?
Yes, the message is intentional. Per my previous response:
The limitation is in this plugin because it’s not possible to set up DNS for a domain and folder.
Again, it had nothing to do with the website. I’m not positive, but I don’t even think I got far enough into this plugin to configure it for a website, root or not. The message complained about WordPress not being installed at the root.
@dlburkhart – What I am trying to explain to you is that the domain mapping plugin prevents you from setting the plugin up in an install where it is impossible for the plugin to work.
To reiterate – you cannot set up DNS for a domain and path. When someone clicks a link like http://example.com/some/path/ their web browser first makes a call to DNS servers to look up example.com. Once the browser receives a result (ex. IP address 12.34.56.78) it then sends the http://example.com/some/path/ request to 12.34.56.78.
I realize that. And, I am familiar with the way domains are translated.
One of my websites is at the root. And, if I wanted to use the plugin for that site, it wouldn’t help. Because, whenever I try to configure the plugin, I would still get the error message that WordPress is not installed at the root.
To be clear:
- I have a website at the root
- I have WordPress not directly at the root
- I installed this plugin
- I try to configure this plugin
- I immediately get an error message (with nothing set yet)
