Like many users, I was intrigued by the cross-domain cookie features of the Domain Mapping plug-in, but found it didn't do quite what I had hoped. See previous thread:
Starting a fresh thread just in order to take a different angle. Here's the usage scenario: we have a blog network with domain network.com. Two blogs come along, one with domain1.com, another with domain2.com.
Currently, you can do this:
Login to domain1.com, and you're logged into network.com.
But you can't do this:
Log into network.com, and you're logged into domain.com OR
Log into domain1.com, and you're logged into domain2.com.
First, I want to make sure I've set this up correctly -- this is the behavior to expect, yes?
Second, given the first scenario works, what's to stop that from being applied elsewhere, even if we had to work on a way of manually tracking the domains / creating more cookies?
Let's assume that it doesn't work for *all* domains on a site, but that you had three domains for which you did want it to work?
Also, I've encountered another problem. One site I have has subdomain.network.com as its original blog address, so it works correctly. But another has domain2.com as both its "custom" and "original" domain, so it doesn't do any of the cross-domain magic (not even the first scenario). Do I need to change that in the database?