Sitemap of two sites using Domain Mapper
Permalink 1 user found helpful
My customer want's to have slightly different looking sites for two different domains (companies) and some pages need to share some common images and information. Domain Mapper seems to be the way, but I'd like to know the best practice for this. The biggest question is the sitemap (simplified):
Is this ok? I'd rather not use the root (First domains home) as the default page, but is there other way? The root must be always the front page, right?
Just wanted to ask before purchasing the Domain Mapper.
First domains home |-- Services |-- About Us `- Second domains home |-- Services `-- About Us
Is this ok? I'd rather not use the root (First domains home) as the default page, but is there other way? The root must be always the front page, right?
Just wanted to ask before purchasing the Domain Mapper.
Thanks for your answer, but how do you exactly hide the root? Can it be done without Domain Mapper?
Navigations, page lists etc. are not problem, as I have excluded them already from Dashboard/Sitemap/Home. Only problem is that at the moment, when user comes to examplesite1.com, he gets the root page.
Navigations, page lists etc. are not problem, as I have excluded them already from Dashboard/Sitemap/Home. Only problem is that at the moment, when user comes to examplesite1.com, he gets the root page.
simplest way would be to use the domain mapper for both sites, have a 3rd domain for the wrapper instance.
Maybe that's the simplest way, but 3rd domain is not needed or wanted for this site. If I've understand correct, with Domain Mapper and wrapperdomain I'd get urls like these:
wrapperurl.com/site1/about (not good)
site2domain.com/site2/about (not good)
site2domain.com/site1/about (NO!)
All I need is
site1domain.com/about
site2domain.com/about
If Domain Mapper just allowed this, I'd purchase it right away. If not, can this be done with mod_rewrite?
wrapperurl.com/site1/about (not good)
site2domain.com/site2/about (not good)
site2domain.com/site1/about (NO!)
All I need is
site1domain.com/about
site2domain.com/about
If Domain Mapper just allowed this, I'd purchase it right away. If not, can this be done with mod_rewrite?
We need exactly what orsinal is asking. Can anyone respond to this?
The use case is, we want one C5 instance for a multinational company with localized sites being translated and local content for every country in Europe.
companyname.eu (can go to a wrapper page)
companyname.co.uk (goes to EN content)
companyname.de (goes to DE content)
etc, etc
We don't want 50+ C5 instances to manage.
Can C5 support this with the Domain Mapper?
I'd expect this to be an normal internationalization feature of any CMS.
Also the sitemap.xml generated links must use the domain being accessed not the original domain.
The use case is, we want one C5 instance for a multinational company with localized sites being translated and local content for every country in Europe.
companyname.eu (can go to a wrapper page)
companyname.co.uk (goes to EN content)
companyname.de (goes to DE content)
etc, etc
We don't want 50+ C5 instances to manage.
Can C5 support this with the Domain Mapper?
I'd expect this to be an normal internationalization feature of any CMS.
Also the sitemap.xml generated links must use the domain being accessed not the original domain.
Yes to everything but the sitemap.xml question, which will list all links using the root domain.
Can someone answer this guy's question? I'm having the same thoughts.
Hello alseageo! I purchased the Domain Mapper pretty soon after these questions here. I'm not perfectly happy with the DM and how it handles urls, but after some struggling with navigations I got okayish result that filled the requirements for the project.
If I remember right the biggest problem was to not find myself from urls like site2domain.com/site1/
As Autonav block doesn't respect different domains in DM, your navigation tries to always use the domain where you currently are (relative address, not absolute). For cross linking these domains I had to exclude the home page of Site 2 from navigation and use external link for it's homepage, using absolute url with domain.
As I said, I got okayish result and client didn't complain. BUT if anyone knows better practice or thinks that I've misused DM somehow, please tell me. :)
If I remember right the biggest problem was to not find myself from urls like site2domain.com/site1/
As Autonav block doesn't respect different domains in DM, your navigation tries to always use the domain where you currently are (relative address, not absolute). For cross linking these domains I had to exclude the home page of Site 2 from navigation and use external link for it's homepage, using absolute url with domain.
As I said, I got okayish result and client didn't complain. BUT if anyone knows better practice or thinks that I've misused DM somehow, please tell me. :)
no the root could be hidden easily enough, just depends on how you build your navigations.
home
+Site 1
+--Page
+--Page
+--Page
+Site 2
+--Page
+--Page
+--Page
Should work fine.