mandrill

Thanks. I may have a poke around with RC4 in addition to building my site on 3.0.5 and see how it fares 🙂

Scratch above. It was the Domain, Path and SiteURL settings causing the issue. The combination of the following gives me access to the directory listing of the directory mapped to the subdomain:

Domain: subdom.fakedom.kn
Path: /
Siteurl: http://subdom.fakedom.kn/

Further poking in the vhosts file resolved this and blog is now displaying on subdom.fakedom.kn and the main blog on fakedom.kn

All subdomains in the vhosts file should be mapped to the root directory of the main domain and not their own directories.

as follows:

<VirtualHost *:80>
    ServerName subdom.fakedom.kn
    DocumentRoot "C:/xampp/htdocs/"

   #DirectoryIndex index.php

    <Directory "C:/xampp/htdocs/">
        Options Indexes FollowSymLinks Includes ExecCGI
        AllowOverride All
        Order allow,deny
        Allow from all
    </Directory>
</VirtualHost>

it all seems to be working correctly now and I can access the backends of each blog through a single user.

You can probably chalk this one up as being resolved. Might be worth mentioning to people that if they want to run subdomains on localhost they should set up a fake domain (subdom.fakedom.tld) rather than use subdom.localhost as I think thats where my original issue sprang from.

Thank you both for your help. 😀

WordPress installed and working correctly.

Subdomains displaying correct files and not the wordpress blog on root directory. localhost and testing domain work identically.

Installing network through testing domain rather than localhost.

Installing through differently named local domain actually gives me the option to choose either subdirs or subdoms. Whereas installing via the localhost domain forces the settings for subdirs and doesn’t give you the option to change them.

Network is installed, no blogs are added to it as yet tho, and I’m having no issues logging in and out as normal.

Have reinstalled WordPress and am running a single site without any problems. I can log in and out without any difficulty.

However, upon rechecking that my subdomains are indeed working as expected I have found another issue. I have not changed the vhosts settings since the first time I tried it and it seemed to work. Now however instead of displaying the index.html of the directories the subdomains are mapped to they all display the front page of my blog.

This is an example of the settings I have in the vhosts.conf which has not changed since I first got it working:

<VirtualHost *:80>
    ServerAdmin postmaster@eve.localhost
    DocumentRoot "C:/xampp/xampp/htdocs/"
    ServerName eve.localhost
    ServerAlias www.eve.localhost
    ErrorLog "logs/eve.localhost-error.log"
    CustomLog "logs/eve.localhost-access.log" combined
	<Directory "C:/xampp/xampp/htdocs/">
		AllowOverride All
		Allow from All
	</Directory>
</VirtualHost>

As to manually removing the cookies. I can’t find any indication of how to do this with chrome. Every page I look at simply says “open the options dialogue and push the button.” The only reference to cookies for Chrome that I can find is in the C:\Documents and Settings\Owner\Local Settings\Application Data\Google\Chrome\User Data\Default folder and its just a single file there is no indication that the cookies are stored individually anywhere. IE and Firefox are set to delete their cookies upon shutdown as I only use them for testing. I have ensured that this is in fact happening.

I have not attempted to install the network again, I’m going to try and figure out the subdomains problem first and ensure that it is working as it should before I do.

most perplexing :/

I had my local apache set up to do all that, and it /was/ working before I ran into this login loop problem.

My original setup, before I hit the login loop on even the admin account to get into the network dashboard, and the basis of the original question of this thread, was getting each blog in the network to recognise the super admin account as an administrator of the individual blogs. basically so I could post and change the settings of each individual blog with one account. I was originally hitting the login loop when trying to login to the backend of each blog with the super admin account but after a second clearing of cache and cookies it stopped letting me into even the super admin dashboard.

Each blog on the network was using its own subdom.localhost successfully, however since I’ve reinstalled wp a couple of times since then and kept hitting the login loop when trying to login to the superadmin dashboard. So I haven’t been able to set up the blogs again to test if all the subdomain settings (in vhosts etc.) are working correctly.

I’m not sure what you mean by ‘funky chicken’ suggestions I followed the advice of this thread if thats any help.

The whole thing has been tested multiple times in IE, chrome, and Firefox with the same results every time.

Doing a bit of digging I have discovered that there are no cookies being set for my local wp installation. could this be an issue? I have allowed cookies in all my browser’s settings but chrome seems to think that none are being set.

from reading through this trac page http://core.trac.wordpress.org/ticket/12142
I’m getting the feeling that this may be a cookie issue.

the redirect_to and &reauth=1 added to the URI when logging in is, from what I can gather, only added if the login script can’t find a valid cookie. If I have no cookies and its not storing any its never going to find a valid cookie and so begins the loop. Does that sound about right?

Am I missing a setting somewhere in the config telling it to store a cookie?