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.