I have site.com , es.site.com
in the site.com i want to make a page with url writen as site.com/doc, but its also visible in es.site/doc, how can i make a diferent doc for each subdomain?
I have site.com , es.site.com
in the site.com i want to make a page with url writen as site.com/doc, but its also visible in es.site/doc, how can i make a diferent doc for each subdomain?
Comments
Comment #1
agentrickardI am not sure I fully understand the question.
One option is to use Domain Prefix to create different {url_alias} tables for each domain. That would give you domain-specific path lookups.
Comment #2
bforchhammer commentedIf I understand peregrina correctly he would like to have something we could call "multilingual" domains...? That would be something I'm looking for as well...
My Situation is the following:
I would like to use the domain module to decide which content (menu, page title, nodes, etc.) to display on each domain (because they e.g. share some nodes), and at the same time I would like to use subdomains (en.one.com, en.two.com, de.three.com, ...) to decide which language to display the content and interface in.
So if I call en.one.com or de.one.com or just one.com I would like to have the same site configuration (title, header, footer, theme, tables, menus etc.) for all of them, just as if they were one single domain record in the domain access module. But if I call en.one.com I would also like an english interface language and english content...
I figured that I could probably use the table prefix module and prefix the languages table in the database, but the domain module wouldn't recognise en.one.com as the domain entry for the first affiliate, so that doesn't quite work yet.
Maybe we can widen the domain name matching part of the domain access module somehow... by adding a placeholder (*.one.com), defining synonyms or "further domains" for one affiliate entry or introduce a new option which automatically also recognises subdomains if the domain name doesn't already contain one...?
Any other ideas or comments? I'm probably going to implement some solution to this problem, but I'd hate doing it "the wrong way"...
Comment #3
bforchhammer commentedI looked into it a bit more, see: #276303: Domain bootstrap patch
@peregrina: sorry for hijacking this issue; I can confirm that agentrickard's suggestion to prefix the {url_alias} table works in terms of creating the same path for different domains.
Comment #4
agentrickardComment #5
agentrickard