From: "Will Scheidegger" <user-list@magnolia.info>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Sender: willscheidegger@mac.com
Message-id: <10D69DD0-F96F-4150-BEF4-9DC6757B74E1@mac.com>
To: user-list@magnolia.info
In-reply-to: <list-14579516@mail.obinary.com>
Content-transfer-encoding: quoted-printable
Subject: Re: [magnolia-user] PUR for multi domain setup
Date: Wed, 23 Jul 2008 12:21:37 +0200
References: <list-14579516@mail.obinary.com>

On 23.07.2008, at 12:05, Gr=E9gory Joseph wrote:

> Yeah, that is a similar approach we've taken for the new cache =20
> configuration - you can have multiple cache configs, and the cache =20
> filter is configured to use the appropriate one.

Ah, interesting. I'll have a look at how you've done things there.

> But you'll have to think about handling of duplicates etc. What if =20
> the *same person* wants to register on siteX and siteY, how do you =20
> handle that ? (because as it, it will just be rejected, saying this =20=

> user already exists, while what you want is probably add some roles =20=

> or groups to it)

Well, if the sites are related (and therefore user accounts should be =20=

"shared") then one could really solve this via roles/groups (e.g. the =20=

"Apple ID" which might be valid for bugreport.apple.com as well as for =20=

the Apple Store or .Mac). If the sites are not related at all I don't =20=

see a problem in showing a "username already taken" error message.

> Also: defaultBaseUrl is what it says it is - if you add this in =20
> public-user-registration config it, you'll have to rename it. But at =20=

> that point, you'll probably want different emails anyway, so you =20
> could just as well hardcode it in the email.

Right, but you would at least want to specify different mail templates =20=

depending on the site and language.

Will=