Shared User Base

Permalink Browser Info Environment
I've been tasked to develop a site/sites for a number of promotional campaigns and a central hub to organize them.

Each campaign will likely have its own URL, but the reason I'm considering the domain mapper is the user base. If a user changes their password or custom attributes on one campaign site, the change must be reflected on the other sites.

It'd be nice if there was a way to maintain logins between domains too, but that's not a deal breaker. Any ideas?

I would also like to clarify how the URLs of the child pages work. If I'm on campaign1.com (a mapped domain) and I go to the about us page, will the URL be campaign1.com/campaign1/about-us?

Type: Discussion
Status: New
PerryGovier
View Replies:
ryan replied on at Permalink Reply
ryan
Yes, With the domain mapper you'll have one site, one database, but maintaining session state - logged in on one domain, then you go to the other domain and your still logged in would be problematic. You could get fancy if you were using subdomains (site1.test.com, site2.test.com), but using separate domains wouldn't work, you'd have to log in on each domain.

As far as the urls go, you're correct. When you first go to the mapped domain campaign1.com you'd see:http://campaign1.com in the address bar. clicking about us would showhttp://campaign1.com/campaign1/about-us... in the address bar.

Another thing that's helpful to know about is concrete's config/site_theme_paths.php configuration file. That'll allow you to set different themes for each branch of the tree without having to specify them when you create each page.

concrete5 Environment Information

Browser User-Agent String

Hide Post Content

This will replace the post content with the message: "Content has been removed by an Administrator"

Hide Content

Request Refund

You have not specified a license for this support ticket. You must have a valid license assigned to a support ticket to request a refund.