I created a subdomain and pointed it to that folder at…
Don’t do that. Do NOT redirect the subdomain anywhere. Just create it and install WP in/on it. It should work.
Also, read the release notes about the canonical urls introduced in 2.3.x (top of this page > Blog)
Don’t do that. Do NOT redirect the subdomain anywhere. Just create it and install WP in/on it. It should work.
I’ve tried this and I still get the same error. Even with placing WP in the auto-created subdomain (not the pointed one) it boots me back to the main page. I had to use the plugin that disables canonical redirects to get it to work.
I am getting the exact same problem, but for me this occurred when I upgraded WordPress from 2.0.2 to 2.3.2. My blog can be found at the following location:
http://avelient.com/BioPharmBlog
I had set up a subdomain for the blog:
http://bpblog.avelient.com
And everything was fine and dandy under version 2.0.2. When I upgraded to version 2.3.2, I am suddenly no longer able to access the blog through the subdomain (I am redirected to the main site, avelient.com). As in the original thread, my service provider and I both threw in test files which are accessible through the subdomain and we’re able to reach them without a problem.
Here’s another point that I’ll add to the mix. I use the “Maintenance Mode” plugin provided by Software Guide now when I’m making modifications to the look of the site. When maintenance mode is activated and I use a browser where I am *not* logged on as an administrator, my subdomain correctly shows the maintenance page.
The theme does not seem to make a difference, I’ve noticed the same problem using the default WordPress Theme, Fauna, and Elite Circle.
I am really happy with the features in 2.3.2, and would prefer not to downgrade if that’s possible. If I can provide any more information, please let me know.
Actually, as an update I too disabled canonical URL redirection and it appears to have corrected the problem. Is it simply that canonical URL redirection and subdomains can’t coexist peacefully? Or is there perhaps something in the configuration of the subdomain that’s not correct? I’m fairly certain the latter isn’t true; but would welcome any information you might have.
