Thread Starter
T3Kaos
(@t3kaos)
By the way for additional info, this was done as a fresh install, not a 1-Click Install. Also I noticed that no new directory was created for the blog inside of the blogs.dir folder. The permissions are already set as correct for the folder.
I checked the dbase for the site (uknexttopmodel.com) and found that the following tables had been created for the test subsite;
>wp_2_commentmeta
>wp_2_comments
>wp_2_links
>wp_2_options
>wp_2_postmeta
>wp_2_posts
>wp_2_terms
>wp_2_term_relationships
>wp_2_term_taxonomy
However if you visit http://test.uknexttopmodel.com/wp-admin.php you get a Error 404 problem. What do I do?
Thread Starter
T3Kaos
(@t3kaos)
In a further addition I managed to get the /blogs directory listing problem to work now – so I’m just still stuck with not being able to access the dashboard for the test subsite 🙁
The URL is http://test.uknexttopmodel.com/wp-admin/ but that’s not working either.
Did you create a physical folder named ‘test’ on your server? (You should NOT, I’m asking if you DID).
You may need to check if AllowOverride is set to ALL on your httpd.conf
Thread Starter
T3Kaos
(@t3kaos)
Nope, didn’t create a physical folder whatsoever. I will check to ensure AllowOverride is set to all on the httpd.conf (whereever the hell that is – lolz)
Thread Starter
T3Kaos
(@t3kaos)
I have set AllowOverride to All
#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be “All”, “None”, or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride All
Is this correct?
Thread Starter
T3Kaos
(@t3kaos)
Should the http://test.uknexttopmodel.com/wp-admin/ just work straight away, or should I:
a) perform a server restart?
b) create new test subsite?
c) or combination of both?
It should work right away.
That it’s NOT means one of two things.
1) Subdomains aren’t set up right (which I’m inclined to think, since http://test.uknexttopmodel.com/ is a setup page and NOT WordPress)
2) .htaccess is buggered.
I think it’s #1. WordPress should be parsing ALL your subdomains, if wildcards are set up right. The subdomains should all point to /public_html (or whatever you have) and a non extant subdomain will look like http://jkhdfkjhsdfdkjf.ipstenu.org
Thread Starter
T3Kaos
(@t3kaos)
How do I check the first one? Especially on a 1and1 Dedicated Server running CentOS 5?
Thread Starter
T3Kaos
(@t3kaos)
I contacted 1and1 and the reason for the incorrect forwarding is because that domain is using a shared IP address.
So for example if you throw a random sub-domain in front of my z01.co.uk domain, ergo: test.z01.co.uk, it will instantly bounce to the z01.co.uk site because that is a dedicated IP address and is set to have z01.co.uk as the default address point.
Does anyone know of a way around this?
Try MANUALLY mapping the subdomain. That is, create a subdomain for TEST and then point it to /public_html (I’m not 100% remembering how that works with 1&1). You’ll have to make the subdomain manually every time, but it can be done.
Thread Starter
T3Kaos
(@t3kaos)
Basically in this instance you’d be better off with subfolders then. Interesting.
Thread Starter
T3Kaos
(@t3kaos)
Thanks guys. I must say this new build of WordPress is definitely the best by far!
I contacted 1and1 and the reason for the incorrect forwarding is because that domain is using a shared IP address.
So for example if you throw a random sub-domain in front of my z01.co.uk domain, ergo: test.z01.co.uk, it will instantly bounce to the z01.co.uk site because that is a dedicated IP address and is set to have z01.co.uk as the default address point.
Does anyone know of a way around this?
So basically they would not tell you how to add *.z01.co.uk as a ServerAlias.
