Gotcha Tweaks for "Option 1"

[lesliekirk]

Since the documents refer to the Multi-Domain option that lets you use a branch instead of an Additional Store as "Option1" - I'll use it too. Has anybody put together a checklist of "gotchas" that need to be tended to? I ask this question because the first thing that has caught my eye is that &mvt:global:domain:name; goes exactly to that - the main domain of the Option 1 configuration. Is there a token that should be used instead of it?

While trying to figure this one out, I started wondering if there are other things that need to be tweaked (that have popped up while working with the Option 1 configuration). That's what made me think first we should have a Multi-Domain sub-forum and now a "gothca" list.

[Nick]

lesliekirk That value is going to be a global value with the multi domain branch options. All global data is going to be assigned to both domains .. ie Price Groups would be accessible with both domains as are the settings in Domain Settings which are available in the g.domain array.

Side note that entity is not used anywhere in the current Shadows framework so using a fresh install on the new branch will get you started in a good place.

[lesliekirk]

lesliekirk

Side note that entity is not used anywhere in the current Shadows framework so using a fresh install on the new branch will get you started in a good place.

The site has a lot of custom work that was done in another framework. The storeowner wants to preserve all of that custom work to use in the "Option 1" configuration. So for this store - it's a gotcha.

[Nick]

lesliekirk Also, note that the Template Search and Replace module will update that value in the new branch, with just a few clicks.

[lesliekirk]

lesliekirk Also, note that the Template Search and Replace module will update that value in the new branch, with just a few clicks.

Good to know that the Template Search and Replace module will work for this Multi-Domain branch template.

I may have overlooked or missed this - how do I get the Option 1 Store Name to display in the &mvt:store:name; tag? Will this be another find-and-replace task?

[SidFeyDesigns]

I semi recently went through some of these Multi-Domain gotchas but this was specific to a store using a heavily modified version of the Suivant theme. This was also set up using Option 1. I'm not entirely sure if this will help your specific case but I thought it might be helpful to share.

My workaround for some of the global variables was to give them their own unique variables and use the Template Serach and replace to update where needed which was a huge time and headache saver.

I used these in the global HTML profile to keep them all in one place and ensure they were declared at the top of every page template.

<mvt:comment>Set Theme File Path to Domain Two branch specific directory</mvt:comment>
<mvt:assign name="g.theme_path" value="'b17/themes/suivant'" />
<mvt:comment>Global DomainTwo.com Variables</mvt:comment>
<mvt:assign name="g.DT:domain:name" value="'www.DomainTwo.com'" />
<mvt:assign name="g.DT:store:name" value="'Domain Two" />

Then searched for &mvt:global:domain:name; and &mvt:global:store:name; and replaced with &mvt:global:DT:domain:name; and &mvt:global:DT:store:name;

Also, via FTP access I added a directory folder in the branch specific directory for images that are only used on the 2nd domain (b17/graphics/). I'm not sure if this was the correct way to do this but it helped with some conflicts I was having between the 2 domains when working in the 2nd domain's branch.

I also added this to the htaccess file to handle the two different sets of robots.txt, fav.ico, and sitemap.xml files that all live in the root folder/primary directory of the server. These rewrites were placed after the Miva Merchant URI Managment rules.

# rewrite robots_dt.txt for DomainTwo.com
RewriteCond %{HTTP_HOST} ^(.*)?DomainTwo(\.com)
RewriteRule ^robots\.txt$ robots_dt.txt [L,NS]

# rewrite favicon_dt.ico for DomainTwo.com
RewriteCond %{HTTP_HOST} ^(.*)?DomainTwo(\.com)
RewriteRule ^favicon\.ico$ favicon_dt.ico [L,NS]

# redirect robots_dt.txt for DomainOne.com
RewriteCond %{HTTP_HOST} ^(.*)?DomainOne(\.com)
RewriteRule ^robots_dt.txt$ https://www.DomainOne.com/robots.txt [R=301,L,NE,NC]

# redirect favicon_dt.ico for DomainOne.com
RewriteCond %{HTTP_HOST} ^(.*)?DomainOne(\.com)
RewriteRule ^favicon_dt.ico$ https://www.DomainOne.com/favicon.ico [R=301,L,NE,NC]

# redirect sitemap_dt.xml for DomainOne.com
RewriteCond %{HTTP_HOST} ^(.*)?DomainOne(\.com)
RewriteRule ^sitemap_dt.xml$ https://www.DomainOne.com/sitemap.xml [R=301,L,NE,NC]

# redirect sitemap.xml for DomainTwo.com
RewriteCond %{HTTP_HOST} ^(.*)?DomainTwo(\.com)
RewriteRule ^sitemap.xml$ https://www.DomainTwo.com/sitemap_dt.xml [R=301,L,NE,NC]

There may be some other gotchas I'm forgetting but these were the bigger ones I remember dealing with.

Hope this helps.